Enterprise Services · Work Demand Diagnostic · For Ops Managers and Team Leaders · Half-Day
Bring the execution problem your team keeps talking about. We trace how the work actually moved.
Slow decision making. Work waiting on one approval. The same decision reopened for the third time. A manager everybody is waiting on. Before deciding it is a people problem, we trace how the work is moving. In half a day, the Work Demand Diagnostic finds the recurring pattern, estimates what it is costing, and names the first change worth testing.
The Diagnostic uses observable work evidence and information participants choose to provide. It does not inspect private app activity or monitor individual state.
Bring one recurring problem, the people who see it, and the numbers you already have.
Executive SummaryThe half-day step when the drag extends beyond one stalled priority.+
A half-day working session for 6 to 10 managers and team leaders. Light preparation, no homework, no follow-on commitment. You bring one recurring execution problem and the evidence already in the room. We reconstruct it together.
We trace selected work and decisions as they actually moved, looking at queues, approvals, handoffs, work in progress, priority collision, rework, and manager bottlenecks. Then we look at whether the same conditions are reducing the judgment, focus, and communication the work requires.
The session closes with a directional cost case, ranked operating experiments, and a straight recommendation on whether a full Capacity Audit is warranted.
Investment: $3,500 to $7,500 depending on participant count and scope. The one-page Diagnostic summary is included. No follow-on engagement is required.
Best fit when you are seeing: slow decision making, decisions that keep reopening, manager bottlenecks, meeting overload, or repeated rework. It also fits uneven performance that shows up under the same operating conditions.
Why It Exists
One stalled priority can reveal a route problem. This asks whether the pattern keeps happening.
The free calculator produces a scenario from a few inputs. The Stalled Priority Snapshot examines one local route. The Capacity Audit measures multiple flows, roles, and cost exposures at depth. The Diagnostic sits between those when the drag reaches past one priority and a full Audit is premature.
A project can look like a people problem because that is where the symptoms appear. Somebody missed a date. Somebody made a call that had to be reversed. Before blaming motivation, skill, or management, we trace how the work moved and where it stopped.
What you get is enough evidence to rank practical experiments and decide whether a Capacity Audit is worth commissioning.
Want a lighter first step? The Stalled Priority Snapshot examines one stuck priority in 90 minutes for $1,500. It supports a local routing hypothesis, not a completed capacity diagnosis.
What Work Demand Means
Demand is not just workload.
Workload is volume. Work demand is the total load created by what enters the system, how much stays open, where it waits, who it passes through, how often it loops, and how much recovery margin the design allows. The Diagnostic examines seven types.
The question is not only whether the team is busy. It is whether the design makes work harder to move, and whether the same conditions leave people with less access to the skill the work requires.
What We Will and Will Not Claim
The limits, stated once.
Sometimes we find a work-path problem and no capacity effect. That is still a useful finding. A queue is real whether or not the people standing in it have full access to their skill.
We do not prove reversibility. A half-day can show that a condition looks expensive. Only the Pilot shows that changing it moves the metric.
We do not price Recovery Debt from one hard week. One absence or one resignation proves nothing. That exposure needs longitudinal and turnover evidence before it goes in a number.
Forfeited Upside stays yours. You supply the opportunity value. We do not book it as an audited loss, and we do not add the five Taxes together to reach a bigger figure.
We do not watch individual state. Managers work from declared information, observable load, and task consequence. No private app activity, no Zone history, no live monitoring, and no Zones dashboard.
A weak capacity read also does not tell you what the cause is instead. A skill gap, the wrong strategy, thin staffing, bad tooling, or ordinary error can produce the same symptoms. We will say which explanations the evidence still allows.
The Five Capacity Taxes
Where the cost shows up.
The Five Capacity Taxes are five entry points into one execution system. They overlap, so we do not total them. We find the work-path pattern first, then say which cost it is producing.
Meeting Tax (coordination cost)
Meeting overload fragments the week. Meetings, alignment, and rechecking consume production time or push decisions later without producing output. Most of it is visible in the calendar.
Decision Density Tax (quality and rework cost)
Consequential decisions stack, wait, escalate, reopen, or come back for cleanup. Delay and rework follow directly. Under sustained load, judgment also gets harder to reach.
Manager Load Tax (delay and queue cost)
Approvals, escalations, exceptions, and open work route through one manager. The queue slows everyone behind it. Constant switching then burns the capacity that would clear the queue.
Recovery Debt Tax (longer-term attrition exposure)
Sustained demand runs with no recovery margin built into the rhythm. People leave, or they stay and produce less. This is the one Tax we will not price without history.
Forfeited Upside Tax (missed future value)
Strategic work, customer signals, and new ideas never get protected capacity or a route to action. Nobody logs what did not happen, which is why this cost stays invisible longest.
First we find what is slowing the work. Then we work out what it is costing.
What Happens in the Diagnostic
What we do in the room.
It is a working conversation, not a pitch. The facilitator brings the method. The room brings the live execution pattern, the dates, the counts, and the operating context. Four blocks form the spine of the half-day. Setup, transitions, debrief, and the Audit decision fill the rest.
Frame the recurring pattern
The room names one execution problem that has repeated across more than one event, priority, or decision. Together we define the business consequence, the scope, the roles involved, what has already been tried, and the operating metric that would matter if the condition changed.
The starting question is deliberately neutral: where is the work losing time or quality, and what evidence would tell us why?
Trace the work and decisions
The facilitator reconstructs selected work and decisions as they actually moved. The trace looks for queue age, approval wait, handoff failure, work in progress, priority collision, rework, escalation, reversal, and manager concentration.
Where the room can support the dates and counts, we get two useful reads: how much elapsed time was active work versus waiting, and how far decisions traveled, how long they sat, how often they reopened. This is a working reconstruction. Timestamp-level measurement across roles belongs to the Audit.
Screen the capacity effect
Then a narrower question. Are capable people performing below their own sustained baseline? Do the errors, reversals, rework, and delay cluster under identifiable load conditions? Do several people exposed to the same design show the same pattern?
We work from declared information, observable workload, and the operating evidence in front of us.
Build the case and rank the experiments
We work out what the bottleneck is costing the team and where that cost is showing up, using your numbers, with the assumptions visible. Traceable operating loss, elapsed delay, Recovery Debt, and opportunity value stay in separate columns.
The session closes with ranked, reversible operating experiments, each tied to an owner, metric, target, and decision rule, plus a straight recommendation on whether the evidence justifies a full Capacity Audit.
What You Leave With
What you get 24 hours later.
The primary work-path pattern
The strongest recurring mechanism the session found: queue buildup, approval drag, weak handoffs, too much work in progress, priority collision, rework, or manager bottlenecks. Named before any Tax is attached to it.
The flow and decision reads
Active work versus waiting, decision latency, escalation distance, reversals, and reopenings, from the traces the room could support. Gaps in the evidence are shown, not filled in.
The capacity-effect screen
A clear read on baseline shift, load signature, and shared conditions: supported, unsupported, or still unknown. Three of the Four Tests. Reversibility waits for the Pilot.
The relevant Tax exposure
Which of the five costs this pattern is producing, with the overlap and the evidence limits stated.
The directional cost case
A starting economic case built from your own inputs, with the assumptions and the confidence level visible. Direct operating loss, elapsed delay, Recovery Debt, and Forfeited Upside stay distinct.
Ranked experiments and the Audit verdict
A short list of reversible operating tests, each with an owner, metric, target, and decision rule, plus a straight answer on whether a Capacity Audit is warranted.
Who It Is For
Leaders who can see the drag repeating and want a disciplined read before commissioning an Audit.
It works best when a sponsor can name one recurring execution problem, bring the managers who see it from different points in the path, and supply enough dates, counts, or examples to reconstruct how the work moved.
Right for a Diagnostic
A leadership team of 6 to 10 with a pattern that crosses priorities, roles, decisions, or handoffs. The room is willing to test more than one explanation and wants ranked experiments plus a first cost case.
Ready for an Audit instead
You need measurement across multiple flows and roles, a CFO-readable model with confidence levels, a ranked intervention portfolio, or a formal Pilot measurement plan. You do not need to decide in advance that the problem is capacity-driven.
Investment
$3,500 to $7,500.
Half-day session. 6 to 10 participants. In person or by video. One-page Diagnostic summary within 24 hours.
Small leadership team
$3,500
Up to 6 participants. Half-day, remote or in person.
Standard
$5,500
Up to 8 participants. Recommended for most leadership teams.
Extended
$7,500
Up to 10 participants or two related execution patterns examined.
No follow-on commitment. If the session supports a clear case for a Capacity Audit, that conversation happens afterward on its own merits.
Not ready to commit the leadership team? Start with one priority. The Stalled Priority Snapshot is a 90-minute read on one stuck priority for $1,500, with up to three people and a one-page readout within 24 hours. The fee credits toward this Diagnostic when booked within 30 days.
Where It Fits in the Engagement Path
Between one stuck priority and a full Audit.
The Snapshot tests one live priority. The Diagnostic looks for the pattern across several. When the evidence supports a broader case, the Capacity Audit measures the friction, the cost, and the intervention options at depth.
You Are Here
Diagnostic
Next, if warranted
Capacity Audit
Test reversibility
Pilot
Sustain after proof
License
The Diagnostic is not required first. If you already need measurement across multiple flows, a CFO-readable cost case, and a Pilot plan, go straight to the Audit.
Questions
How is this different?
How is this different from Lean, Agile, EOS, operational excellence, or traditional consulting?
Those disciplines improve flow, structure, accountability, and operating practice, and they recommend changes. We do not pretend otherwise.
What we add is the second question. We trace the work path, then ask whether the same conditions are reducing the judgment, focus, communication, and creativity the work requires. A later Pilot can combine work redesign, manager practice, private individual support, and measurement of the operating result.
Where is the work path creating drag, and is it also reducing access to the skill the work requires?
A reorganization can change the structure without settling how work moves day to day. Bain's January 2026 research reported that 88% of senior leaders believed a new structure would achieve its aims, while 36% of the people working in it agreed. The same research reported considerable work changes for 90% of middle managers and sufficient support for only 22% of employees.
Bain's conclusion is that structure has to be translated into workflows, decision rights, and new operating habits. Moving the boxes does not establish that the execution path changed. We trace the approvals, handoffs, queues, work in progress, and decision routes people actually live.
Is this just a wellness or burnout session?
No. We start with queues, approvals, handoffs, rework, work in progress, decision rights, and manager bottlenecks. Those conditions slow execution on their own.
Then we look at whether the same conditions are also reducing access to existing skill. We do not ask employees to become more resilient, and we do not treat a structural bottleneck as an individual wellbeing problem.
What if the problem is not a capacity problem?
Then we say so, and the queue you found is still a queue. A broken handoff, an unclear approval, and a rework loop do not disappear because the capacity read came back weak.
A real skill gap, poor role fit, the wrong strategy, or ordinary error may be the better explanation. Tooling, staffing levels, incentive design, and external dependencies can create genuine execution drag that falls outside what we would take on. Unclear ownership, decision rights, reopening, and concentrated approvals stay inside the work-path investigation.
Bring the pattern. Leave with the next test.
Tell us the recurring execution problem, who sees it from different points in the path, and what dates, counts, or examples you already have. We will confirm whether the Diagnostic is the right format, what it would cost, and what a realistic output looks like.