Turn a pile of research notes into a report stakeholders actually read
A thorough research writeup and a report someone will actually finish reading are not the same document.
- Outcome
- A report that leads with the finding that matters most, backs it with just enough evidence to be credible, and gets read to the end instead of skimmed or ignored — built from the same raw notes a exhaustive writeup would have used.
- Time
- 1.5-3 hours depending on research volume
This workflow is part of PromptKit Pro
A handful of prompts and workflows stay free for everyone — Pro unlocks the full library, including this one, plus the guided runner.
Research notes accumulated across interviews, surveys, or usability sessions often get compiled into a thorough writeup that covers everything found, in the order it was discovered — comprehensive, but structured for the researcher's process rather than a stakeholder's attention span, which means it gets skimmed for a summary or not read at all. This playbook restructures the same raw findings around what a stakeholder actually needs first, backed by just enough evidence to be credible without burying the point.
When not to use this
If the audience genuinely needs the full methodological detail — an academic or highly technical audience, say — a comprehensive writeup is the right call. This is for a business stakeholder report.
Did this work?
A stakeholder who only reads the first paragraph still knows the main finding and what it implies, not just that "research happened."
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.