Your app is built. Try this one-user launch rehearsal
You have a working app, or you're close. Before making a long launch checklist, try a short rehearsal with someone who hasn't watched you build it. The goal is…
You have a working app, or you're close. Before making a long launch checklist, try a short rehearsal with someone who hasn't watched you build it. The goal is simple: see whether that person can do one important thing without your help.
A usability test is an observation of someone attempting a task with a product. Digital.gov recommends choosing a scenario, preparing a script, getting the participant's consent, and asking them to think aloud. You can use those steps without turning this into a giant research project.
Choose one task
Pick the first action that matters to a new user. That might be creating an account, saving a project, finding a lesson, or booking something. Your task should describe the goal, not the buttons: “Find a way to save this for later” is more revealing than “Tap the bookmark icon.”
Write down what success would look like. Decide where you'll take notes. If the app contains personal information, prepare a demo account or safe sample data.
Prepare a fair starting point
Open the app at the place a new user would normally arrive. Check that the task is possible in the version you will show. If the app contains personal information, set up a demo account and sample data. Turn off notifications that could reveal anything private during a screen share.
Make a tiny note sheet with four headings: task, actions, pauses, and questions. “She tapped the menu three times” is an observation. “The menu is bad” is an interpretation. Keeping those separate helps you decide what to change after the session rather than defending the design in the moment.
Invite one relevant person
Choose someone who resembles the first user you're trying to reach and who hasn't been coached through the app. Tell them you're testing the app, not testing them. Ask permission to take notes or record, and be clear about how you'll use what they share.
Here's a plain invitation you can adapt:
I'm getting my app ready for new users. Would you spend 15 minutes trying one task and telling me what you're thinking? I'm looking for confusing parts so I can improve them.
One session will not represent every customer. It will give you a real first observation to work from.
A friend can help you practice the script, but someone closer to the first user you hope to reach will usually give you a more useful launch signal. That first attempt gives you a real starting point for a launch decision.
Watch before you explain
Read the task, then pause. Ask the person to say what they're looking for and what they expect to happen. Notice where they hesitate, backtrack, or ask a question. Try not to rescue them immediately; the pause is information. Digital.gov's sample usability-test script uses this think-aloud approach during task completion.
Afterward, ask what they expected at the confusing point. Keep the question open. “What were you looking for?” is more useful than “Did you like my navigation?”
If they go quiet, ask, “What are you thinking now?” without pointing them toward a button. When they truly cannot continue, note the stopping point and move on kindly. There is no value in making someone struggle for the sake of a test.
After the session, thank them and follow whatever you agreed about notes or a recording. You do not need to turn their words into a testimonial or share their screen outside the session.
Make one change and repeat
Review your notes. Pick the problem that most directly stopped the task. Change the label, explanation, order, or screen that caused it. Then let another person try. You don't need a perfect launch plan to begin learning from real use. If the person completed the task smoothly, ask what they expected to happen next and choose another important task for a later session. If they stopped, give the same goal to another relevant person after your change and see whether that step is clearer.
Here's a small exercise for this week: write one task your first user should finish, invite one person to try it for 15 minutes, note the first place they pause, and make one improvement. Put the invitation on your calendar today.
If you'd like people alongside you as you turn those observations into launch steps, read about the Women Who Build Launch Program.