Part II: Building the first version
9. Choose one useful journey
Work out what the user needs to accomplish, then draw a boundary around the first version.
Start with the moment someone needs your product. What has happened? What are they trying to do? What would let them put it away and get on with their day?
Those questions help you choose the work your first version needs to support. A list of features can grow for as long as you keep thinking about it. A specific task gives you a way to decide which features belong.
Name the job
You might hear this described as a “job to be done.” We'll use it to mean the progress someone wants to make in a particular situation. Write it in everyday language, using what you learned in Part I.
For our hypothetical designer, the job is getting a clear client decision so work can continue. For example, you might build a feature that reminds the client to review the latest draft. That reminder helps if it gets the designer closer to receiving the decision they need.
You already have a sentence about who you're helping and how. Use this one to describe the moment they'll need your product:
When [situation happens], I want to [make progress], so I can [reach an outcome].
For the designer, that might read: when a draft is ready for review, I want the client to answer a specific question about it, so I can finish the next round of work.
Check the sentence against a real example from your conversations. If it describes something the person never actually tries to do, go back to those notes before using it to choose features.
Follow the task from beginning to end
A user journey is the sequence someone goes through to reach the outcome. Start with the simplest successful version, often called the happy path.
For our example:
- The designer adds a link to the draft and the decision they need.
- The product saves the request and provides a link to share.
- The client opens the request, reviews the draft, and responds.
- The designer opens the saved response and decides what to do next.
This includes two people. A beautiful client response page is only part of the flow. The designer must be able to create the request and see the answer afterwards, or the trial stops before you can learn much.
Write the steps before sketching screens. Some steps may happen on the same screen. Others may happen outside the product: for now, the designer can copy the link into an email they send themselves.
Decide what belongs in the first version
For each feature, ask which step needs it. Then ask whether there's a simpler way to complete that step for the first trial.
Here's a possible boundary for our example:
| Needed for this trial | Can wait |
|---|---|
| A link to the draft and a clear question | Uploading and managing design files |
| A way for the client to submit a response | Comments pinned to parts of an image |
| A saved response the designer can read | A dashboard of trends across projects |
| Access limited to the intended people | Team roles and organisation settings |
The access rule belongs in the first version because the flow includes another person's work. You can keep the arrangement simple, but you still need to decide who is allowed to see and change each request.
Keep a separate list of ideas for later. Recording them lets you return to them without adding them to the current brief. You can move something back in when you discover that the useful task depends on it.
Describe what completion looks like
Write a check you could perform yourself. “The feedback system works” is too vague to be helpful when the AI tells you it has finished.
For this example: create a request, open it as the client, submit a response, and see that response from the designer's view. Refresh the page and check that it is still there. Use content you wrote yourself so you can tell it apart from a sample response.
Add your steps, the features you're leaving out, and your completion check to the same notes. This is the detail the AI will need in your build brief. In the next chapter, we'll look at how to make the steps understandable to someone seeing them for the first time.