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 routinely assume the implementation team is the problem: they increase oversight; they add reporting; they commission self-justifying diagnostics. These responses often stabilise the very dynamic that caused the issue in the first place, a belief that clearer or more 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. Clients expect more for less.
Somewhere in that mix, the true north becomes obscured. 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.
Leaders often know the external pressures shaping a decision but hesitate to name them. They want strategic freedom without acknowledging the regulatory, financial, or political boundaries that actually constrain it. If those constraints go unspoken, teams end up building plans on false space.
Every transition also involves a sacrifice: speed against accuracy, cost against capability, compliance against autonomy. When leaders refuse to surface these trade-offs, the mandate stays aspirational instead of becoming operational.
And boards and executives often assume a shared interpretation exists when it doesn't. A mandate is not an agreement. It's a hypothesis, until it's been tested. If the people responsible for it can't paraphrase it the same way, it isn't clear yet - whatever the meeting minutes say.
When the mandate is unclear, implementation can only approximate value, and teams will quietly build their own version of the direction to fill the vacuum or to make sense of what they think they’re being asked to do. This isn't resistance. It's adaptation.
Clarity Requires Confronting Consequence
Clarity forces consequence, and not every leader is ready for consequence. A clear mandate closes off alternative paths. It defines what the organisation will not do. That's uncomfortable, and 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 mandate only becomes clear once it names the actual outcome. For example, not "strengthen governance," but something closer to “operating within a board-approved risk framework that reduces regulatory exposure by [a defined amount]”. It has to name the real constraints. Budget, timelines, political conditions, resourcing realities, and the like should all be declared upfront rather than discovered midstream. The mandate has to name the trade-offs being made, because independence costs speed and control costs empowerment, and clarity is what makes that cost visible rather than assumed. And it has to name what is genuinely non-negotiable, because people treat the unstated as implied when it isn't, and that gap is where months of friction and rework quietly accumulate.
Clear mandates reduce the emotional labour of downstream teams. Unclear ones increase it.
The Real Work Is Upstream, Not Midstream
Most organisations reach for independent clarity once the midstream symptoms are already showing: missed transition milestones, board frustration, regulatory escalation, teams spinning in activity loops, leadership starting to question the team's capability to execute.
But by the time these appear, the real work has already moved. Not gone. Just elsewhere. And earlier than where most people are still looking for it. The decision point that mattered has passed, which doesn't mean the chance to fix things has passed with it. It means the fix now has to happen at a new decision point, further upstream than anyone expected to have to go.
Fixing execution starts at the top of the funnel. Whether the mandate has actually been articulated, and in language specific enough to mean something. Whether the leaders who hold it would describe it the same way if asked separately. Whether the trade-offs inside it are understood and genuinely accepted, not just nodded through. Who actually holds the decision when friction surfaces. What precisely has to happen when before anything else downstream can succeed.
Without that groundwork, what looks like an execution plan is a plan in name only. No amount of leadership enthusiasm will make it work. Enthusiasm doesn't improve a plan. It just executes a bad one faster.
Why Clarity Feels Confronting
Clarity isn't intellectually difficult. It's emotionally difficult.
A clear mandate does three things at once. It removes ambiguity, which feels safe. It exposes assumptions, which feels vulnerable. And it declares intent, which feels binding.
This is why organisations so often stop short of naming the full mandate. The fear of losing optionality outweighs the fear of losing effectiveness.
But clarity is a release valve, not a constraint. It reduces organisational anxiety, because people finally know what's expected of them and why. I've seen morale visibly lift in a team the moment someone finally said, “This is the real mandate, the thing we actually have to do, and here's what it means for you.”
Where Leaders Misread the Problem
The same misdiagnoses appear over and over.
“The team isn't executing well enough”, leaders will say. But more often, the team is executing exactly what it was implicitly asked to do — with the skills it has, the tools it was issued, and the last version of the map it was told was current.
“We need more governance”, is the second instinct. But governance is frequently compensating for an unclear mandate. More people watching what you're doing doesn't mean you're doing the right thing.
“We need different people”, is the third. But even the best people fail under ambiguous instruction. Replacing people is not a clarity strategy.
Mandate Work
My role isn't to fix execution. It's to fix the upstream conditions that determine the quality of today's execution: naming what others can't yet name; simplifying what's become complex; and making sure decisions are happening at the right altitude.
When leaders see the mandate clearly, they act differently. Decisions move faster. Governance gets lighter rather than heavier. Teams settle. Transitions stabilise. Outcomes improve.
Clarity is not reassurance. Clarity is alignment.
Before committing a team to action, it's worth a leader asking some plain questions. What they are actually promising to deliver? What constraints genuinely shape it? What trade-offs are being chosen rather than avoided? What has become non-negotiable? Can every decision-maker in the room describe the mandate the same way if asked alone?
If those questions can be answered cleanly, the transition has a chance. If they can't, the organisation is optimising for friction, however busy it looks.
Closing
The true cost of unclear mandates isn't financial. It's the momentum, alignment, and morale that organisations struggle to regain once they've been spent chasing the wrong problem.
Clarity is the upstream intervention that prevents those losses. In every transition I've worked on, the mandate has been the leverage point: the place where consequence lives and where alignment begins. Talented teams can compensate for flawed mandates for a while, but the cost is morale and energy, and it's paid quietly.
When leaders commit to clarity, the organisation moves. When they don't, the organisation works for work's sake.