Let me take you inside a real meeting as it happened.
It is 8:30 a.m. A boardroom. Air-conditioned. Coffee untouched. The executive team had circulated a 120-page pack three days earlier. Everyone has “read it.” Everyone is prepared.
By 11:00 a.m., nothing has been decided. That is not a time problem. That is a writing problem.
I was invited into this organization because execution had stalled. Projects dragged. Risks lingered. The board felt management was evasive, and management felt the board was intrusive. Both were right and were victims of the same disease: writing for files, not for decisions.
Let me show you how it actually plays out at work.
What the documents looked like
The reports were technically excellent, risk registers, financial analysis, scenario modelling, clear English and professional formatting.
But every paper had the same hidden structure.
- Background first.
- History second.
- Analysis third.
- Options listed neutrally.
- The conclusion is carefully vague.
The final page usually said, “For discussion” or “For noting.” That single phrase explained everything.
No one was expected to decide. Everyone was expected to look informed.
What it felt like inside the organization
I spent time with a senior manager, of medium height, always neatly dressed, highly competent. She walked me through a major operational risk that had appeared in three consecutive board packs.
“Why is this still open?” I asked.
She smiled, slightly embarrassed. “We are still monitoring it.”
Monitoring had become a substitute for judgment.
The risk was real. The mitigation was known. But no one had written a paper asking for a decision to spend money, change ownership, or accept residual exposure.
So the risk lived on. Safely documented. Perfectly filed.
What most leaders miss
Imagine a pilot who announces turbulence, explains wind patterns, shares altitude data, and lists three possible routes. Then lands the plane without choosing any of them.
Passengers would not call that professionalism. They would call it avoidance.
Yet this is how many leaders write.
The turning point moment
We did something deliberately unconventional. At the next board cycle, I asked management to rewrite just one paper. Not shorter. Clearer.
The first sentence had to be this: “This paper asks the board to decide whether to approve X.”
No background allowed until that sentence was written.
There was resistance. Real resistance. One executive said, “What if the board disagrees with our recommendation?” I replied, “Then at least you will know where you stand.” That is the fear no one names.
What changed in the room
When the rewritten paper landed, the board discussion changed immediately. Instead of wandering through the background, board members challenged the recommendation directly.
Instead of asking for more information, they debated trade-offs. Instead of deferring, they decided. The meeting ended early, which had never happened before. More importantly, management was left with a mandate, not minutes.
What the case revealed
Three things became obvious very quickly. First, writing for decisions forces thinking to mature before the meeting, not during it.
Second, ambiguity had been protecting individuals, not the organization.
Third, boards are not slow; they are cautious when they are not asked to decide.
Within two quarters, execution speed improved. Not because people worked harder, but because fewer issues lingered in limbo.
Why smart leaders avoid decision writing
Writing for decisions exposes judgment; it shows what you believe should happen, it creates a record of your thinking, it ties your name to an outcome. Writing for files does the opposite; it shows effort without commitment. It signals diligence without risk.
In environments where leaders are punished for being wrong rather than for being unclear, file-writing thrives.
This is not a technical problem; it is a leadership climate problem.
What boards and executives should demand
In every serious organization I now advise, I insist on three disciplines. Every paper must ask for a decision. Every recommendation must name its downside.
Every delay must have a stated cost. When these rules are applied consistently, something interesting happens: politics reduces, trust increases, and accountability sharpens. People stop hiding behind paper.
The deeper lesson
Documents do not fail organizations. Cowardly writing does. Writing for decisions is an act of leadership. It says, “This is my judgment. Challenge it if you must, but do not ignore it.”
Files are safe, decisions are risky. That is why leadership matters.
If your organization has excellent documentation and mediocre results, do not train people to write better reports. Train them to take clearer positions.
Because in the end, no organization is remembered for its files. It is remembered for the decisions it dared to make.
I remain, Mr Strategy
Copyright Summit Consulting Ltd 2025. All rights reserved.
