People cannot own outcomes when every decision still waits for permission.
A capable employee spots a customer problem.
They understand what happened. They know the sensible next step. The decision is small, reversible and well within what most customers would consider reasonable.
But they cannot make it.
They ask the team lead. The team lead asks the manager. The manager wants to check with a director because the situation is slightly outside the normal process.
By the time the approval arrives, the customer has called again, the employee has repeated the story to three people, and a ten-minute recovery has become a two-day organizational event.
Then someone asks why employees are not showing more initiative.
I think we sometimes want the behaviour of ownership without creating the conditions for it.
We tell people to think like owners. We encourage them to use judgement. We put empowerment into values statements and leadership presentations.
Then we route every meaningful decision upward.
An approval queue is not just a process. It is a lesson in who is allowed to think.
Employees learn that lesson quickly.
They learn that acting carries personal risk, while waiting distributes the risk upward. They learn that a delayed decision is usually safer than a reasonable decision someone later questions. They learn to arrive at meetings with recommendations, but not commitments.
Eventually, capable people stop deciding before they stop caring.
That distinction matters.
The employee may still be engaged. They may still want the customer to have a good outcome. They may still see exactly what needs to happen.
What has disappeared is not motivation. It is permission.
This is where engagement, enablement and empowerment separate.
Engagement says, “I care.”
Enablement says, “I have the information, tools and support to act.”
Empowerment says, “I know which decisions are mine.”
If decision rights are unclear, the organization does not create healthy caution. It creates learned dependency.
People cannot be accountable for outcomes while being trained to wait for permission.
This does not mean removing controls or encouraging people to improvise beyond their competence. Some decisions carry legal, financial, safety or reputational consequences and should have deliberate oversight.
But many approval layers are not controls. They are accumulated habits. A past mistake created another sign-off. An anxious leader kept one more decision. An exception became a permanent meeting. Nobody revisited the design.
The result is a management system that treats every employee as both responsible and not quite trusted.
The practical question for leaders is not, “How do we get people to take more ownership?”
It is, “What decisions are we asking people to own—and which of those are they actually allowed to make?”
That question leads directly into first-line management systems.
Roles should define decision rights, not only responsibilities. Processes should distinguish routine judgement from genuine exceptions. Meetings and escalation paths should resolve the few decisions that need elevation, not become the default route for ordinary work. Reporting should show outcomes and patterns, so leaders can adjust boundaries without taking every decision back.
Empowerment does not begin with a speech about trust.
It begins when a capable person can make a sensible decision, within clear boundaries, and knows the organization will support responsible judgement.
If approval queues are teaching your people to wait, the issue may be in the management architecture surrounding the work. The 7 Essential First-Line Management Systems explores how clear roles, workable processes, useful measures and improvement routines create the conditions for genuine empowerment: www.imadlodhi.com/flm1
