Operational Payoff · Operations consulting
Work Demand Diagnostic: investigate recurring operational problems.
Decisions keep coming back. Priorities slip across several teams. Rollouts launch, but the expected business result never follows.
Bring one recurring operational problem. Emergent Skills conducts a focused operational investigation across several examples of the work. In the half-day working session, we run the Initial Investigation Checks, examine necessary work and ownership, trace how work moved, test competing explanations, and identify the next decision the evidence supports.
Before you fund the fix, find the right problem.
Half-day · $3,500–$7,500 · One-page summary.
Normally 6–10 managers and team leaders. In person or by video. No follow-on commitment.
When it fits
The same problem keeps showing up in different work.
Use the Diagnostic when slow decisions, manager bottlenecks, repeated rework, or delivery and adoption shortfalls recur across priorities, roles, or handoffs. These problems usually already have explanations. The Diagnostic tests whether the examples support the same explanation or whether different causes are being grouped together.
Bring managers who see different parts of the problem, someone with direct knowledge of the work, and a manager who can authorize the next step. Use dates, counts, and records already available. No presentation is required. An outside investigation can also help when the issue crosses teams or the sponsor needs an independent finding they can take back across the organization.
Is the result worth investigating? Identify what the shortfall means for revenue, customer delivery, or other valuable work. The next decision should justify the fee and your team’s time. A straightforward internal correction may be enough.
For one isolated result, consider the $1,500 Stalled Priority Snapshot. The free calculator can help explore the possible scale of a problem using your assumptions.
What you receive
A one-page Diagnostic summary.
The summary records what the evidence supports, what remains unresolved, and the next decision. It does not need to prove one root cause. It covers:
What the evidence supports
Which explanations the examples support or weaken, what remains uncertain, and what could change the conclusion. Several conditions may interact, or another cause may explain more than either ES route.
The recurring pattern
A map of selected work and decisions, showing missing ownership, waits, loops, and handoffs where found. Disputed dates and gaps stay visible.
Work-demand contribution
Whether interruptions, switching, competing decisions, or other surrounding demands are connected to observable execution failures across the examples. This does not by itself establish a capacity effect.
Where the cost appears
Supported extra labor, elapsed delay, opportunity value, intervention cost, and relevant cost lenses, with overlap and missing records identified.
The directional cost case
Supported estimates from your inputs, with assumptions and confidence stated. Extra labor, elapsed delay, and possible future value stay separate.
The next decision and its owner
A management decision, local correction, specific evidence step, bounded test where warranted, or a recommendation to stop or redirect. If the cause remains unresolved, the summary names what is needed next, who owns it, and when it will be reviewed.
What we investigate
Start with the basic checks. Then test the recurring pattern.
Several initiatives can miss their expected results for different reasons. We do not assume repeated symptoms share one cause. The Initial Investigation Checks, necessary work and ownership, the two execution routes, and other competing explanations are all parts of the investigation. We compare the evidence before calling the problem a recurring pattern.
First: do the Initial Investigation Checks
Check whether the expected result is still valid, whether it remains a chosen priority, whether the required capability, information, authority, funding, and other means are present, and whether an external dependency is setting the pace.
Was the necessary work identified and assigned?
Necessary work may have no owner across several initiatives. Common prompts include adapting a system to actual data and exceptions, agreeing handoffs between teams, retiring or deliberately coexisting with the old process, and deciding who absorbs the operating change. These are prompts, not universal jobs.
Route 1: friction in the work path
Work waits for approval, loops back, queues behind the same person, or breaks at a handoff. These conditions can cause delay and rework even when people can do the work well.
Route 2: demand affecting execution
Interruptions, switching, or competing decisions may make existing judgment, focus, and communication harder to use. We look for errors, reversals, missed handoffs, or repeated work under those conditions. Being busy alone does not establish the cause.
Necessary work, Route 1, and Route 2 can interact. Strategy, capability, resources, incentives, execution discipline, or another cause may explain the shortfall better. An existing Snapshot supplies starting evidence; it does not establish a wider pattern by itself.
The working session
How we investigate recurring operational problems.
The half-day is the working session, not the whole engagement. Scope, participants, and the examples to examine are confirmed before the session, and the one-page summary follows it. During the session, the facilitator brings the method and participants bring examples and records they are authorized to share. Four working blocks, with setup, breaks, and a closing decision, make up the half-day.
Frame the problem and check other explanations
Define the expected result, the shortfall, its business consequence, earlier fixes, and a useful measure of improvement.
Check whether the result is still worth pursuing and genuinely prioritized. Confirm the required capability, information, authority, and funding. Identify outside dependencies, unassigned work, and workable standards that aren’t being followed.
Trace selected work and decisions
Reconstruct what happened: approval waits, queues, handoffs, priority collisions, escalation, reversal, and rework. Compare examples and mark disputed dates.
Keep person-hours of effort separate from calendar duration. The Diagnostic builds a working reconstruction; the Audit measures across work flows and roles in greater depth.
Examine whether work demands contribute
Compare execution problems with the surrounding demands. Look for whether errors, reversals, rework, missed handoffs, or delays vary with identifiable conditions and whether similar work exposed to similar conditions shows a related pattern.
If the evidence raises a capacity hypothesis, use baseline shift, load signature, and shared conditions to strengthen or weaken it. Record supporting and contradictory evidence. Reversibility requires changed conditions and is not established in the half-day session.
Build the cost case and choose the next step
Use available dates, counts, and cost inputs. If they can’t support an estimate, name the missing evidence.
Where a bounded test is justified, rank it by expected impact, cost, and ease of implementation. Agree the approval, owner, metric, target, review window, safeguards, and decision rule. Otherwise, identify the evidence or management decision needed next, its owner, and the review point.
Work demand
Look beyond the amount of work.
Volume matters. So do the decisions, interruptions, handoffs, and competing demands surrounding each task. Examples we may examine include:
We connect these conditions to observed work. Their presence alone doesn’t explain an error or establish a capacity effect.
The Five Capacity Taxes
Where the cost may show up.
When relevant, these are overlapping cost lenses for examining where execution loss may be landing. They do not establish five separate causes, and we don’t add them together as though every cost were distinct.
Meeting Tax (coordination cost)
Time spent in repeated alignment and rechecking. We distinguish necessary coordination from avoidable repetition.
Decision Density Tax (quality and rework cost)
Decisions that wait, reopen, or require cleanup. Any claim that demand affected judgment needs separate evidence.
Manager Load Tax (delay and queue cost)
Approvals, escalations, and exceptions concentrated through too few people.
Recovery Debt (sustained demand affecting reliable performance)
Sustained operating demand may affect reliable performance. Any estimate must connect those conditions to observed execution problems.
Forfeited Upside Tax (missed future value)
Strategic work, customer signals, or improvements that don’t get time or a route to action. Your opportunity assumptions remain separate from observed operating costs.
Every estimate retains its source and assumptions. We keep extra labor, elapsed delay, Recovery Debt, and opportunity value separate and check for double counting.
Evidence and limits
What a half-day can establish.
The Diagnostic can identify supported explanations, weaken others, and resolve the next useful decision. It does not have to prove one root cause, and it can’t turn incomplete records into an audited loss or a promised saving.
A capacity effect remains a hypothesis. The first three checks may justify investigation. The fourth, reversibility, requires changing the relevant conditions and measuring what happens. A better result alone doesn’t isolate capacity as the cause: a simpler work path or another change may also explain the improvement.
The investigation concerns the work. Participants describe observed events and surrounding demands. Managers use voluntarily shared work constraints, observable load, and task consequences. ES doesn’t rate people.
The expected explanation can be wrong. If another cause fits better, the summary says so. If evidence is insufficient, it names what is missing, who owns the next evidence or management decision, and when it will be reviewed. A deeper Audit is recommended only when that additional investigation is justified.
Investment
Half-day Diagnostic: $3,500–$7,500.
In person or by video, with a one-page summary. Participant count, scope, summary delivery timing, and arrangements are confirmed before booking.
Small leadership team
$3,500
Up to 6 participants.
Standard
$5,500
Up to 8 participants. Recommended for most leadership teams.
Extended
$7,500
Up to 10 participants. Larger or full-day scopes are agreed before booking.
No follow-on commitment. Any Audit is scoped and commissioned separately.
Where it leads
A separate decision at each step.
The Snapshot investigates one result. The Diagnostic examines a recurring pattern. A Capacity Audit measures that pattern and its economic significance in greater depth, when the evidence warrants it.
A Pilot tests a defined change against an agreed operating metric. The License is intended to help reproduce and sustain what worked.
Across the ES system, the next step may involve the work path, priorities, resources, authority, manager practice, further evidence, or another response supported by the finding. Capacity or individual support belongs only where the evidence makes it relevant.
You can enter at the Audit when the need for deeper measurement, scope, evidence access, and a manager’s authority to act are already established. If a local fix is enough, stop there.
Questions
Before you decide.
What does ES add to an internal review or another improvement method?
An internal review may be enough if your team can assemble the records, challenge competing explanations, and authorize a useful change. Lean, Agile, EOS, and other operating approaches may also be appropriate.
ES combines the Initial Investigation Checks, necessary-work and ownership questions, a work trace, work-demand evidence, competing explanations, and a supported cost case in one bounded outside investigation. The output is the next decision the evidence supports. When the issue crosses teams or the explanation is disputed, the written summary can also give the sponsor an independent finding tied to the evidence.
Is this a wellness or burnout session?
No. It is an operations investigation into a business result and the work behind it. ES starts with the work and the evidence, not wellness, personality, or an assumption about the people doing it.
Should we start with a Snapshot?
Usually, if the question concerns one late, partly delivered, underused, or otherwise underperforming result. The $1,500 Snapshot typically combines written input from 6–8 contributors with a 90-minute working session for up to three participants, a written readout within 24 hours, and a 15-minute walkthrough. The 90 minutes is the working session, not the whole investigation.
It runs the Initial Investigation Checks, examines necessary work and ownership, tests Route 1, Route 2, and competing explanations, and recommends the next decision. A bounded test is optional where supported. Follow-up comes after an agreed test or evidence review. A Snapshot is useful on its own; it isn’t required before a Diagnostic.
Bring the problem that keeps coming back.
Tell us what is recurring, who sees different parts of it, and what records you already have. We’ll confirm whether the Diagnostic fits, its scope and price, and what the investigation can reasonably establish. The goal is a defensible next decision, not a predetermined diagnosis.
