Useful before perfect: how to give fast feedback someone can act on.

Picture a museum preparing a new audio tour for school groups. The exhibit producer sends you a handheld player loaded with the first version and asks for your judgment before the recording studio closes its schedule at lunch. You have ninety minutes. The question is not whether every sentence is elegant. The question is whether a teacher can hand the device to a group of restless twelve-year-olds and have them start the tour without help.

Begin by naming what the feedback is for. The producer has to decide whether to record this version tomorrow or delay the session. That purpose changes what you examine. The opening minute matters more than a small wording problem at stop nine. A visitor must know how to begin, change the volume, find the next object, and recover after pressing the wrong button. Spend your first pass as a visitor, not as the colleague who knows how the tour was designed. Pick up the player with no explanation. Follow the first instruction. Write down every moment when you pause, guess, or look for help. Those hesitations are the review.

Usability researcher Jakob Nielsen showed that a small number of testers can reveal most of a product's major problems, and one careful tester can uncover a great deal. Your value is not in producing the longest list. It is in finding the two or three obstacles that a first-time user will meet before the rest of the experience has a chance to work. Give the producer fourteen observations and you have handed the ranking job back to them. Give three in order and they can make a decision.

Shape each note so another person can reproduce it. Use three parts: what you did, what happened, and what you expected. Not, "The navigation is confusing." Say, "I pressed the green button after the welcome message, the introduction started again, and I expected the first exhibit story." That note gives the sound editor a specific path to test. It also separates an observed event from your opinion. If you have a preference, add it afterward and label it as a preference.

Name what worked, too, and not as a polite sandwich around criticism. The team needs to know what must survive the next revision. Perhaps the short chime makes it obvious when the group should move, or the opening voice immediately quiets the room. A useful positive note identifies a choice and its effect. "I liked it" is praise. "The chime got everyone looking for the next object without another instruction" is design information.

Then answer the question at the top. "Record tomorrow after fixing the first-button instruction" is a verdict. So is, "Delay the session; a visitor cannot recover after choosing the wrong language." A review that describes the tour but refuses to recommend an action leaves the producer with the same decision and less time.

Use the ninety minutes deliberately. Spend twenty minutes moving through the tour as a stranger. Spend another twenty turning the hesitations into did-happened-expected notes. Rank the top three. Take five minutes to name the strongest choice. Write one sentence of verdict above everything else. Send the review while it can still change the studio decision. Feedback that arrives before lunch is more useful than a more polished review that arrives after the booking is locked.

There is one caution. Fast does not mean careless, and ranked does not mean hiding a safety or access problem because it landed fourth. Anything that prevents a visitor from using the tour, creates a hazard, or excludes a group goes above ordinary polish. The point of ranking is to protect the decision, not to make the list artificially short.

Try the same structure the next time someone asks for feedback on a clock. First write the decision they need to make. Test as the actual user. Turn your three most important observations into what I did, what happened, what I expected. Add one choice worth protecting. Put the verdict first and send it in time to matter.

That is lesson fifteen. Answer the real decision, rank what matters, and make every note something another person can see for themselves.