Operational Payoff · Operations consulting - 
Find out what's wrong with one project.
Priority Snapshot: investigate what is holding back one critical result.
A project is late, keeps returning for review, or launched without the expected uptake. A recurring operation, like customer onboarding, keeps coming back for corrections. What does that shortfall mean for revenue, customer delivery, or other valuable work, and what can still be protected?
Before you fund the fix, find the right problem.
The Stalled Priority Snapshot is a focused operational investigation. Emergent Skills starts with one important result, tests competing explanations against the work and the evidence, and tells you what the evidence supports, what remains uncertain, and what decision is justified next.
Most stalled projects already have explanations: the process, the people, training, priorities, workload, or the system. Any one could be right. The Snapshot tests those explanations instead of treating the first plausible answer as the cause.
Your first option may be to ask your PMO, operations team, project manager, or analysts to investigate. They already know the organization and may have the records and systems needed to determine what happened. If they can assemble the evidence, challenge the competing explanations, and recommend a useful next step, an outside investigation may not be necessary.
If the explanation remains unclear, we first check whether the result is still worth pursuing and genuinely prioritized. We also check whether the required capability, information, authority, and funding are available, and whether an outside dependency controls progress.
Then we examine the work needed to produce the result:
Missing Work Check
Was necessary work assigned?
Check whether the work needed for the result was identified and assigned to a named owner.
Route 1
Where work gets stuck
Trace where work waits, loops, or comes back through queues, approvals, and handoffs.
Route 2
Do work demands add errors and rework?
Check whether interruptions, switching, or competing decisions contribute to errors, rework, reversals, or missed handoffs.
You get
- A manager’s decision brief
- The evidence record: Initial Investigation Checks, necessary-work assessment, work-path map, competing explanations, and evidence behind the finding
- An action plan naming the first step, owner, approval needed, and effort to confirm
If the evidence points to the business case, capability, authority, incentives, an external dependency, ordinary execution discipline, or something else, we say so.
\$1,500 USD
Fixed scope
Written input
From people involved in the work (typically 6–8)
90-minute session
With up to three participants
Written report
Within 24 hours of the session
15-minute walkthrough
With the result owner
Follow-up
After an agreed test or evidence review
No follow-on commitment. Remote or in person, with location and travel agreed before booking.
Led by Jim Wilde, founder of Emergent Skills. Nine years as lead consultant at the MTA on mta.info and the NYC subway countdown clocks. Decades in enterprise systems before that.
Request a SnapshotYour side of the cost: up to 4.5 person-hours in the session, plus time for written input, preparation, and the walkthrough. We agree on the contributors and session participants before booking. Tell us the result, your PO or quote needs, and your preferred date. We reply within one business day. Scope and the session date are confirmed separately.
Evidence first, then the two execution routes
Start with the result. Keep competing explanations open.
The Snapshot first checks whether the expected result is still valid, genuinely prioritized, supported by the needed prerequisites, and free of a controlling external dependency. It keeps competing explanations open. If execution remains in scope, it tests both routes against the record.
Route 1. The work gets stuck.
Waits at approvals, loops back for rework, queues at a gate, gaps at a handoff. What the work record itself explains.
Route 2. Do work demands disrupt execution?
Do interruptions, repeated switching, or competing decisions make it harder for capable people to catch errors, decide consistently, or complete handoffs? Waiting behind a busy person can still be a work-path finding. A capacity effect needs its own evidence.
The diagram illustrates the two execution routes, not the whole investigation. The evidence may support necessary-work gaps, Route 1, Route 2, another explanation, several interacting conditions, or none. The readout says what holds up, what remains uncertain, and the next step.
An illustrative written readout
Read a finished evidence-first readout before you buy one.
Northline Group is a fictional company with about \$2B in revenue and roughly 9,000 employees. All figures are invented to demonstrate the report, not customer results. This earlier sample shows the decision brief, findings, action plan, and supporting calculation.
The invented case is a pricing and packaging strategy intended to improve realized margin on eligible new contracts by the end of Q1. It reached those contracts one quarter late. The report keeps the commercial consequence, the work-path evidence, competing explanations, and the extra-labor estimate separate.
Start with the decision brief below. This earlier sample records some prerequisites within the route findings; it does not show the current Initial Investigation Checks as a separate opening section. The result remained required and funded, and no external hold was recorded. Required Compliance sequencing remains an open question. Route 1 is partly supported; Route 2 remains unresolved. Necessary work was not assessed in this particular pricing example.
See the earlier mixed-results sample: launched on time, adoption below target, with unassigned necessary work identified. This earlier PDF is not the current method reference: the four jobs are investigation prompts, and a Route 2 finding requires evidence connecting demands to execution failures.
Sample findings
What the four-page report supports, and what must still be confirmed before acting.
A prerequisite question remains open
The fictional record says the result remained required and funded, reviewers were available, and no external hold was recorded. Required Compliance sequencing must be separated from avoidable serial routing before the route is changed.
The finding: Route 1 partly supported; Route 2 unresolved
The gate log records 12 steps over 119 calendar days, including 71 days of waiting. Sequential reviews and returned work support a routing contribution. The record does not yet link demand pressure to errors or rework. Required Compliance work, pricing complexity, and unclear scope remain plausible competing explanations.
The business consequence: a strategy one quarter late
Eligible contracts may have been signed under old terms during the delay. The report does not assign a dollar loss. Finance must establish the affected contracts, incremental margin, timing, and repricing rights. Historical losses are not presented as recoverable savings.
The first action: establish the commercial case and review permissions
The internal Pricing Lead and Finance analyst identify affected contracts and upcoming Q4 margin exposure. Control owners confirm which reviews may overlap. A test is authorized only if the remaining value justifies the effort and the required controls can be preserved.
The conditional test: parallel review with controls preserved
If authorized, Finance, Legal, and Compliance review in parallel against one comment deadline. The target is a median gate wait of 5 business days or less against a fictional 10-day baseline, with at least five comparable decisions and explicit guardrails.
The supporting calculation: \$45,900 to \$81,600 in extra labor
Page four shows the twelve-step map and calculation. The estimate is one cost component, not total business impact or promised savings, and the assumptions remain visible beside the number.
The full written read Open all four pages of the Workbench sample report
Read the report in this order: the manager’s decision brief; what we found; what happens next; and supporting notes. In this earlier sample, some prerequisites are recorded within the route findings. Current Snapshots begin with the Initial Investigation Checks and also assess necessary work and assignment. The action plan begins with the evidence and permissions needed before any test.
Report length follows the evidence. A case with assessed necessary-work items, longer evidence notes, or observed test results can add pages. Unknown value stays unknown.
Why bring in ES?
What a focused outside investigation adds
Your PMO, operations team, project manager, or analysts may be able to resolve this with the systems and records you already have. If they can assemble the evidence, challenge the competing explanations, and recommend a useful next step, use the internal review. An outside investigation earns its place when the explanation remains unclear or disputed, nobody has time to reconstruct the work, the issue crosses teams, or the sponsor needs an independent finding they can take back to the organization. Compare what each investigation would give you: scope, evidence, independence, and the next decision.
The Snapshot starts with the business result, runs the Initial Investigation Checks, reconstructs the work, keeps competing explanations open, and then tests the execution routes the evidence supports. Jim checks the available evidence and identifies what still needs testing. You receive a written assessment of what happened, what value remains at stake, and what to do next:
Convene the room
Bring the right perspectives into one conversation and keep attention on the result and its path.
Challenge the explanation
Check the sponsor’s starting hypothesis against the record, the Initial Investigation Checks, necessary work and assignment, Route 1, Route 2, and credible competing explanations. State what remains uncertain and what could change the finding.
Resolve the record
Reconcile conflicting accounts where possible and mark unresolved steps or dates as uncertain.
Agree the next step
Help the responsible people agree on a practical next step, the authority it needs, and the evidence that would justify continuing.
If your team can do this confidently itself, use the sample and the cost-of-stalled-work calculator to build and check an estimate.
Jim leads every session and prepares the written readout. View Jim’s experience on LinkedIn.
What you get.
- Written input from people involved in the work (typically 6–8), then a 90-minute facilitated session with up to three participants, focused on one result and the gap between expected and actual.
- A work-path map showing work, handoffs, approvals, waiting, and rework, with uncertain steps marked.
- An evidence assessment that starts with outcome validity, priority, delivery prerequisites, and external dependency; checks necessary work and assignment; tests Route 1 and Route 2 separately; preserves competing explanations; and states what could change the conclusion. The report names the first action, owner, approval needed, effort to confirm, and review date.
- Business consequences and value still at stake: lost value, delayed benefits, customer or operating effects, and additional costs where supported. Estimates show the affected population, period, sources, assumptions, and gaps. Extra labor is one component. Overlapping amounts are not added together.
- The business case for the next step: what the evidence could change, the value that decision could still protect, and the fee and internal effort involved. A straightforward internal correction may be enough.
- A proposed local experiment when warranted: question, change, required approval, owner, baseline, metric, target, evidence threshold, guardrail, and decision rule. A capacity-effect test also tracks the associated capacity pattern. If a test is premature, the report names the next question to investigate.
- A brief written report within 24 hours and a 15-minute walkthrough with the result owner.
- A brief follow-up after an agreed test or evidence review to decide what comes next.
\$1,500 USD, fixed scope. No required follow-on engagement.
Is this the right fit?
What if the chokepoint turns out to be me?
Then we look at what that approval does, why it exists, and whether the work could move differently without losing the control it provides. Any test needs the relevant authority and must preserve required controls. The subject is how the work moves and what can change. The Snapshot does not rate individual performance.
You decide who sees the report within your organization. No HR records, system credentials, or data exports are required; we use the work description, dates, estimates, and purchasing information needed for the engagement, and participants share only what they’re authorized to share.
Best fit: one important result in a project or recurring operation is falling short across functions or decision points. Delays, repeated errors, missed handoffs, or adoption below target have a meaningful business consequence. A manager or leader owns the result and can act on the next step, whether that means gathering evidence, resolving a management decision, or authorizing a local test.
Is the result worth the investigation? Identify what the shortfall means for revenue, customer delivery, or other valuable work. The \$1,500 fee and your team’s time should be justified by the value still at stake. Money already spent is context. Any proposed change needs its own case; a straightforward internal correction may be enough.
How the session runs
A 90-minute working session inside a focused investigation.
The 90 minutes is the working session, not the whole investigation. Before the session, we typically ask 6–8 people involved in the work to write up what they handled, what they waited for, what came back, and what changed. ES reviews the input and available records around one tightly scoped question: one result, competing explanations, and one next decision. Up to three people then join the 90-minute session to reconcile the route, check the evidence, and agree what happens next. Include someone who does the work directly and, where possible, someone who can authorize a change. For an adoption shortfall, include someone who knows how users get access and make the switch. We agree on the people needed to cover the relevant work before booking; a simpler route may need fewer contributors.
Light preparation. Bring the expected result, the actual result as of a stated date, and the main steps or waits you know, with a note on where the figures came from. Approximate dates are fine. For mixed results, say who owns the target and how progress is measured. Where authorized, have calendar invitations, ticket or approval history, and revision dates for the route at hand, and an approved blended loaded hourly rate if you have one. No presentation, system credentials, or data export is required; the preparation sheet explains what will help.
Allow for internal time. With up to three people attending for 90 minutes, allow up to 4.5 person-hours for the session, plus time for the agreed written contributors, light preparation, the result-owner walkthrough, and any agreed test. Those internal costs are additional to the fee.
Initial Investigation Checks
We begin with the result and the conditions needed to deliver it.
1. Outcome validity
Is the result still worth pursuing?
2. Priority choice
Is it genuinely a chosen priority?
3. Delivery prerequisites
Are capability, information, authority, and funding available?
4. External dependency
Is something outside the organization controlling progress?
These checks may settle the next decision on their own. A problem here doesn't, by itself, rule out either route. We also check whether known, workable standards are being followed before blaming the route; if the evidence supports an ordinary management correction, we say so and recommend it.
Necessary work and assignment
Check whether necessary work was identified and assigned. For implementation and rollout work, these four jobs are common places to look, not universal requirements. We ask for a name, not a department, and can record other case-specific necessary work when these prompts do not fit.
1. Make it work here
Who owns making it work with the actual data, volumes, exceptions, and operating conditions?
2. Fit the interfaces
Who owns getting the affected teams to agree on definitions, handoffs, and dependencies?
3. Take out the old process
Who owns retiring the old process, or defining when it must remain in use?
4. Settle the disruption
Who owns the work needed to absorb the operating change across the affected roles and teams?
Necessary work that has no named owner is different from work that is merely stuck. A status alone is not a finding: an unowned item needs a note and a source. The readout names what the evidence supports and can include case-specific necessary work outside these four prompts.
The Four Tests
When a capacity effect is suspected. We use the Four Tests to assess that explanation against the work evidence.
1. Baseline shift
Are people performing below a level they sustained over time?
A peak held through unsustainable effort is not automatically the baseline.
2. Load signature
Do errors, reversals, delays, or rework cluster under identifiable demand conditions?
3. Shared conditions
Do multiple capable people exposed to the same operating conditions show the pattern?
4. Reversibility
When the suspected conditions change, does the execution effect change in the expected direction?
The first three tests can support a capacity-effect hypothesis. Reversibility tests it. A Snapshot can assess the available evidence for the first three tests. Reversibility requires evidence from changed conditions and enough comparable observations to support the conclusion. Better flow alone does not establish a capacity effect because the change may have improved the work path directly or another condition may explain the result.
Where this sits
Use the Snapshot for one result that is falling short.
The Snapshot finds a local next step. Where the question spans a team or function, the Diagnostic examines the wider pattern. A Capacity Audit establishes the baseline and evidence for a proposed change. The Pilot tests an authorized change against agreed operating measures and, where relevant, the associated capacity pattern. The License supports wider use where the evidence justifies it. All use the same execution gap analysis at different scopes. The next step depends on the evidence.
The investigation checks begin with the business result and its consequence. The Five Capacity Taxes organize supporting cost questions. Lost value, delayed benefits, extra labor, and future exposure remain distinct, with sources, assumptions, and uncertainty visible.
Want to explore the fit first? The Execution Drag Checklist walks through the opening questions used to frame a result that has not moved. Download the checklist.
Request and schedule
Start with the priority. We will confirm the fit and arrangements.
1. Send the request
Describe one result: what was expected, what happened, and by what date. For a rollout with low uptake, include the target and observed adoption. Suggest the participating roles and give your preferred date and session format. A few sentences are enough.
2. Tell us your purchasing status
Have a PO ready? Include its number and any purchasing instructions. Need a quote to obtain a PO, or expect the PO to follow? Select that option. We will coordinate any PO documentation, supplier registration, invoicing requirements, and payment terms with you.
3. Confirm the session
We reply within one business day, then confirm fit, scope, contributors, participants, purchasing, and a date. We decline when the answer is already clear and further investigation would add little, the group can't cover the relevant work, or no owner can act on the next step. That step may be gathering evidence, resolving a management decision, or authorizing a local test. Once agreed, we send the preparation sheet and session details.
Submitting the form does not charge you, accept PO terms, reserve a date, or confirm a booking. Your date is a preference until we agree the session with you.
Start with one result
Bring one important result that is falling short.
\$1,500 USD, fixed scope. Written report within 24 hours of the session.
