6. The Cost of Unclear Mandates
Organisations rarely fail because of a lack of effort.
Things fail because of a lack of clarity about what effort is supposed to achieve. I’ve seen this pattern across sectors, sizes, and leadership styles: a team works extremely hard, delivers activity at pace, and yet the organisation remains stuck.
When you look upstream, the cause is almost always the same — the mandate itself was unclear, contested, or quietly contradictory.
You can’t fix execution when the instruction set is broken.
But leaders can routinely assume that the implementation team is the problem. They increase oversight. They add reporting. They commission diagnostics. But these responses often stabilise the very dynamic that caused the issue: a belief that clearer activity will somehow compensate for unclear direction.
In my own work, I’ve learned that organisations rarely articulate mandates fully — not because leaders are avoiding responsibility, but because there are usually competing pressures shaping what they can commit to: Boards want progress; regulators want compliance; executives want optionality; markets want signals; staff want autonomy; and clients expect more for less.
Somewhere in that mix, the actual mandate becomes diluted. Everyone thinks they agreed to the same thing, but they didn’t.
This quiet divergence is where transition work begins.
Mandate Drift Happens Before the Work Starts
Mandate drift isn’t a mid-project deviation — it’s baked in at the start. It shows up in three places:
i. The unspoken constraints
Leaders know the external pressures but hesitate to name them. They want strategic freedom without acknowledging regulatory, financial, or political boundaries. If those constraints are not named, teams build plans on false space.
ii. The invisible trade-offs
Every transition involves a sacrifice: speed vs accuracy, cost vs capability, compliance vs autonomy. When leaders refuse to surface these trade-offs, the mandate becomes aspirational instead of operational.
iii. The “everyone thinks they agreed” effect
Boards and executives often assume shared interpretation. But mandates are not agreements — they’re hypotheses until tested.
If people can’t paraphrase the mandate the same way, it isn’t clear.
When the mandate is unclear, implementation can only approximate value, and teams will create their own direction to fill the vacuum. This isn’t resistance; it’s adaptation.
Clarity Requires Confronting Consequence
One thing I’ve noticed repeatedly is this: clarity forces consequence, and not all leaders are ready for consequence.
A clear mandate closes alternative paths. It defines what the organisation will not do.
That’s uncomfortable.
Leaders sometimes keep mandates vague not because they lack confidence, but because they unconsciously want to preserve optionality. But optionality held too long becomes hesitation, and hesitation is expensive.
A clear mandate has four properties:
i. It names the outcome.
Not “strengthen governance,” but “operate with a board-approved risk framework that reduces regulatory exposure by X.”
ii. It names the constraints.
Budget, timelines, political conditions, resourcing realities — declared upfront, not discovered midstream.
iii. It names the trade-offs.
If you want independence, you lose speed. If you want control, you sacrifice empowerment. Clarity articulates the cost.
iv. It names the non-negotiables.
People often treat non-negotiables as implied. They are not.
Stating them explicitly avoids months of friction and rework.
Clear mandates reduce the emotional labour of downstream teams.
Unclear mandates increase it.
The Real Work Is Upstream, Not Midstream
Most organisations tend to need independent clarity when the midstream symptoms show up:
failure to hit transition milestones
board frustration
regulatory escalation
teams spinning in activity loops
leadership questioning execution capability
But by the time these appear, the real work is already behind us. The upstream mandate was either insufficiently defined, or never socially validated. If you want to fix execution, you start at the top of the funnel:
Mandate articulation
— what exactly are we asking this organisation to become?
Mandate coherence
— do key leaders describe it the same way?
Mandate consequence
— do they understand and accept the trade-offs?
Mandate ownership
— who holds the decisions when friction emerges?
Mandate sequencing
— what must happen before anything else can succeed?
Without these, the organisation will build an execution plan on soft sand, and no amount of leadership enthusiasm can stabilise it.
Why Clarity Feels Confronting
Clarity isn’t intellectually difficult; it’s emotionally difficult.
A clear mandate does three things simultaneously:
Remove ambiguity
— which feels safe
Expose assumptions
— which feels vulnerable
Declare intent
— w(which feels binding
This is why organisations often stop short of naming the full mandate.
The fear of losing optionality outweighs the fear of losing effectiveness.
But clarity is not a constraint. It is a release valve.
It reduces organisational anxiety because people know what is expected and why.
I’ve seen morale lift in teams simply because someone finally said, “This is the real mandate, the thing we have to do. And here’s what it means for us.”
Where Leaders Misread the Problem
Three misdiagnoses appear over and over:
Misdiagnosis 1:
“The team isn’t executing well enough.”
Reality: the team is executing exactly what they were (implicitly) asked to do. And they are doing it with the skills and experience that the leaders know they have; with the tools issued to them; and with the last version of the map they were instructed was “current”.
Misdiagnosis 2:
“We need more governance.”
Reality: governance is often compensating for an unclear mandate. More people watching what you’re doing doesn’t necessarily mean that you’re doing the ultimately correct thing.
Misdiagnosis 3:
“We need different people.”
Reality: even the best people fail under ambiguous instruction. Replacing people is not a clarity strategy.
The Work of a Transition Advisor Is Mandate Work
My role is not to fix execution.
It’s to fix the upstream conditions that define the quality of today’s execution.
A transition advisor is, in effect, a mandate architect.
Someone who names what others can’t yet name, simplifies what’s become complex, and ensures decisions happen at the right altitude.
When leaders see the mandate clearly, they act differently:
decisions become faster
governance becomes lighter
teams become calmer
transitions stabilise
outcomes improve
Clarity is not reassurance. Clarity is alignment.
The Mandate Test
Before committing a team to action, leaders should answer five questions:
What are we actually promising to deliver?
What constraints shape this mandate?
What trade-offs are we explicitly choosing?
What becomes non-negotiable?
Can every decision-maker describe this mandate the same way?
If these questions can be answered cleanly, the transition has a chance.
If they can’t, the organisation is optimising for friction.
Closing
The true cost of unclear mandates is not financial.
It’s the momentum, alignment, and morale that organisations struggle to regain.
Clarity is the upstream intervention that prevents those losses.
In every transition I’ve worked on, the mandate is the leverage point — the place where consequence lives and where alignment begins. Talented teams can compensate for flawed mandates, but the cost is morale and energy.
When leaders commit to clarity, the organisation moves.
When they don’t, the organisation works for work’s sake.