Plan A Product Experience Before Designing Screens
Turn a promising idea into a journey your team can explain, test and build.
- For
- Founders and product teams
- Level
- Foundations
- Steps
- 5
Choose One Decision To Support
Start with a situation you can describe without naming a feature. A warehouse manager needs to find stock before promising a delivery, for example. Write down who faces the problem, what they need to finish and what currently gets in their way. Attach an observation, support request or interview note to that statement. If the evidence is missing, record a question to investigate before treating the problem as settled.

Draw The Journey In Ordinary Words
List the steps from the moment someone recognises the need to the moment they know the task is complete. Include work outside your product, such as checking a spreadsheet or asking a colleague. Beside each step, note the information needed, the choice being made and what could go wrong. A row of labelled boxes is enough at this stage; detailed screens can wait until the sequence makes sense.
Decide What Belongs In The First Release
Choose a complete, useful path through that journey. Keep a separate list for ideas that can wait, and record why they are waiting. Identify dependencies such as permissions, payment providers, content and data access. Ask engineering to review the difficult parts before polishing the easy ones. Your first release should have a clear boundary, including what happens when a required integration or piece of information is unavailable.

Test The Task Rather Than The Presentation
Make a simple prototype that lets someone attempt the priority task. Give them a realistic starting point and goal without explaining which buttons to use. Watch where they pause, recover or ask for help. Record observed behaviour separately from your interpretation. Small studies can reveal useful problems, though they do not establish how common every problem is across your audience. Revise the journey around what you actually learned.
Leave With A Decision Record
Create a short handoff with the agreed journey, the evidence behind it, the release boundary and the questions still open. Give each unresolved question an owner. Define how you will check the released experience, such as observing completion or reviewing avoidable support requests. Include empty, loading and error states in the review. The next person joining the project should be able to understand both the design and the reasoning without replaying every meeting. Try reading the handoff aloud to a teammate who previously missed the early planning sessions, then note which practical questions still need an answer.