Diagnose whether an overload signal is transient or structural
Takes a flagged utilisation pattern and judges whether it is a transient spike, a schedulable conflict, or a structural capacity shortfall warranting escalation to hiring.
In / outFlagged utilisation pattern with context → categorised diagnosis (transient / schedulable / structural) with recommended response
You might say…
“The system flagged someone at 130% but I don't know if that resolves itself next week or if I have a real hiring problem.”
What it does
Takes a flagged utilisation pattern and reasons about whether it is a one-off spike that will self-resolve, a schedulable conflict, or a structural capacity shortfall that warrants escalation to hiring. Used when a warning fires and the principal needs a judgement on what kind of problem it actually is before deciding how to respond.
Trigger: Use when a utilisation warning fires and the principal needs a judgement on what kind of problem it is before deciding how to respond.
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