Skip to content

Part II: Building the first version

16. Give it to a friend

Watch someone try the live version and use what happens to choose the next changes.

Send someone the live URL. Choose a friend who is willing to try an unfinished product and tell you where it makes their task difficult. If they have experience of the problem you're solving, you'll have more to discuss afterwards.

Be clear about what you're asking them to do. They don't need to review every screen or come up with a list of features. Give them a task that lets you see whether the first version does what you intended.

Set up a useful first try

Use sample material you can comfortably share. Make sure your friend has the access they need, and explain any limitation that could affect their attempt. If their work won't be kept after the trial, tell them before they enter it.

For our hypothetical feedback product, you could ask a designer friend to create a request for a sample draft. You can act as the client and submit a response, then watch the designer find it. If your friend is trying the client side instead, prepare a request and ask them to respond.

Here's an invitation you could adapt:

I've built a first version of the feedback tool we talked about. Could you try asking for a decision on a sample draft? I'd like to watch how you use it and hear what gets in the way. It's an early version, so please use the sample material rather than client work.

Only refer to a previous conversation if you actually had one. Use your own words and describe the task that fits your product.

Let them try before explaining

Introduce the task, then give your friend room to work through it. You can ask them to say what they're looking for or what they expect a button to do. Avoid describing each click before they've had a chance to choose it themselves.

Introduce the task, then give your friend room to work through it.

When they pause, notice where they are and what they appear to be trying to do. If they ask a question, find out what they expected to happen. Their expectation can help you understand why the screen isn't giving them enough information.

If they get stuck, help them continue. You can still learn about the rest of the flow. Record where you helped, because completing the task with your explanation is different from completing it independently.

This is a trial of the product. Make it comfortable for them to point out awkward parts, and don't spend the session defending why you built them that way.

Keep observations separate from guesses

Write down what happened while it is fresh. “They opened the request but couldn't find the draft link” is something you can act on. You might decide that a guided tour of the page would help, but first check whether the link itself was easy to find.

For each difficulty, note the step, what the person tried, and any help you gave. You can then decide whether clearer wording, a different layout, or a missing piece of behaviour would address it.

Ask about the result too. Could the client give the decision the designer needed? Could the designer continue the work after reading it? Completing every click doesn't necessarily mean the product helped with the original problem.

If your friend doesn't experience that problem themselves, keep the conclusions narrow. You can learn about confusing interactions without treating their approval as evidence of demand. Take the working version back to people you spoke with in Part I as well.

Choose the next change

Fix failures that stop the task or lose someone's work first. Then look at places where your explanation was necessary. A small change may make the next attempt much easier.

Keep new feature requests alongside the situation that prompted them. For example, suppose the designer asks for an email when a client responds. Ask how they currently find out a response has arrived and when they need to read it. That helps you decide whether they need an alert while they're away from the product, or a clearer indication of new responses when they open it.

Make the change, deploy it, and repeat the affected task. Give your friend a short explanation of what changed if they're willing to try again.

This is where the first release of the handbook ends. Keep using what you observe to choose the next change, then try it again with someone who has the problem. Part III is coming soon and will cover preparing the product for people you won't guide personally, including clearer messaging, payments where relevant, tracking, and reaching the first community.

Before your next round of changes0 / 4