What Happens When Decisions Move at the Right Level

He wasn’t expecting what he found.

Daniel had been tracking his escalations for three weeks,  not because it was a formal process, but because something hadn’t been adding up. Twelve issues had reached his desk in the past month. Different projects. Different teams. The same instinct: bring it to Daniel.

He’s VP of Operations at a Western Canadian energy services firm. Twenty-two years in the industry. The kind of leader who’s genuinely good at having the answer. So his team had learned, reasonably enough, to bring things to him.

When we sat down in week three and worked through the twelve together, what each one was, who had brought it, whether it genuinely needed VP involvement, the pattern became clear.

Nine of the twelve could have been resolved at the supervisor or site-manager level. With the right framework and the right operating culture around them, those nine decisions belonged closer to the work.

‘I’d never actually thought about it this way before,’ Daniel said. Not as a criticism of himself. As a genuine observation. ‘I wonder how many of those people could have handled it and didn’t know they were expected to.’

That question,  what would happen if your operating culture trusted people to decide at the right level,  is the most interesting one in most technical businesses. And very few leaders have actually run the experiment.

The capability is already there. The operating culture is the next step.

The technical businesses I work with,  energy services, construction, engineering, industrial operations,  almost universally have capable people. Strong systems. People who know their work. The question that opens up once the technical foundation is solid is a different one: how does the operating culture around those people help them make decisions, surface problems early, and hold accountability at the level where the work actually happens?

That’s the frontier most technical businesses haven’t deliberately crossed yet. Not because they aren’t ready, because nobody has mapped the terrain.

The result is what we call key-person dependency: a handful of senior leaders carrying decisions, conflicts, and problem-solving that the culture should be distributing closer to the work. The organization’s capacity to grow is real. The operating culture is what determines whether that capacity reaches the people who need it.

What senior leaders in technical businesses say when the operating culture shifts:

• “My team is making calls I used to make, and getting them right.”
• “Problems are reaching me earlier than they used to. I actually have time to do something about them.”
• “I went away for two weeks and came back to a brief. One decision was waiting. It was the right one.”

These are operating outcomes,  more achievable than most leaders realize.

Where the operating opportunity is,  in numbers

The financial case for building stronger decision velocity is real,  and rarely calculated. Here’s what the numbers look like in a typical technical business.

Executive time returned.

In a 100-person technical business, at an average loaded cost of $150 per hour for VP-level time, one escalated decision consuming forty-five minutes costs $112. Multiply that by the volume of decisions that could have been made at the level below in a given month, and you’re looking at a meaningful annual return,  in senior leadership time alone,  when the operating culture is built to distribute those calls.

Decision velocity.

In construction and energy services, a decision that moves at the right level keeps a project moving. A decision that waits for a VP who’s in back-to-back meetings until 3pm stops it. That latency rarely shows up on the accountability system,  it shows up in the project debrief, attributed to ‘coordination challenges.’ Building the operating culture to move decisions closer to the work is one of the most direct levers on project delivery.

Early problem surfacing.

A quality defect caught at the supervisor level costs a fraction of what it costs when it reaches the client. A performance concern addressed in week two costs less than the exit and replacement process it becomes in month six. The operating culture that makes early disclosure safe,  where raising a concern is seen as doing your job, not causing a problem,  is worth more than most organizations have calculated.

What accountability looks like when it’s built into the operating culture

When accountability is inconsistent across a team or site, the instinct is to look for the right person to hold it. Some managers are good at it. Others aren’t. The solution appears to be finding better managers, or running an accountability training programme.

Neither of those addresses what’s actually happening. Accountability varies because the operating culture hasn’t yet built the conditions that make consistent accountability possible: decision rights clear enough to be owned, commitment frameworks specific enough to be measured, and an environment where surfacing a problem early is genuinely safer than managing it quietly.

The organisations that build strong accountability cultures do three things consistently. They make decision rights explicit — not as a policy document, but as a living conversation revisited when roles and structures change. They build a shared commitment standard: not ‘do your best,’ but a specific picture of what ownership looks like. And they change the leadership reflex when problems are raised early. Curiosity first. Problem-solving second. That reflex, made consistent, changes what people are willing to surface.

The Culture Capacity Scan, your operating baseline

The Culture Capacity Scan establishes a baseline across five operating dimensions: decision velocity, accountability follow-through, problem-surfacing speed, leadership depth, and operating rhythm reliability.

It gives you a clear picture of where decisions are moving and where they’re waiting,  not as a leadership assessment, but as an operating diagnosis with three to five agreed indicators to track as the culture improves.

This is the starting point for every significant Sage & Summit engagement.

What Daniel’s organization found,  and what changed

The nine-out-of-twelve pattern gave Daniel’s organization a starting number. Over the following ninety days, working with his leadership team on decision rights, commitment clarity, and the habit of early problem-surfacing, the count changed.

By week twelve, seven of the twelve recurring issue types were being resolved at the supervisor or site-manager level without reaching Daniel. Not because the supervisors had become more capable — they were always capable. Because the operating culture had been built to let them be.

The metric Daniel tracks now isn’t engagement or leadership confidence. It’s the weekly escalation count and the percentage of site-level decisions that reach his desk. Those two numbers tell him more about the health of his operating culture than any survey.

If you’re curious about what your escalation count would tell you,  the Culture Capacity Scan gives you the baseline. Fifteen questions across five dimensions. The starting point for a different operating picture.

If you’d like to go deeper on what leadership culture cost looks like in numbers,  the July Week 1 article covers the full calculation.