Why Moving the Work Does Not Move the Ownership
A VP of Finance was promoted into the top finance seat after a high-priced CFO left. She was capable and she worked hard.
Her peers saw her as a gatekeeper.
Part of the reason was time. She did not have enough of it to help her colleagues work through financial issues. When she did engage, it was mostly to point out problems.
The only way to find that time was to get better at delegation. She did hand out work, mostly as end goals. When standards were even remotely at risk, she took the work back.
She was delegating tasks. The ownership had not moved.
Why busy delegators are still bottlenecks
Many successful executives believe they delegate well because they distribute a great deal of work. Their teams are fully occupied, and their calendars are still the constraint.
The mechanism is simple. Analysis and execution get assigned to other people, while every important decision stays with the executive. The work moves, but the responsibility keeps returning.
In a consulting engineering firm it is easy to spot once you look. The project manager runs the project, but any conversation with the client about scope still goes through the VP. Judgment calls on the design wait for a sign-off from the same person.
The people underneath complete their assignments. They never get the chance to exercise judgment or own an outcome, so they do not learn to.
What is happening is easy to misread. The firm sees a leader who is stretched and a team that is waiting, and it concludes the leader needs more people. More people add volume to the same bottleneck.
Then comes the feedback. Delegate more.
That instruction is accurate and it will not change anything, because the leader is already delegating tasks.
The difference between moving work and moving ownership
A piece of work is a task with instructions. Ownership means an outcome, the decisions that go with it and a named person accountable for the result.
There is a quick way to tell which one moved. When something goes wrong, who gets the call? If the client still phones the VP, the VP still owns it, whatever the org chart says.
A second test is what happens when the plan has to change halfway through. If the person doing the work has to come back for permission, they were given a task.
The finance leader had a different version of the problem. She handed her people end goals without the how-to direction they needed to act. On paper that looks like ownership. In practice it left capable people with a target and no clear way to reach it.
Moving ownership does not mean stepping away. In her case part of the fix was breaking goals into steps and sequences the team could actually execute.
Seven questions that turn delegation into an operating framework
Delegation that works is a designed system, with decision rights and check-in points agreed before anything moves.
These are the seven questions I work through with a leader to build it:
What responsibility should be transferred?
Who should own it?
What decisions can that person make?
What outcome will that person be accountable for?
How often should the executive check in?
When should the executive intervene?
How will the executive avoid taking the responsibility back when pressure rises?
Most people picture the first two when they hear the word delegation. Whether it holds depends on the other five.
Question three does most of the work. If the new owner can approve scope changes up to a set value, write the number down. If client escalations above a certain level still come to the executive, say which level. Anything left vague gets settled by habit, and habit sends it back up.
The check-in cadence matters because it replaces the informal version. A leader with no scheduled way to see progress will find an unscheduled one, usually by stepping into the work.
Intervention needs a trigger agreed in advance, such as a missed milestone or a budget variance past an agreed point. When the trigger fires, the executive steps in. Otherwise they stay out.
The seventh question gets its own section. Pressure is where delegation plans get tested.
Why leaders take responsibility back when the pressure rises
The executive agrees that ownership should be delegated. Then an important client becomes unhappy, and the responsibility comes straight back.
For a strong technical leader, taking it back feels like the responsible move. They can fix the problem faster than anyone on the team. The client gets a quicker answer, and nobody questions it in the moment.
Each take-back teaches the team something. The ownership was provisional. It lasted until things got hard. Next time the pressure rises they will wait for the executive to step in, and they will be right to.
The finance leader took work back whenever standards were even remotely at risk. Two other habits sat alongside that one. She avoided difficult conversations. She judged performance in black and white rather than coaching people up.
So we replaced the reflex with a system. Performance issues got handled objectively against a standard instead of personally. Underperformers who had potential got coaching and clear timelines for improvement. She was also prepared to replace chronic underperformers who did not respond. And she put a system in place for monitoring progress.
What changes in the business when ownership actually moves
Her reputation with her peers improved. They noticed the extra time she spent with them looking for solutions instead of pointing out problems. The gatekeeper became an implementation partner.
Her own team changed too. People owned their work, operated more independently and got more productive.
That is the pattern when ownership moves. The executive's time goes to the work only they can do. The people underneath start making decisions, which is the only way anyone learns to make them.
Gallup put numbers on a version of this. It studied 143 CEOs from the Inc. 500 list of fast-growing private companies. Companies run by CEOs with high delegator talent averaged three-year growth 112 percentage points higher than those run by CEOs with limited or low delegator talent. They also generated 33 percent more revenue.
Those were fast-growing private companies, and Gallup was measuring a talent rather than a practice. It is a different population from an engineering firm.
For a consulting engineering firm the bigger payoff is the bench. People who have owned outcomes are the people you can promote. Someone who has only completed assignments will be described as not ready, and nobody will be able to say exactly why.
Is one of your leaders the constraint on their own team?
If a strong leader's team is busy and their calendar is still full, the ownership has not moved.
The fix starts with one responsibility. Name it, name who should own it and work through the seven questions before anything changes hands.
A short conversation can build that plan, including what keeps the responsibility from coming back the first time a client gets unhappy.
Comments