Skip to content

Part II: Building the first version

10. Design for someone's attention

Make the next step easy to understand and the useful result easy to reach.

You know what your product does because you've been thinking about it for a while. The person opening it has none of that context. They may be looking at it on their phone between other things they need to do.

Give them enough information to recognise why they're here and what to do next. Each unexplained choice asks for a little more of their attention. Spend that attention on the task they came to complete.

Make the purpose of the screen clear

Start with a rough sketch. A piece of paper is enough. Put the information the person needs beside the action you want them to take, then read the screen as if someone had just sent you its link.

In our hypothetical feedback product, the client needs to know which draft they're reviewing and what decision the designer needs. Imagine they open the link and land on a page headed “Dashboard,” with no explanation of what to do. They'd have to work that out themselves. Showing the draft and the designer's question under “Review the latest draft” gives them somewhere to start.

Put the information the person needs beside the action you want them to take.

They also need access to the draft itself. Put the link where they can find it, and make it clear whether it opens another page. Don't require the client to search an earlier email for the thing they're supposed to review.

Think about the order of the information. Understanding the request comes before submitting an answer. Details that don't help with either can move further down the page or wait for another version.

Make actions predictable

Use words that describe what will happen. “Send response” tells someone more than “Continue.” After they send it, show that the response was saved and explain whether there's anything else they need to do.

A successful click should have a visible result. While the product is saving, make that state understandable. Avoid inviting another submission while the first is still being processed.

If saving fails, keep the response they wrote and let them try again. Having to retype it would add work at the exact moment they're already unsure what happened.

Follow familiar patterns when they fit. A labelled field, a clear submit button, and a readable confirmation can do a lot. Distinctive branding can come later; you can already make the product feel considered through clear writing and consistent behaviour.

Ask for what you need now

Onboarding is the path from arriving to being able to use the product. It might need an explanation or an account. It doesn't automatically need a tour, a questionnaire, or a sequence of welcome screens.

Look at the first useful action. What information does the product need before someone can take it? Suppose you're designing a signup form for the designer and considering fields for a company biography and profile photo. Neither is needed to write the first feedback request, so those fields can wait.

The client's path is different from the designer's. The client is responding to an invitation, so the request itself can provide much of the context. Give them a way to open and answer that request without taking them through the steps for creating requests of their own.

Account and access choices affect more than convenience. A shared link may be forwarded, for example. We'll make those choices explicit when we connect the product to saved data.

Include the ordinary awkward moments

Your sketch should show what a new user sees before anything has been created. An empty designer view can explain how to create the first request. A request with no response can say it's waiting for one.

Also sketch what someone sees if a link no longer works or a required answer is missing. Put useful guidance near the place they can act on it. “Write a response before sending” is more helpful than an unexplained error code.

Sketch how the page should fit on a phone, with the request and button easy to find. Include visible field labels, and use words to explain status changes so the meaning doesn't depend on colour alone. Add keyboard use to your build brief: someone should be able to move through the controls and complete the task without a mouse. We'll try these things on the working page in Chapter 12.

Take your sketch through the steps from the last chapter. Remove anything that gets in the way of completing them, then carry it into the setup as a reference for the build.

Before you move on0 / 4