Power Shifts When Control Stops Working: Leadership in the Age of AI
For a long time, leadership and control were closely linked.
Not always explicitly.
But structurally.
Leaders were expected to:
- assign work
- track progress
- remove blockers
- ensure delivery
And that made sense.
Because execution was the problem.
Control Was a Rational Strategy
If work is:
- slow
- complex
- dependent on individuals
Then control becomes a way to reduce risk.
You define:
- who does what
- when it should be done
- how progress is measured
In many environments I’ve worked in, this showed up in very familiar ways.
Detailed Jira workflows.
Weekly status reporting.
Milestone tracking with increasing pressure as deadlines approach.
Not because people loved control.
But because without it, delivery felt unpredictable.
When Execution Stops Needing Control
Now compare that to what’s happening today.
Execution is getting:
- faster
- more standardized
- partially automated
A developer can scaffold solutions in minutes.
A product idea can be explored and visualised within hours.
Analysis that used to take days can be generated instantly.
You don’t need the same level of control
when the cost of doing something drops that much.
And that creates tension.
Because the system still behaves as if control is required.
The Moment Control Becomes Friction
This is where things start to break.
Control doesn’t just become unnecessary.
It starts to slow things down.
I’ve seen situations where:
- a team could move quickly, but waited for approvals
- insights were available, but had to be “validated” through layers
- simple changes got stuck in process rather than execution
The irony is hard to ignore.
The capability to move is there.
But the system prevents movement.
Not because of technical limitations.
But because control is still embedded in how decisions are made.
Why We Hold On to Control
Letting go of control is not just an operational change.
It’s psychological.
Control provides:
- a sense of responsibility
- a way to demonstrate leadership
- a mechanism to reduce uncertainty
If you’re accountable for outcomes, controlling execution feels like the safest path.
I’ve been in conversations where leaders said:
“If I don’t check this, how can I be sure it’s done right?”
It’s a fair question.
But it’s based on an assumption that is becoming weaker:
That quality and outcomes depend on direct oversight.
From Controlling Work to Shaping Direction
If control over execution loses relevance, leadership has to shift.
Not toward less responsibility.
But toward a different kind of responsibility.
From:
- controlling tasks
- monitoring progress
- enforcing structure
To:
- setting direction
- defining clarity
- enabling decision-making
In practice, this looks different than most people expect.
It’s less about asking:
- “Are we on track?”
And more about asking:
- “Are we solving the right problem?”
Where Power Actually Moves
Power doesn’t disappear. It moves.
Away from those who:
- control execution
- manage tasks
- oversee processes
Toward those who:
- frame problems clearly
- make meaningful decisions
- connect people and context
This is subtle. Because titles don’t change immediately. But influence does.
A Pattern I Keep Seeing
In several environments, there’s a recurring situation.
Teams are capable of delivering quickly.
They have the tools, the skills, the support.
But they hesitate.
Not because they can’t execute.
But because:
- direction is unclear
- decisions are delayed
- priorities shift without explanation
In those moments, leadership becomes the bottleneck.
Not execution. Not capability. But clarity.
What Leadership Starts to Look Like Instead
If execution is no longer the main constraint, leadership becomes less about control and more about orientation.
It shows up in small but important shifts.
Instead of reviewing every detail, you:
- create clarity on what matters
- define what “good” looks like
- make trade-offs explicit
Instead of tracking progress constantly, you:
- trust shorter feedback loops
- encourage decisions at the right level
- intervene when direction drifts, not when activity slows
This is less visible work.
But more impactful.
The Risk of Doing Nothing
If leadership doesn’t adapt, something else happens.
Control structures remain.
Execution accelerates.
And the gap widens.
You get:
- fast teams in slow systems
- high output with low impact
- frustration on both sides
Because people feel they could move faster…
But aren’t allowed to.
A Subtle but Important Shift
This is not about “empowering teams” in the usual sense.
It’s not a slogan.
It’s a structural necessity.
Because when execution becomes cheap and fast:
The cost of wrong direction becomes higher than the cost of wrong execution.
And that’s where leadership matters most.
Closing Thought
Control made leadership effective in a world where execution was hard.
But when execution becomes easier, control loses its leverage.
Leadership is no longer about making sure work gets done.
It’s about making sure the right work gets done.
