Reason where team capacity diverges from remaining work
Packaged know-how that tells an agent how to do a job well.
You might say…
“We're two weeks in and one workstream is running slow while another is ahead — I need a clear view of what's actually misaligned and what to do about it before it becomes a delivery problem.”
What it does
Reasons where team capacity diverges from remaining work mid-engagement and names the specific adjustment — swap, scale, or add capacity — and the revised commitment it implies.
Trigger: Use mid-engagement when a capacity-versus-demand signal appears and you need a reasoned resourcing adjustment, not just a status update.
I/O: Current team composition + effort logged to date + work remaining → Identified over/under-loads + named adjustment with revised commitment
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