Interpret the allocation and name the imbalances
Reads the per-client load table and contracted terms, then names which clients are over-consuming, which are being crowded out, and where context-switching is costliest — a plain diagnostic ready for action.
In / outPer-client time totals + contracted terms → named diagnosis of imbalances and crowding-out
You might say…
“I had the numbers but I couldn't see what they meant until someone helped me name the pattern.”
What it does
Given the per-client load table and the contracted terms, reasons out where time is genuinely going wrong — which clients are over-consuming, which are being crowded out, where context-switching is costliest — and states the diagnosis in plain terms ready for action. Used as the interpretive read of the load picture, the diagnostic that precedes any rebalancing.
Trigger: Use when you have the load table in front of you and need a clear diagnosis of what's actually wrong before deciding what to do about it.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation