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.
One route is visible in the work itself: waits, queues, handoffs, approval loops, and rework. The second shows up when the demands created by that route contribute to observable execution failures such as errors, repeated work, reversals, or missed handoffs.
ES tests both routes against the evidence. We check what changed, when the execution failures appear, and whether the pattern repeats under similar conditions.
The findings help you decide what to change: which priorities stay active, who can authorize a decision, how reviews and handoffs work, or 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 show that the work path contributed, that work-demand effects contributed, that both did, or that neither is supported yet. It 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.
Before the route. We check the intended outcome, the priority leadership has chosen, the skills and resources available, and any external dependency setting the pace. If one needs attention first, we explain why. That alone does not rule out a work-path contribution. Previous success is useful evidence; a new result may require investigation of both capability and the work path.
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.
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?
When work-path evidence is weak, we also check whether work-demand effects are contributing to observable errors or rework. We first check whether the intended outcome still makes sense, whether leadership still chooses it as a priority, whether the required skills, information, authority and funding are available, and whether an external dependency controls the pace.
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 shows the demands of the work are driving errors or rework, the readout says so and recommends a change to the work. 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.