Execution Drag · Work Demand · Capacity Intelligence™
The work got harder to execute before your people got worse at it.
Execution drag is the gap between the capability you are paying for and the output you actually get — and it is usually built into how work is routed, not into who is doing it.
The thing most operations never name
Execution drag /noun/
The slow, rough, late output that shows up when capable people are working hard but the work system is fighting them.
You can already see its effects — in your attrition, your rework, your stalled priorities. You just have not had a name to file them under, or a way to price them. So they get filed under whoever happened to be in the room. Name it, and you can finally manage it.
Drag has a direction. It runs one way.
The miss you notice at the end of the chain was set up at the beginning of it.
Starts here
Work demand design
How work is routed, how many decisions stack up, who it flows through, how much recovery is built in.
Lands on
The state people are in
Capable people end up in degraded states they did not choose, and the work does not account for.
Shows as
What execution looks like
Decisions slow. Rework climbs. Priorities stall. Strong performers turn uneven.
Ends as
What it costs
Attrition, redone work, missed signals, forfeited upside — most of it never reaching a dashboard.
Fix the front of the chain and the rest moves. Manage only the back of it and you pay for the same drag every quarter.
What you see vs. what the work system is doing
Every line on the left reads like a people problem. Read the right column before you act on the left one.
What you see
A strong performer's work turns uneven, quarter over quarter.
What's actually moving
Their skill has not changed. Their weeks are so full of meetings that they are now making decisions with no quiet time left to think them through.
What you see
A decision that should take a week takes six.
What's actually moving
Every path routes through one saturated manager. The bottleneck is the routing, not the person sitting in it.
What you see
A priority the whole team agreed on never goes live.
What's actually moving
No week ever holds enough uninterrupted capacity to finish it. It is losing to the noise, not to disagreement.
What you see
A clear customer signal gets noticed but never pursued.
What's actually moving
The team is spending its entire margin defending the current load. There is nothing left over to chase the signal with.
What you see
Your best manager becomes the bottleneck everyone waits on.
What's actually moving
Demand keeps getting added with no recovery between waves. Saturation looks like a performance issue. It is a load issue.
Sometimes the left column really is a people problem. The point is to stop assuming it — and to check the demand first.
Why your operating dashboards miss it
Most dashboards report the result after the cost is already spent. They can tell you a project is late, a decision got reversed, a team is behind. They rarely tell you which demand pattern caused it.
That is the missing layer. Capacity shows up in individuals, but demand is created by the work system. Look only at the individual and you miss the routing, the meeting load, the decision density, the unclear ownership, and the recovery gaps that made the miss likely in the first place.
Individuals manage their state. Managers manage the demand. We connect the two.
We do not call everything a capacity problem.
Plenty of misses are ordinary — a skill gap, a role mismatch, a genuinely bad call. Those are not demand problems, and we will say so. A pattern only counts as execution drag when all four of these hold.
Baseline shift
Capable people are performing below their own established level — not below someone else's.
Load signature
The miss shows up under identifiable demand pressure, not at random.
Shared conditions
The same pattern appears across people exposed to the same work design.
Reversibility
Performance recovers when the demand pattern changes — and only when it changes.
Four passes, not one. It is the test that keeps this honest — and the reason a no from us is worth as much as a yes.
This is not a fringe idea.
The pattern has been measured for two decades, and none of it is controversial. What is rare is someone who will price it for your specific team and redesign the routing — instead of booking another offsite and hoping it sticks.
Figures reproduced from the cited research, used as external corroboration. Emergent Skills measures your own operating data rather than asserting these numbers for your team.
Find the demand pattern behind the drag.
Tell us what you are seeing — slow decisions, climbing rework, a manager who has become a bottleneck, a priority that will not ship, capable people suddenly missing. We will tell you whether a half-day Work Demand Diagnostic is the right low-risk next step, and what a realistic output would look like.