The day · Page 48
15:30, user testing: reactions, not results
For you only
Same-day testing is rough, and it is still better than another opinion in the room.
Be honest about the word. You get reactions, not results. A reaction is a person opening the thing for the first time and getting lost, or lighting up, or asking "what is this for?". That is signal. It is not a statistic. It is enough to decide and move forward.
At Ionian Technologies, the team tested a finished-looking app with strangers on the streets of Thessaloniki. One user spent ten minutes and never found an outfit. Another tapped an outfit expecting details that were not there. A third could not say what the app was for. None of that was visible from inside the team. Heavy findings, learned in a day instead of a quarter. The prototype looked done. The reactions told the truth.
Two honesty rules for this half hour, both from Rob Fitzpatrick's The Mom Test, the best short book ever written on talking to users. Compliments are worthless; he calls them the fool's gold of customer learning. And the deadliest sentence a user can say is that they would definitely use it, because "would" is a promise about an imaginary future. People are polite, and politeness is noise. Watch what they do. Discount what they predict.
If you ran synthetic users mid-build (Chapter 21), this half hour is where their findings meet reality. The AI argued; these thirty minutes decide.
If you genuinely cannot test on the day, run the day anyway, for alignment, and test in the days after. A Product Build Day with no user test is still worth it, because the room aligned and built together and you led it. But test if you possibly can.
The test is what makes the day honest.