Work Demand · Stalled Priority Snapshot · Where Work Stalls. What It Costs.
Before you blame the people, trace the path.
Execution drag can arise from several conditions. Emergent Skills examines two of them: friction in the work path, and demand conditions that can reduce access to existing skill. The Snapshot starts with the path, because the path can be examined directly.
In 90 minutes we reconstruct how one result actually moves across functions, put a conservative number on the friction with every assumption shown, and leave you with one change to test in the next two weeks. $1,500, fixed scope.
Executive summary What it is, when to use it, what it produces, and where it stops.+
What it is. Ninety minutes on one result that should have moved. The people who move, approve, or unblock it reconstruct the route in the room. We tag every step as work or waiting, name what is most likely holding it up, put a conservative number on the extra labor, and define one change to test in the next two weeks. $1,500, fixed scope.
Why it exists. Status meetings return three explanations for the same delay: capacity, competing priorities, waiting on legal. All three are partly true. None of them says what to change on Monday. The route is the part that can be examined directly, because waits, queues, approvals, handoffs, and rework are visible in the work itself.
When to use it. One result is materially late, has restarted, or keeps waiting on an approval that slides. Or nothing has gone wrong yet, and something with a real date has to clear the same functions a comparable piece of work already cleared. That completed route is the baseline for the next one.
What it produces. A work-path map with disputed steps marked uncertain. The pattern behind the delay. The hours you can defend, with the arithmetic and the confidence level shown. One 14-day experiment carrying an owner, a metric, a target, and a decision rule.
What it does not do. It does not forecast. It does not assess an individual. It does not reconstruct an entire enterprise program, and it does not force every stalled result into a work-path explanation. Priority choice, capability, funding, and external dependencies get checked first. When one of those explains the stall better, the read says so.
Where it stops. One session reads one route and establishes what that route cost once. Whether other priorities travel it is a separate question, and at enterprise scale usually the larger one.
Best fit when one result that should have moved is: materially late, restarted more than once, waiting on an approval that keeps sliding, crossing at least two functions or decision points, gated by a committee that meets on a fixed cadence, or stuck behind one person who is the only route through. Someone owns the result and can test a routing change within 30 days.
Also a fit before anything has gone wrong. Something dated is coming. A launch, an integration, a compliance deadline. It has to clear the same functions that a comparable piece of work already went through. We trace the completed one to establish an internal baseline, which shows what the next one is likely to encounter if the route stays as it is. Nobody has to concede that anything went wrong to get it.
The situation
You already know it is late. Nobody can tell you why.
You have asked in three status meetings and gotten three different answers: capacity, competing priorities, waiting on legal. Each one is partly true. None of them tells you what to change on Monday.
Each person sees the part they touch. The approval that came back twice. The review that sat in a queue in another department. The cycle lost because one committee slot was missed. Nobody sees how the whole route connects, so the conversation drifts toward who is not delivering, which is the most expensive conclusion to get wrong and the hardest one to support.
People are usually the first explanation offered. The path is the one that can be examined directly: waits, queues, approvals, handoffs, and rework are visible in the work itself, without anyone's assessment of anyone. That is where we start. If the route does not explain the stall, the read says so.
The same is true before anything is late. If something with a real date has to clear the functions a comparable piece of work already cleared, that completed route is your baseline. It is knowable now, while there is still time to change it rather than explain it.
One end-to-end view
The people who do, move, and approve the work reconstruct the full route together: handoffs, approvals, waits, loops, restarts, and meeting cycles. In a large organization no single function holds that view.
Something concrete to argue with
The read gives the room a shared object: the route, what is most likely holding it up, the hours you can defend, and the proposed test. The work is the subject, not the character of the people in it.
The sample read
See the deliverable before you buy it.
Northline Group is invented: about $2B in revenue, roughly 9,000 employees, dozens of departments, built from patterns that recur in large organizations. Every figure below is illustrative. What is real is the format. This is exactly the read that arrives within 24 hours, at exactly this level of detail.
The invented case: a Q1 pricing and packaging change that was supposed to be live by the end of the quarter. Intended path was Pricing drafts, Finance reviews margin, the Pricing Council approves, it goes live for new contracts. Ten people ended up in the route. Three of them were in the room. Here is what the read found.
The path: 12 steps, 119 calendar days, 13 percent flow efficiency
Six days produced the initial draft. About five days more went into revisions, margin analysis, and contract language inside the loops. That is 88 hours of hands-on work, or 11 active working-day equivalents, against roughly 85 available working days, which is where the 13 percent comes from. Of the 119 elapsed days, 71 were spent purely waiting.
The pattern: serial gating
Finance, Legal, and Compliance each reviewed in sequence rather than in parallel, and every reopened item restarted the sequence. Worst chokepoint at step eleven, where missing a single Pricing Council slot cost a full cycle.
The number: $45,900 to $81,600
Direct extra labor only, medium confidence, with the arithmetic on the page: four people carrying the work at three to five extra hours a week, plus six approvers and reviewers at one to two, at $150 loaded across 17 weeks. Carriers and approvers are counted separately because they were not engaged at the same intensity.
What the two numbers say together
About 11 active working days went into the work. Thirty-eight to sixty-eight person-days went into moving it through the gates. Three to six times more effort went into routing the priority than into doing it, and the ratio widens with every approver added. The dominant delay was waiting and repeated gating in the route, not the hands-on work.
What is reported separately, and never added in
The 119 days of elapsed delay are shown on their own and never priced into the labor figure. Where a client supplies the basis, missed value is reported separately too: in this invented case, about $7.5M of Forfeited Upside exposure, from roughly $2B in revenue at 1.5 margin points, one quarter late. That figure is the client's assumption, not our finding, and it is not part of the number above.
The test: parallel review instead of serial
Run the Finance, Legal, and Compliance reviews in parallel against one consolidated comment deadline, and give Pricing a pre-cleared margin and contract-language band so only out-of-band items reach the Council. Metric: number of sequential gates, median gate wait, and scope reopens. Target: one Council pass, gate wait of five business days or less, no more than one reopen. Decision rule at day 14: if the targets hold, standardize parallel review for this class of change. If not, test the Council cadence itself.
The full written read Here is a sample readout+
The read is organized so it can be handed to an executive who was not in the room. Page one is what stalled and the route it took. Page two is the pattern, the associated Capacity Tax exposure named separately from the causal finding, the estimated cost with its arithmetic and confidence level, and the elapsed delay reported outside that figure. Page three is the 14-day routing experiment with its change, owner, metric, target and decision rule, and the verdict on whether the Work Demand Diagnostic is warranted.
A twelve-step path does not fit legibly on one page. Where a route is shorter, the read is shorter.
What you leave with, and what it costs.
- A work-path map for the result with every step tagged, showing hands-on work against waiting, and anything disputed marked as uncertain.
- What is most likely holding it up, the pattern behind that, and the evidence for the conclusion, in plain language.
- The hours you can defend, with the assumptions, math, and confidence level shown, and elapsed delay reported separately.
- One 14-day routing experiment: the exact change, the owner, the metric, the target, and the decision rule.
- A straight verdict, including the finding that the route does not explain the stall when the evidence points elsewhere.
- The map and the number in the room. The written read within 24 hours, a 15-minute readout for the executive who owns the result, and a brief follow-up after the test window.
$1,500, fixed scope. No follow-on commitment, and the full $1,500 credits toward the Work Demand Diagnostic if you book it within 30 days.
How the session runs
90 minutes. One priority. One result that should have moved.
Bring the milestone, decision, deliverable, or dependency that should have moved next, and up to three people who move, approve, or unblock it. At least one should touch the work directly. Include the approver when decisions routinely wait on them. A whole enterprise project is too large to reconstruct properly in 90 minutes. One blocked result is not.
A route involving ten people can usually be reconstructed to a useful first-pass map by three who sit at different points along it. Nobody prepares anything: the sequence and the dates are reconstructed in the room, out loud, from what people remember, and any disputed step or date is marked as uncertain rather than treated as fact. That is the method, not a shortcut.
We frame what should have moved and by when, walk it step by step along the route it took, tag where it waits and loops and changes hands, name the condition most likely controlling progress, and put a conservative number on the extra labor. The last ten minutes belong to the people closest to the work, who define one exact routing change, one owner, one metric, and what would count as evidence for or against it.
Worth saying plainly: the fee is not the whole cost. Ninety minutes from three people is roughly another $700 of internal time at a $150 loaded rate, so the real figure is nearer $2,200. That is about the cost of one of the status meetings already being held about it, and we would rather you ran that arithmetic with us than after.
A fair question
What if the chokepoint turns out to be me?
Then you find out first, in a room you convened, from a document you control. The read describes the route the work takes. It does not rate a person, and it produces no input to any performance process. If the strongest pattern is an approval you own, that is the most useful outcome available, because it is the one change you can make on your own authority inside 14 days.
No HR process, employee data, dashboard pull, or system access is involved at any point. You decide who sees the read and when.
Who runs the session
Jim Wilde, founder, Emergent Skills.
Decades building and supporting enterprise systems across three companies, including nine years on mta.info and the real-time subway information systems behind the platform countdown clocks.
That work was queues, handoffs, and routing under real load, where a delay anywhere is visible to everyone standing on the platform. The Snapshot applies the same read to the work paths inside your organization.
Where this sits
Start here when there is one route you can reconstruct.
Use the Work Demand Diagnostic ($3,500 to $7,500) instead when the drag spans many priorities, there is no single route or target date, or formal data analysis is already required.
One Snapshot establishes a rate: what one result cost moving through one route. It does not establish how many other priorities use the same route. In an organization with dozens of departments that second question is usually the larger one, and it is the question the Diagnostic answers.
Method Notes What is checked before the route, how the Five Capacity Taxes are handled, and where the Snapshot stops.+
Before classifying the route. The Snapshot first checks whether the intended outcome is still valid, whether leadership still treats it as a genuinely chosen priority, whether the required capability, information, authority and funding are available, and whether an external dependency controls the pace. If one of those explains the stall better than the route does, the read says so. The Snapshot does not force every stalled result into a work-path explanation.
The Taxes come after the pattern, never before. The Five Capacity Taxes are overlapping cost lenses, not root causes. The Snapshot identifies the work-path pattern first, then connects it to the associated exposure. The Taxes are not added together.
Three can be screened from path evidence: the Meeting Tax as coordination cost, the Decision Density Tax as quality and rework cost, and the Manager Load Tax as delay and queue cost.
Two are held as downstream exposure only: Recovery Debt, which is attrition exposure and needs turnover and longitudinal data, and Forfeited Upside, which is missed-value exposure and can only be valued from your pipeline and your assumptions.
The math is deliberately conservative. The visible drag floor counts directly traceable extra labor only. Elapsed delay and client-supplied opportunity value are shown separately and never folded in. Where a route involves people at different levels of engagement, they are counted at different intensities rather than averaged.
Where the Snapshot ends. It asks whether one work path supports a credible local routing hypothesis worth testing. It does not run the full evidence set that a claim about capacity would require, does not classify the wider performance problem as capacity-driven, and does not establish a measured execution outcome. If the path evidence is weak, the read says so and names the next question to ask: priority choice, definition of the work, capability, sponsorship, or an external dependency. It does not imply that some other cause has been proved.
Not ready to book
Run the first fifteen minutes yourself.
The Execution Drag Checklist walks the same opening questions we use to frame a result that has not moved. It will not give you the route or the number, but it will tell you whether you have a case worth tracing. Download the checklist.
Start with one result
One result. One route. One next move.
Bring the milestone, decision, or deliverable that should have moved by now, or the one that has to move next. You leave with the route it actually takes, the hours you can defend, and one change to test in the next two weeks.