Testing the Questionnaire Before It Costs Us

On Movement, the self-assessment questionnaires were where usability testing earned its keep. Completion rate is the metric the whole experiential design hangs on, so a confusing question isn't a cosmetic issue — it's an abandoned flow and a checkup that never gets logged. From a delivery standpoint, that's exactly the kind of risk you want surfaced before a sprint commits to it, not in production. I ran tests on the questionnaire flows early, watching where people hesitated, re-read, or tapped the wrong target on mobile. The fixes were often small — bigger tap targets, a more conversational phrasing, an icon that carried meaning faster than text — but catching them early meant we weren't re-opening 'done' work later. For a PMO, the value is predictability: testing converts vague 'is this good enough' debates into observed evidence, so prioritization calls get made on what users actually struggled with rather than opinion. I also kept tests lightweight and frequent rather than one big event, which fit the cadence better and kept findings flowing into the backlog instead of arriving too late to act on.