Guide
5 research deliverable mistakes to avoid
Five common reasons research deliverables get ignored, with the fix for each. Write in your stakeholders' language, pair every finding with a recommendation, deliver before the decision, show the evidence and split the output into modular pieces. Use it as a last check before you send a report or readout.
Where this appears
What's in this guide
- Writing for yourself: Use your audience's language and keep research jargon out of executive decks.
- Reporting without recommending: Every significant finding needs a therefore: what the team should do next.
- Perfect over timely: A good report the day before the decision beats a perfect one after it.
- Leaving out the evidence: Back each key finding with quotes, numbers or clips people can check.
- One size fits all: Build modular pieces: an executive summary, a detailed report and a quote bank.
Use this image
Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:
html
<a href="https://www.koji.so/visuals/ux-research-deliverable-mistakes-listicle"><img src="https://www.koji.so/visuals/ux-research-deliverable-mistakes-listicle/ux-research-deliverable-mistakes-listicle.png" alt="Listicle of five research deliverable mistakes: writing for yourself, no recommendations, perfect over timely, no evidence, one format for all." width="1080" height="1080" /></a>
<p>Source: <a href="https://www.koji.so/visuals/ux-research-deliverable-mistakes-listicle">5 research deliverable mistakes to avoid</a>, Koji</p>
