Reason where team capacity diverges from remaining work
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.
In / outCurrent team composition + effort logged to date + work remaining → Identified over/under-loads + named adjustment with revised commitment
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
Given the current team composition, logged effort to date, and the work remaining, reasons where a producer is over- or under-loaded and what the adjustment should be — swap a person, scale subcontractor hours, or add capacity for expanded scope — naming the change and the revised commitment it implies. Used mid-engagement when a resourcing adjustment is triggered by a capacity-versus-demand mismatch.
Trigger: Use mid-engagement when a capacity-versus-demand signal appears and you need a reasoned resourcing adjustment, not just a status update.
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