Independent assessment of one stalled project
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.
Someone will trace the workflow. The status report, the team's own post-mortem, and the outside firm's assessment all show where the work waited. None of them test whether the load on the people doing the work is what's producing the errors, reversals, and rework. So the fix lands on the queue, and the rework keeps coming.
Emergent Skills checks both, with tests that can fail, and tells you which one the evidence supports. If it's neither, we say what it does point to, and we're done. You get a written finding you can put in front of the person asking.
Led by Jim Wilde, founder of Emergent Skills. Nine years as lead consultant on mta.info and the NYC subway countdown clocks. Decades in enterprise systems before that.
$1,500 USD fixed · One stalled priority · Written input from 6–8 contributors · One 90-minute session, up to 3 people · Readout within 24 hours
Two routes into execution drag
The workflow gets traced. The load on the people gets guessed at.
Route 1
The work itself
Queues, handoffs, approvals, rework. Every assessment looks here, and it should.
We trace where delivery is obstructed. A work-path finding stands on its own.
Route 2
The load on the people doing it
Interruptions, constant switching, and a growing stack of open decisions make judgment and focus harder to use. This is the route that gets skipped, because a delay is easier to pin on a queue than to trace to the conditions around it.
We don't assume it. It has to show up in the errors, repeated work, reversals, or missed handoffs, and it has to pass four tests.
The two routes can feed each other. Waiting creates chasing, and if the chasing wears on people, their mistakes create more waiting.
The Four Tests
Does the evidence support a capacity effect?
-
Baseline shift
Are people performing below a level they sustained over time?
A peak held through unsustainable effort is not the baseline.
-
Load signature
Do errors, reversals, delays, or rework cluster under identifiable demand conditions?
-
Shared conditions
Do multiple capable people under the same operating conditions show the pattern?
-
Reversibility
When those conditions change, do the agreed metric and the error pattern improve without replacing the people?
Tests 1 to 3 can support a capacity-effect hypothesis. Test 4 checks it. Better flow alone doesn't prove one: the work path may have improved on its own, or something else changed.
What the findings help you decide
Which priorities stay active, who has decision authority, how reviews and handoffs work, and how much demand runs through the same people and decision points.
If the evidence supports neither route, the readout says what it does point to. There is no phase two waiting behind the finding.
Stalled Priority Snapshot
Investigate one result that still matters.
Bring one delayed decision, stalled rollout, or launch that hasn't paid off. We reconstruct what happened, test both routes, and check the competing explanations.
What you receive
A written readout within 24 hours: a map of the work as far as the evidence supports, 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.
We tell you which route the evidence supports. If it's neither, we say what it does point to: a resourcing gap, a priority call, a business-fit question, or a constraint outside your control. Every recommendation comes with what backs it and what still needs checking.
What could change this conclusion?
Every readout names the assumptions behind any cost estimate, the open questions that could change the recommendation, and whether settling them takes more evidence, a management decision, or both.
Follow-up after the test is included. No commitment past that.
What it looks like before you have a name for it
These patterns show up when leaders ask why projects fail. Each one is evidence of a problem. None is 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.
Operational bottlenecks can sit in resources, approvals, dependencies, or cross-functional handoffs. Workflow bottlenecks show up as waiting and rework. Slow decision-making can point to unclear authority or an overloaded decision route. We check each, and whether the conditions around the work are adding errors on top.
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 record who owns what, where it stands, and what's blocked. They don't say why a queue moved slower than the plan assumed or why finished work came back. Business process mapping documents the route. We start from that record and trace both routes from there.
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 of these needs attention first, we say so. That doesn't rule out either route. We also check whether known, workable standards are being followed before blaming the route at all; if the evidence supports an ordinary management correction, we recommend it.
What the delay costs
The delay is visible. Its full cost may not be.
Four hours of work. Nineteen days waiting for approval. Underneath the wait, people chase the decision, repeat the review, and rebuild context, and a customer delivery or a billing milestone slides with it. The five Capacity Taxes below sort those costs so each is counted once.
How much is at stake? Tie the delay to revenue, a customer delivery, or other work that matters. What's still at stake should justify the cost of looking.
01 Extra coordination
Meeting Tax · Traceable extra labor.
A team spends the day in coordination meetings and finishes the deliverable after hours. Identify the extra meetings, follow-ups, and repeated explanations tied to the stalled result. Count that time once; don't assume every meeting or interrupted hour was wasted.
02 Rework and corrections
Decision Density Tax · Traceable extra labor.
A proposal comes back because pricing criteria arrived after the review. People redo the numbers, repeat the checks, and explain the change to the client. Those hours are the cost. Check whether the return reflects late criteria, a 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 rebuild context. Record the waiting separately from time spent chasing or restarting. In the Northline sample, about 60 percent of elapsed time was waiting.
04 Turnover exposure
Recovery Debt Tax · Requires additional evidence.
Repeated delivery pushes, persistent after-hours work, and resignations deserve a look. A Snapshot can flag the concern. Showing that work conditions contributed to a departure, and costing the replacement and ramp-up, takes evidence beyond one session.
05 Missed opportunities
Forfeited Upside Tax · Assumption-based exposure.
A pricing change or customer opportunity sits in a queue while its value goes unrealized. Estimate that exposure only from a documented business case or pipeline, assumptions shown. The Northline sample models roughly $7.5M of it, kept outside the labor estimate.
One traced result shows what happened once. Whether it keeps happening is the next question.
How the number holds up
Extra-labor estimates come with the arithmetic and key assumptions beside the figure. Elapsed waiting stays in days, on its own line. The Tax categories overlap, so their figures aren't added together. Turnover and opportunity exposure stay outside the labor estimate. Northline is an invented sample, not a client result; the sample readout shows the format and the calculation.
Common questions about business execution and stalled work
What if the work path is not the problem?
We run the Initial Investigation Checks above, and we look for a capacity effect even when work-path evidence is thin. A problem in one of those checks can make a resource or leadership decision the next step. It doesn't rule out either route.
If neither route holds up, the readout names the strongest other explanation the evidence allows, or says the cause is still unclear and what would settle it.
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, states its limits, and recommends the next check or a test of changed conditions. A delay alone doesn't establish burnout, disengagement, or a skills gap.
Could my team do this with AI?
Yes. AI will organize the records and draft the map. The question is whether anyone on your team has the time to run the investigation, and what evidence ends up behind the decision.
With the Snapshot, ES runs the working session, checks explanations against the records, and writes the recommendation with its assumptions and limits. The Snapshot page sets out the scope and what to bring.
Bring the one you keep getting asked about.
A stalled project, a partial rollout, or a launch that hasn't paid off. Written assessment within 24 hours of the session: what the evidence supports, and what to do next. $1,500, fixed.
