findings aren’t decisions

i’ve seen a lot of research readouts that were technically excellent and practically useless.

good recruitment, solid protocol, representative sample. the researcher did their job. and then the slide deck went up, people nodded, and the roadmap stayed the same.

the thing that’s usually missing isn’t data. it’s the connection between data and decision. research that lists what users said is not the same as research that argues what you should do next. and the gap between those two things is almost never acknowledged.

the format is part of the problem. a readout organised by theme feels rigorous — onboarding, navigation, trust, error states — but themes don’t force a decision. they describe a landscape. the PM in the room looks at the landscape and thinks “interesting” and then keeps building what was already planned.

compare that to a readout organised by tension. “users expect to see progress feedback, but our current architecture gives them nothing until the end — and that’s when 60% of drop-off happens.” that’s a claim. you can agree or disagree. you can weigh it against other priorities. it becomes an input to an actual decision.

the difference isn’t about the data. it’s about what was done with it. turning evidence into a claim requires judgment. you have to decide what the data means, what it implies, and how confidently. that’s harder than summarising themes, and it’s easier to get wrong, so a lot of researchers avoid it.

i get why. naming implications puts your interpretation on the line. if you say “this means we should redesign onboarding” and the team pushes back, you have to defend it. if you say “users mentioned onboarding in 7 of 12 sessions,” you’re just reporting. much safer.

but safety here means the research lands without consequences. which means it didn’t work.

the research i’ve seen actually change priorities always makes an argument. it names what the evidence implies. it says what needs to happen and why, not just what was observed. that’s the step that makes findings useful — the one that turns them from documentation into design direction.

if your research is stalling at the findings stage, i offer research synthesis — turning evidence into a clear design position you can actually act on. $300.