Stalled business results, investigated and explained.
The project is falling short.
You’re the one explaining why.
Another status meeting. Different explanations from each team. You still need to decide what happens next.
Emergent Skills investigates two routes into execution drag: where the work itself is obstructed, and whether the demands around that work are contributing to errors, rework, reversals, or missed handoffs. You get a written finding and a recommended next step you can put in front of the person asking. Start with one priority through the Stalled Priority Snapshot.
$1,500 USD fixed · Written input from 6–8 project contributors · 90-minute working session with up to 3 participants
Led by Jim Wilde: decades in enterprise systems, nine of them as a lead consultant at the MTA on mta.info and the NYC subway countdown clocks.
Two routes into execution drag
The work path can create drag. The demands around it can create more.
Route 1
The work path
Work waits in queues, stalls at handoffs or approvals, or comes back for rework.
Trace where delivery is obstructed. A finding about the work path stands on its own.
Route 2
The demands around the work
Interruptions, repeated switching, and a growing stack of open decisions can make judgment and focus harder to use consistently.
Look for errors, repeated work, reversals, or missed handoffs. A capacity effect has to be shown from the evidence.
The two routes can feed each other. Waiting creates chasing, and if the chasing wears on people, their mistakes create more waiting. Neither effect is assumed.
The Four Tests
Does the evidence support a capacity effect?
-
Baseline shift
Are people performing below a level they sustained over time?
An exceptional peak maintained through unsustainable effort is not automatically the baseline.
-
Load signature
Do errors, reversals, delays, or rework cluster under identifiable demand conditions?
-
Shared conditions
Do multiple capable people exposed to the same operating conditions show the pattern?
-
Reversibility
After the relevant conditions change, do the agreed operating metric and associated capacity pattern improve without replacing the people?
The first three tests can support a capacity-effect hypothesis. Reversibility tests that hypothesis after conditions change.
Better flow alone does not establish a capacity effect: the work path may improve directly, and other changes may also explain the result.
What the findings help you decide
Which priorities stay active, who has decision authority, how reviews and handoffs work, and how much demand is routed through the same people and decision points.
Where a change is supported, we propose a test of whether it improves delivery or reduces rework.
Stalled Priority Snapshot
Investigate one result that still matters.
Bring one delayed decision, incomplete rollout, or launch whose expected benefits have not arrived. We combine structured written input from 6–8 people who worked on the project, available records, and a 90-minute working session with up to three participants to reconstruct what happened, test both routes into execution drag, and check competing explanations. You receive a written assessment and a recommended next step.
What you receive
A written readout within 24 hours, with a map of the work as far as the evidence supports, an assessment of what each route explains, and one recommended next step. A 15-minute walkthrough helps the result owner review it.
Where the evidence supports them, the readout includes an extra-labor estimate and a proposed 14-day test. Missing evidence becomes a specific question to investigate.
The evidence determines the next step.
The investigation may support a work-path contribution, a capacity-effect hypothesis to test, both, or neither. A supported work-path finding does not, by itself, establish a capacity effect. The evidence may instead point to a resource, priority, business-fit, or external constraint. We explain what supports the recommendation and what still needs checking.
If the evidence points to a recurring work-demand pattern, the readout explains what needs further investigation. If a simpler correction is supported, that can be the next step. Where the cause remains unclear, we name the missing evidence.
What could change this conclusion?
Every readout names the assumptions behind any cost estimate, any unresolved question that could change the recommendation, and whether resolving it needs more evidence, a management decision, or both.
Follow-up after the agreed test or evidence review is included. There is no commitment to a further engagement.
What it looks like when the result falls short
These patterns often appear when leaders ask why projects fail. Each one is evidence of a problem, but it is not yet proof of a cause.
The team starts the day in meetings and does the real work after hours.
Every new priority stayed active. Nothing came off.
The team that delivered last quarter is gridlocked this quarter. Same people. Same skills.
The rollout works at headquarters. The branches are still waiting.
The work itself took four hours. Approval took nineteen days.
A completed deliverable is back for a third review because the criteria arrived late.
The new process launched on time. People still use the old spreadsheet.
The AI pilot added review and exception work. The old process still runs beside it.
The intake got automated. The request reaches the same reviewer's queue a day sooner and waits there just as long.
Urgent work keeps shipping. The strategic initiative that defined the plan is still on the slide.
These symptoms do not establish one cause. Operational bottlenecks can sit in resources, approvals, dependencies, or cross-functional handoffs. Workflow bottlenecks often show up as waiting and rework, while slow decision-making can point to unclear authority or an overloaded decision route. Emergent Skills examines these explanations and checks whether the conditions around the work are also producing errors and rework.
Stalled, partly delivered, or launched but underused? See the three situations →
For work crossing departments, explore the roles a strategy passes through and why it stalls.
Project and work-management systems such as Workfront, ServiceNow, Jira, Asana, Smartsheet, and Planview show owners, status, deadlines, dependencies, workload, and blockers. Those records do not by themselves establish why a queue moved more slowly than the plan assumed or why completed work returned for review. Business process mapping documents the route. Emergent Skills uses that work history to investigate both the obstruction and whether the demands it creates are adding errors and rework downstream.
Initial Investigation Checks
- Outcome validity: Is the result still worth pursuing?
- Priority choice: Is it genuinely a chosen priority?
- Delivery prerequisites: Are capability, information, authority, and funding available?
- External dependency: Is something outside the organization controlling progress?
If one needs attention first, we explain why. That alone does not rule out either execution-drag route. Previous success is useful evidence; a new result may require investigation of both capability and the work path.
Check ordinary execution first. We check whether known, workable standards are being followed before attributing the shortfall to either route. If the evidence supports an ordinary management correction, we say so and recommend it.
What the delay costs
The delay is visible. Its full cost may not be.
Four hours of work followed by nineteen days waiting for approval can carry several costs. People may spend extra time chasing a decision, repeating a review or rebuilding context. A customer delivery, a billing milestone or the expected benefit of a launch may also move later. Count the extra labor separately from elapsed waiting and any financial effect the evidence supports. The five Capacity Taxes below organize those questions. Turnover and missed opportunities require additional evidence and stay outside the labor estimate.
How much is at stake? Link the delay to revenue, customer delivery, or other valuable work. The value still at stake should justify the cost and effort of investigation and any proposed change. A straightforward internal correction may be enough.
01 Extra coordination
Meeting Tax · Traceable extra labor.
A delivery team spends the day in coordination meetings and finishes the deliverable after hours. Identify the extra meetings, follow-up and repeated explanations associated with the stalled result. Count that time once; do not assume every meeting or interrupted hour was wasted.
02 Rework and corrections
Decision Density Tax · Traceable extra labor.
A proposal returns because pricing criteria arrived after the review. People revise the numbers, repeat the checks and explain the change to the client. Those additional hours are a cost to investigate. Check whether the return reflects late criteria, necessary review or a quality problem.
03 Approval delays
Manager Load Tax · Waiting and extra labor reported separately.
Finished Monday, reviewed Thursday: the work waits, and both people may need to rebuild context. Record the waiting separately from time spent chasing or restarting. In the illustrative Northline sample, about 60 percent of elapsed time was waiting. That figure describes an invented case, not a client result.
04 Turnover exposure
Recovery Debt Tax · Requires additional evidence.
Repeated delivery pushes, persistent after-hours work and resignations deserve investigation. A Snapshot can flag the concern. Establishing whether work conditions contributed to a departure, and estimating replacement or ramp-up costs, requires evidence beyond one session.
05 Missed opportunities
Forfeited Upside Tax · Assumption-based exposure.
A pricing change or customer opportunity stays in a queue while its expected value remains unrealized. Estimate that exposure only from a documented business case or pipeline, with the assumptions shown. The invented Northline sample models roughly $7.5M of exposure. It is illustrative, not a measured client loss, and is excluded from the extra-labor estimate.
One traced result shows what happened on that occasion. Similar work may encounter the same condition, but that needs checking. Where the evidence supports a change, a 14-day experiment tests whether it helps relevant work move with less waiting or rework, while preserving required controls and quality.
How the number holds up
The Snapshot reports supported extra-labor estimates with the arithmetic and key assumptions beside the figure. The readout also names any unknown that could change the recommendation. Elapsed waiting stays in days, on its own line. The Tax categories overlap, so their figures are not added together. Turnover and opportunity exposure stay outside the labor estimate. The illustrative sample read shows the format and the calculation.
Common questions about business execution and stalled work
What if the work path is not the problem?
We begin with the Initial Investigation Checks: whether the result is worth pursuing, whether it is a chosen priority, whether capability, information, authority, and funding are available, and whether an external dependency controls progress. We also check for evidence of a possible capacity effect, even when work-path evidence is weak.
A problem in one of those areas can make a resource or leadership decision the next step. It does not, by itself, rule out either execution-drag route. If neither route is supported, the readout points to the strongest other explanation the evidence allows. If the evidence is insufficient, we say the cause remains unclear and name the evidence or decision needed next.
Is this a burnout, engagement, or L&D program?
No. The Snapshot investigates one stalled business result: where the work waited, looped, or came back, and what that cost. If the evidence supports a capacity-effect hypothesis, the readout names it, explains its limits, and recommends the next evidence check or a test of changed work conditions. A delay alone does not establish burnout, disengagement, or a skills gap.
Could my team do this with AI?
Yes. Your team can use AI to help organize records, draft a map and examine possible explanations. The question is whether the investigation will get done and what evidence can support the decision.
With the Snapshot, ES leads a focused working session, checks explanations against the available records, and produces a written recommendation with its assumptions and limits. The Snapshot page sets out the scope and what to bring.
Bring one priority that still matters.
A stalled project, a partly delivered rollout, or a launch that has not produced the expected result. Bring the work and the questions around it. Get a written assessment within 24 hours of the session, with what the evidence supports and what to do next.