Decision Authority: Give Routine Decisions Somewhere to Go
A project manager needs an answer on a replacement supplier. The original supplier has missed a delivery, the alternative meets the specification, and the purchase fits the approved budget. The request still waits in the owner’s inbox.

Meanwhile, the crew needs a revised sequence. A customer update is delayed. Three people follow up on the same question.
This is an illustrative situation, but the operating question is concrete: what prevented the manager from deciding?
A reminder to take more ownership will achieve little if the manager has never been told where their authority begins and ends. Define decision authority for that recurring decision.
Find the approvals that keep returning
For five working days, record each request that reaches the owner. Capture the decision requested, when it arrived, when it was answered, who had the information, and what waited for the answer.
Keep the record factual. An approval that took two days may have involved a genuine risk. Another may have taken two days because it arrived between meetings.
At the end of the week, group similar requests. Supplier substitutions, schedule changes, small purchasing exceptions and routine customer adjustments may appear repeatedly. Start with one category that is common, reasonably predictable and suitable for a manager’s authority.
This exercise makes the discussion easier. Instead of asking an owner to relinquish an undefined amount of control, the team can examine a specific class of decisions.
Define decision authority before transferring the decision
A usable decision rule answers six questions:
What event triggers the decision?
Which role makes the final call?
What information must that person review?
Which limits apply?
What circumstances require escalation?
Where will the decision be recorded?
Bain’s decision-making guidance distinguishes roles in recommending, contributing to and making decisions. That distinction matters even when a business uses a much simpler format: being consulted should not quietly become an extra approval step.
Consider a sample supplier rule. A project manager may select a replacement from an approved list when the specification is unchanged, the purchase stays within the agreed budget, and the delivery change does not alter a customer commitment. A specification change, budget exception or customer deadline change goes to the designated operations leader.
Those conditions are illustrative. The company should set its own boundaries based on its contracts, controls and people.
Give the manager the information needed to act
Authority without context creates a different delay. The manager may be permitted to decide but unable to see the budget, supplier requirements or latest customer commitment.
Before the rule goes into use, check the information path. Can the manager find the current specification? Does the purchasing record show what has already been committed? Is there one place to confirm the delivery promise?
Access and training belong in the rollout. Otherwise the team may keep seeking approval simply to obtain information.
Also tell the people affected by the change. Purchasing should know whose decision it can accept. Finance should understand the limit. The owner should know which exceptions will still arrive.
Review judgment without retaking every decision
During the first few weeks, review a small sample of completed decisions. Ask whether the manager used the agreed information, stayed within the limit and raised exceptions early.
A different choice from the one the owner would have made is not automatically a failed decision. Examine the reasoning and result. If a reasonable decision fell within the rule, support the authority that was given.
If the rule missed a predictable situation, amend it. If the manager needs more coaching, provide it. If a control failed, address the control directly.
This is where delegated authority becomes credible. Managers need to see that the written agreement will hold when they actually use it.
Measure the waiting and the quality together
Track the time from a complete request to a decision. Count routine requests that still reach the owner. Review rework, budget exceptions or customer problems connected to the new arrangement.
A fall in owner approvals is useful only if the decisions remain sound. Faster movement with repeated correction is a signal to investigate.
Keep the first change small enough to evaluate. One decision category with a clear owner, a workable boundary and a short review cycle can teach the business more than a large authority chart that nobody uses.
PSG’s article on building a company that does not depend on the owner explains the broader challenge. The next step is practical: take one recurring approval from last week and write down how it should move next week.
If repeated approvals are slowing your team, talk with Joel Kahn about how fractional operational leadership could help clarify authority and follow-through.



Comments