The Briefing Nobody Writes — And Why Every Steering Committee Suffers For It
The Briefing Nobody Writes
Senior executives spend an average of 23 hours a week in meetings. They also spend, on average, over an hour preparing for each one. Add it up, and that's a significant portion of every working week consumed by the cycle of attending and getting ready to attend.
And yet 71% of senior managers say meetings are unproductive and inefficient. Not because the decisions aren't important. Because the preparation was wrong.
Here's the specific failure mode nobody talks about: the executive briefing — the document that should prepare a leader to walk into a steering committee and make a good decision — almost never contains the right information. It contains last week's information, formatted to look like this week's.
What Goes Wrong Before the Meeting Starts
The briefing pack goes out on Thursday. It was assembled on Wednesday from data pulled on Tuesday. The steering committee is on Friday. On Thursday morning, a dependency shifts. On Thursday afternoon, a risk surfaces in a cross-team sync. By the time the executive sits down on Friday, the pack they read on the train is already telling the wrong story.
Nobody updates it. Not because they don't care — because the pack was assembled by a program manager who has nine other things to do, and updating it would mean reassembling it from scratch.
Microsoft's Work Trend Index found that PowerPoint edits spike 122% in the final ten minutes before a meeting — the digital equivalent of cramming, where teams rush to finish slides rather than prepare thinking. This isn't a discipline failure. It's a systems failure. The briefing was always going to be out of date. The system was never designed to keep it current.
The Briefing That Would Actually Help
A genuinely useful executive briefing doesn't summarise the plan as it existed last week. It answers a specific set of questions about the plan as it exists right now.
What changed since the last steering committee? Which commitments were made and which have gone stale? Where is the plan diverging from reality, and does anyone know about it? Which decision this week requires executive input, and what context does the executive need to make it well?
These questions can't be answered from a static document. They require a live record — one that updates every time a meeting produces a decision, every time a commitment is made or missed, every time the plan shifts.
When that record exists, the briefing writes itself. Not from memory, not from what someone last updated in Confluence, but from the actual execution state of the programme right now.
Why This Matters More Than It Looks
The briefing problem is often treated as an administrative inconvenience. It's actually a decision quality problem.
Executives make better decisions when they have accurate context. They make worse decisions when they're working from a picture of reality that was true three days ago. In fast-moving programmes with high coordination overhead, three days is a long time. Priorities shift. Blockers emerge. Commitments get renegotiated in conversations the executive wasn't in.
A well-prepared executive doesn't just chair the meeting more effectively. They ask better questions, catch risks earlier, and avoid making decisions that contradict something that changed on Tuesday. The briefing isn't overhead — it's the infrastructure of good judgment.
The Coordination Layer Connection
The reason the briefing nobody writes is hard to write isn't that nobody has tried. It's that writing it manually requires someone to attend every meeting, track every decision, and synthesise the state of the programme in real time. That's a full-time job.
A Living Plan changes the calculus. When every meeting decision is captured and propagated automatically, the briefing is no longer assembled — it's generated. The programme state is always current. The questions an executive needs answered are already answered, from the record, not from someone's memory.
The briefing nobody writes is actually the briefing nobody has had infrastructure to write — until now.
In Parallel generates executive briefings from your actual programme state — updated after every meeting, automatically. See how it works →
Related reading
Get insights like this in your inbox
One email per week on execution intelligence, team coordination, and enterprise AI. No fluff.
By subscribing you agree to our Privacy Policy. Unsubscribe anytime.
