Diagnose and clear the producer's blocker
Takes a specific reported blockage, diagnoses what is actually in the way, and makes the call or supplies the clarification that lets the producer continue — in one sitting.
In / outReported blockage description + task context → Diagnosis of what is actually blocking + call or clarification that unblocks the producer
You might say…
“Someone is stuck and waiting on me — I don't want a long back-and-forth to surface what they need, I want to diagnose it and unblock them in one hit.”
What it does
Takes a specific reported blockage — an ambiguous brief, a stuck analytical approach, a missing data/stakeholder access, an unmade scope call — diagnoses what is actually in the way, and makes the call or supplies the clarification that lets the producer continue, in one sitting. Used reactively when a named producer is stuck on a named task. Single human-in-loop judgement; reactive and task-level.
Trigger: Use reactively when a named producer is stuck on a named task and needs a decision or clarification from the lead to move forward.
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