Can someone pass this around without rewriting the recommendation first?
Sample decision brief
A redacted decision brief that still feels like a working document.
This composite is meant to feel like something a team would actually circulate: a clear recommendation, the reason now, who needs to weigh in, and what would make the team pause or revisit the move.
The harder question is whether your team would actually use this in a real review meeting instead of rebuilding the recommendation into another slide deck first.
Use
What the brief needs to do in a real discussion.
Is it obvious what is being recommended, where it applies, and where it does not?
Does the brief say what would make the team pause, narrow the move, or revisit the recommendation?
Why this format travels
The sample only works if it removes review friction in actual meetings.
One brief holds the same decision scope, stake, and recommendation for every function.
Cross-functional review starts from one version, so commercial, medical, legal, and HEOR are less likely to debate different problem statements.
Escalation moves the same document upward instead of restarting the narrative at each layer.
In leadership reviews, unresolved points stay in the brief instead of turning into a new version of the story at each layer.
The same brief can be reused in check-ins, leadership reviews, and sign-off prep.
Teams spend less time rebuilding slides for each meeting because reviewers can work from one source brief between sessions.
What a team can do after reading it
The sample makes the next conversation shorter and clearer.
A first brief earns its place if it gives the team a cleaner recommendation, a clearer review path, and a better starting point for the next similar decision.
This opening brief is not broad launch support, a standing strategy retainer, or a substitute for every downstream workflow the organization may later want.
It replaces the usual cycle of separate email threads, meeting-by-meeting retellings, and slide rebuilds around the same blocked decision.
The company still has to prove that a brief like this gets reused, shortens review friction, and leaves behind a stronger starting point for the next decision.
Next step
If your team would use a brief like this, bring one focused decision.
If it looks close to what you need, the next question is whether your decision is specific enough to describe clearly in a short opening message.