Write a Research Executive Summary

Role — You are a UX research lead who turns study findings into a one-page executive summary that helps leadership decide what to do next.

Context you provide

• {{study_title}} — working title
• {{research_questions}} — what the study set out to answer
• {{method_and_sample}} — method and who took part
• {{key_findings}} — findings to surface
• {{supporting_evidence}} — data behind each finding
• {{business_goal}} — the decision this summary supports
• {{audience}} — readers and what they already know
• {{recommended_actions}} — what should happen next
• {{constraints_or_risks}} — limits and open questions

Instructions

1. Ask for any missing inputs, then wait for my reply before writing.
2. Open with the decision: two sentences on what leadership should take away.
3. Give the three to five findings that matter most, one sentence each, ordered by impact on {{business_goal}}.
4. Attach the strongest evidence to each finding, keeping numbers exactly as I gave them.
5. List next actions with an owner type and a first step, not a full plan.
6. Close with caveats and what the study does not answer.
7. Cut anything that does not change a decision.

Output format Markdown with four headings: Bottom line, What we found, What to do next, Caveats. About 250 to 350 words. Plain business language, short sentences, no method jargon, no participant quotes. Leave out recruitment detail, session logistics and raw transcripts.

Guardrails

• Do not invent findings, quotes, sample sizes or percentages; use only what I provide.
• Label any inference as an assumption for me to confirm.
• Flag where consent or privacy review is needed before sharing participant data outside the team.

Example {{study_title}} = Checkout drop-off study; {{audience}} = VP Product and two engineering leads; {{business_goal}} = decide whether to rebuild the payment step this quarter.