Launching and running it
How do I get useful feedback from my app's first users?
Lumos · Updated
Ask someone to complete a task with the app and watch what happens. Give them room to choose their own steps before explaining the interface. Record where they hesitate, make an unexpected choice, or need help.
Use someone who experiences the problem you're trying to solve. Prepare safe sample material if the app isn't ready for their real information. Explain that you're checking the product, and make it comfortable for them to point out difficulties.
Ask about what you observe
When something is unclear, ask what they expected to happen. If they suggest a feature, ask which part of their task it would help with. Help them continue if they're stuck, and record where your explanation was needed.
The GOV.UK guide to moderated usability testing describes giving neutral tasks, observing attempts, and following up on what you see.
After the task, ask whether the result helped them and how it compares with their current way of working. Someone can complete the screens successfully and still prefer their existing process.
Turn the feedback into a change
Keep observations separate from proposed solutions. In the handbook's hypothetical example, a designer missing a client's response is an observation. Adding email notifications is one possible response; making new replies easier to notice might address the same difficulty.
Fix failures that block the task or lose work first. Choose a small improvement, update the app, and repeat the affected task. Keep the original observation beside the change so you can check whether it actually helped.
In the Builders Handbook
Give it to a friend walks through preparing a trial, taking useful notes, and deciding what to change next.