What a capacity diagnostic actually measures
A third of your talent is making decisions with a brain running at 80%. Engagement surveys won't show you that — a capacity diagnostic will.
The question we get in the first meeting is almost always the same: we already run an engagement survey, so what would a diagnostic add? The honest answer is that the two instruments measure different things, and only one of them warns you early.
Engagement is sentiment. Capacity is structure.
An engagement survey asks people how they feel about working here. A capacity diagnostic asks what the work is costing them to do. Those two readings can diverge for two or three quarters, which is why an engagement score can look stable right up to the quarter where three senior people resign in five weeks.
Sentiment is also easy to distort. People answer engagement questions with one eye on who reads the results. Load is harder to perform — a calendar with no recovery window in it says the same thing regardless of what anyone writes in a free-text box.
What does a capacity diagnostic actually measure?
The diagnostic separates load into five types rather than treating stress as one undifferentiated quantity: decisional, cognitive, emotional, relational, and administrative. The separation matters because the interventions are completely different.
A team drowning in administrative load needs process work — a form removed, an approval level deleted. A team carrying emotional load, because they absorb the distress of the clients or patients they serve, needs something else entirely. Give the second team a process audit and you spend a budget without touching the load that is actually consuming them.
Three levels, read together
We read the organization at three levels: the individual manager, the team, and the structures that make either sustainable or impossible. A single level on its own is misleading. Individual scores without structural context produce a resilience program, which quietly tells people the problem is their coping. Structural analysis without individual data produces a reorganization nobody can connect to their week.
The interesting findings usually sit between the levels — a cohort whose individual readings are fine but whose team-level demand is only survivable because two people are working evenings nobody has counted.
What do I get at the end of a capacity diagnostic?
Not a score. A score invites the wrong conversation: is 71 good? The output is a map of where load has concentrated, which load type dominates in each function, and what the organization would lose first if nothing changed — named roles, named capabilities, not a risk-register abstraction.
That map is what converts a mood into an operating-review topic. It is also the baseline. Ninety days after the intervention we re-measure with the same instrument, so the conversation about whether it worked is settled by the same numbers that started it.
Before you commission one
A diagnostic is only worth running if you are willing to act on a finding you did not expect. We have delivered results showing that the load was concentrated in a function the executive team considered stable, and results showing that the program the client had already budgeted for addressed the wrong load type.
Decide in advance who owns the response and which quarter it lands in. A diagnostic that produces a well-received presentation and no structural change has cost you money and taught your managers that measuring the problem is the end of it.
The diagnostic is the first stage of our organizational performance method, the Capacity Cycle™ — nothing is prescribed before it runs.