Research Communication and Storytelling Questions

Situation / Goal
When I recommend a product direction, my priority is that PMs, engineers and execs understand the “why” clearly enough to act confidently.

Structure I use (for a 10–15 min presentation or 1–2 page memo)

• Recommendation (1 sentence): clear decision and desired outcome.
• Why it matters (30s / 1 paragraph): user problem + business impact.
• Supporting evidence (3 bullets): key qualitative insights, quantitative metrics, representative quotes or heatmaps. Call out sample size & methods.
• Assumptions (bullet list): what we assume about users, tech, timeline.
• Trade-offs & risks (2–3): what we lose, mitigation plans, confidence level.
• Alternatives considered: brief pros/cons.
• Concrete next steps (owner, timeline, deliverable): experiments, metrics to track, gating criteria.

Example snippet
Recommendation: prioritize onboarding micro-tutorials to reduce time-to-value. Evidence: 6 usability sessions showing confusion on first task + analytics: 45% drop-off in first week. Assumption: tutorials won’t add >2 weeks dev. Trade-off: delays new feature; mitigate by A/B test and phased rollout. Next steps: PM to scope, engineer to estimate (1 sprint), research to run A/B and success metric = 20% reduction in week-1 churn.

I end by inviting 5 minutes of Q&A and a decision or next-step assignment.