Build a research brief from messy sources

Should we enter the mid-market segment in the next two quarters?

That is the kind of question a research brief exists to answer: specific, decision-shaping, and answerable in under a page if the material is organized around it rather than around the sources that produced it.

Most research does not end in a report. It ends in a brief, read in minutes, trusted because it is traceable, durable because it can be updated when the situation changes. The problem is that inputs are never clean. Sources conflict, overlap, and arrive in no particular order. What follows is a repeatable path from that mess to a brief you can stand behind.

Start from the decision, not the sources

Write the decision and the question that drives it before you read anything else. Everything downstream gets filtered by that question. Sources that do not move the decision are interesting, not relevant, and the discipline to tell those apart is what keeps a brief short.

Reduce sources to grounded claims

You do not synthesize sources; you synthesize claims. The path from messy inputs to a brief runs through a layer of grounded claims: assertions with their support and qualifications attached.

1. Read actively. Capture signal in context as you read, so each claim already knows its source. (See active reading for analysts.)
2. Cluster by sub-question. Group claims under the questions the decision depends on: market size, competitive response, cost to serve, timing.
3. Resolve or record conflicts. Where sources disagree, either resolve it with better evidence or record the disagreement as a finding. (See source-grounded synthesis.)
4. Mark the gaps. An honest brief names what it does not know. Formal evidence-synthesis practice treats this as its own step, sometimes called a gap map, rather than an afterthought (Cornell University Library).

Shape the brief around the decision

A brief is not a summary of your research. It is an argument structured for the reader. A reliable structure:

• Bottom line. The answer to the decision question, stated plainly, up front. This is the same instinct behind bottom-line-up-front writing in professional and military contexts: state the conclusion before the reasoning, because the reader's attention is scarcest at the start of the document (Princeton University Press).
• Why. The two or three grounded claims that most support the bottom line.
• What would change it. The assumptions or risks that, if wrong, flip the conclusion.
• What we don't know. The named gaps and open questions.
• Evidence. Every claim links back to its source, so any line can be inspected.

A decision-maker should be able to stop after the bottom line and still have the answer, then read deeper only where they want to challenge it.

Keep it traceable

Traceability is the single feature that separates a trustworthy brief from a plausible one. When every claim links to the passage that supports it, the brief survives scrutiny: a reviewer can verify any line without redoing the research, and you can defend the conclusion months later when someone asks where a number came from. It is also what makes a brief reusable. When the situation changes, you update the affected claims and their evidence instead of starting over.

Before you call it done

• State the decision question in one line, at the top.
• Cluster claims by sub-question, not by source.
• Record disagreements you did not resolve. Do not average them away.
• Name the gaps: what you do not know yet.
• Lead with the bottom line; put the evidence after it, not before.
• Link every claim to the passage that supports it.
• Read it back as the skeptic in the room, not the person who wrote it.