Turning a dense BRD into a stakeholder presentation: what I cut and what I kept
I do a lot of work where a 50-plus page BRD already exists and someone needs it turned into something the steering committee will actually engage with. Over enough of these I've landed on a rough method for the cut, so sharing it, and because I want to hear where others draw the line differently.
The mistake I made early was treating the stakeholder presentation as a summary of the BRD. Shorter version, same shape. It never worked, because a BRD is organised for completeness and traceability, and a presentation has to be organised for a decision. Different jobs. You can't just compress one into the other.
What I cut, every time: the full requirement catalogue, the traceability matrix, the detailed acceptance criteria, the glossary, anything that exists for the build team or for audit. None of it earns a place in front of a sponsor. It all stays in the BRD where it belongs and gets referenced, not shown.
What I keep, and lead with: the problem the project exists to solve, stated in business terms, not system terms. The two or three decisions that genuinely change the shape of the solution. The scope boundary, specifically what's out, because that's where stakeholders get surprised six months later. And the assumptions that, if wrong, blow up the estimate. That last one I learned the hard way.
The reframe that made the difference: every slide in the stakeholder presentation has to be something a sponsor needs to know to approve, fund, or scope the work. If a slide only proves the BA did their homework, it's for me, not for them, and it comes out.
The BRD doesn't shrink. The presentation is a different artifact aimed at a different reader, drawn from the same source.
Where I'm still unsure is how much of the "how" to keep. Some sponsors want zero solution detail, some feel managed if there's none. Curious how others handle that line.