Usability testing when you have no budget and no time

Teams skip usability testing for two reasons: they think it needs a lab, and they think it needs weeks. Both were true in 2005. Neither is true now.

Our minimum setup is five participants, thirty minutes each, run over one or two afternoons. Five is not a magic number, but in practice it surfaces the majority of serious problems — by the fourth session you are mostly hearing the same failures again.

The script matters more than the tooling. Write three to five tasks phrased as goals, not instructions: “You want to change your delivery address” rather than “click Settings, then Addresses.” The moment you tell people where to click, the test is measuring your instructions instead of your interface.

During the session, the only hard rule is silence. When the participant gets stuck, the urge to help is enormous — resist it. The stuck moment is the data. Note where it happened, what they said, what they tried. Screen recording plus a notes document is a complete lab.

Afterwards, resist the giant report. We compile findings into a single page: what broke, how often, how badly, and one recommended fix per issue. A one-page document gets read and acted on the same week; a forty-page report gets a calendar invite and then a quiet death.

Do this once per quarter and your product decisions stop being arguments between opinions. It is the highest return-per-hour activity we know in product work.