Describe the problem before the solution
Explain what happens today and where it becomes difficult. A specific example is more useful than a list of technologies. For a website, describe what visitors struggle to find or do. For an application, describe the task your team needs to complete.
- What triggers the task?
- Who is involved?
- Where do delays, repeated work or mistakes occur?
Identify users and responsibilities
List the people who create, review and approve information. Include who will provide content, answer questions and review the work. Different roles may need different access.
- Primary users and their main tasks
- Decision maker and review contacts
- Content and data owners
Separate essentials from later ideas
Describe the minimum useful outcome first. Keep future ideas visible, but distinguish them from what must be ready at launch. Record any existing systems or deadlines that affect the work.
- Essential launch requirements
- Improvements for a later stage
- Existing platforms, integrations and timing constraints
Agree how the work will be reviewed
Describe what a successful journey looks like from start to finish. This gives the project discussion a practical basis for defining scope, acceptance checks and handover.
- Example journeys to review
- Responsibilities for testing and feedback
- Launch, training and support questions
Put it into practice.
Prepare a short brief covering your business, the problem, the users, essential requirements and known constraints.
Discuss Your Project