Every intelligence function produces briefings. Very few produce briefings that change what a leadership team does. The difference is rarely the quality of the research. It's almost always the quality of the delivery.
We've sat in on hundreds of board meetings and watched the same pattern play out. A well-researched briefing is presented, politely received, and then quietly filed — because it didn't land in the place where decisions actually get made.
Here's what separates the briefings that work from the ones that don't.
They start with the decision, not the data
Most briefings open with a summary of what the research found. That's a mistake. They should open with the decision the research is meant to inform. "We need to decide whether to enter the German market" beats "Here is a summary of the German market" every single time.
When the decision is stated first, everything else follows. The reader knows what they're looking for. The evidence is framed in relation to it. And when the paper ends, it ends with a recommendation tied to the decision, not a summary tied to the data.
They carry one argument, not three
An intelligence briefing is not a newspaper. It's an argument. It should make one clear claim, support it with the strongest available evidence, and honestly acknowledge the strongest counter-argument.
If a briefing tries to make three arguments, it will fail at all three. Boards don't read intelligence like a magazine — they read it like a memo. One decision, one argument, one recommendation.
"A good briefing is not a summary of what's known. It's a point of view you can defend."
They are short by design
The single most reliable indicator of a well-written intelligence briefing is that it fits on two pages. Not because detail doesn't matter — because the author has decided what matters most.
Long briefings are usually a sign the analyst couldn't decide what to leave out. That's not a virtue. It's an abdication of the analyst's job, which is to do the hard thinking so the board doesn't have to.
They name their sources — and their uncertainties
Every claim in a good briefing can be traced to a source the reader can check. If the source is an interview, name the type of interviewee. If it's a public filing, cite it. If it's an estimate, say so.
Just as importantly, good briefings are honest about what they don't know. A confident briefing that turns out to be wrong is a briefing the client never trusts again. A calibrated briefing that says "we estimate X with moderate confidence, based on Y" is one the client will come back to.
They anticipate the counter-argument
Boards don't accept recommendations at face value. They push back. Good briefings anticipate the push and address it directly:
- What's the strongest objection to this recommendation?
- What would have to be true for the opposite conclusion to be correct?
- What's the earliest signal that we were wrong?
Briefings that answer these questions feel complete. Briefings that don't feel thin — even if the underlying research is excellent.
They are delivered, not just written
The best briefings we've produced were never just sent. They were walked through, in person or on a call, in fifteen minutes. That conversation is where the reader's real questions come out — and where the analyst can adjust emphasis in real time.
A written briefing alone is a document. A briefing delivered with a conversation is a decision.
The bottom line
Intelligence fails not because the data is wrong, but because it never reaches the room where decisions are made. The fix isn't more research. It's a tighter, shorter, more confident argument, delivered at the right moment, to the right person, in the right format.
Get that right, and your intelligence function stops being a cost centre and starts being a strategic asset.
Want to see what our briefings look like?
We're happy to share a redacted sample from a recent engagement.