Research

Research Brief Prompt

Objective, Background, Findings, Recommendations, Open Questions — briefs where what was found and what to do stay clearly separated.

Overview

Research briefs lose credibility in one move: recommendations that smuggle past the findings. This setup generates briefs in five pinned sections with the type rule stated outright — separate what was found from what is recommended; different sections, different claims — plus evidence discipline: state the confidence or evidence behind each finding. Open Questions is pinned so unknowns get documented instead of papered over, and optional tables handle the comparison grids research briefs lean on.

Workflow

One brief shape per program
Every study reports in the same five sections — stakeholders learn to navigate them once.
Audit the findings-recommendation seam
Each recommendation should trace to a finding above it; the structure makes orphans visible.
Respect Open Questions
A pinned unknowns section is what separates research from advocacy.

Why This Works

Structural separation enforces the found-vs-recommended distinction reviewers check first
Per-finding evidence statements calibrate stakeholder trust
Pinned Open Questions makes intellectual honesty a formatting requirement

Best for

UX and market research teams briefing stakeholders
Briefs that feed decisions and get challenged
Research ops standardizing deliverables

Not for

Summarizing a published paper — that's the Structured Summary Prompt's research-paper setup
Building the research workflow itself — that's the Multi-Step Prompt Builder

Use cases

Writing research briefs in the same shape per study
Keeping recommendations tied to documented findings
Documenting unknowns instead of hiding them

Customize This Resource

Opens this setup in Markdown Output Builder. Generate to get the full markdown prompt — then adjust the sections, table rules, and consistency level.

Open in Markdown Output Builder

Prompt Template

TASK
Write research briefs that keep findings and recommendations clearly separated.
Produce a new markdown document — there is no source text to summarize.

DOCUMENT
The document is a research brief.
- Separate what was found from what is recommended — different sections, different claims.
- State the confidence or evidence behind each finding.

DOCUMENT STRUCTURE
Start with one "# " title line, then use exactly these sections, in this order:
## Objective
The question this research answers.
## Background
Context the reader needs.
## Findings
What was found, with evidence.
## Recommendations
What to do, grounded in the findings.
## Open Questions
What remains unknown.

MARKDOWN RULES
- One "# " title at the top; every section below it is a "## " heading.
- Use markdown lists for enumerations — no walls of prose.
- No HTML tags — pure markdown.

TABLE RULES
- Use a markdown table when content is naturally tabular — comparisons, option matrices, parameter lists; otherwise prefer prose.
- Every table needs a header row and a separator row.

CODE RULES
- Do not include code blocks.

CONSISTENCY RULES
- Use every section defined above, in the order given.
- Do not add new top-level sections — put extra material inside the closest existing section.

OUTPUT RULES
- Return only the markdown document — no preamble, no closing commentary.
- Start directly with the "# " title line.
- Do not wrap the document in code fences.

Related Resources

Explore more resources that work well with this one.