01
Gather the blocker evidence
Capture the expected outcome, visible symptom, attempted actions, known constraints, and delivery impact. Keep facts separate from interpretations.
Made for Engineering Managers
Find the Real Blocker Before Escalating
Also useful for: people in Engineering Managers
20 min
Intermediate
Engineering Managers
Engineering Manager
Improve Team Performance
Career outcome:
Avoid Professional Risk
Separate the visible symptom from the dependency, decision, access gap, or technical unknown that's actually stopping delivery.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Diagnose the constraint behind a stalled task so the team takes the right action, assigns the right owner, and escalates only when escalation will help.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Trace and test the constraint
Use the compiled prompt to rank plausible blocker types and identify the fastest check that separates the leading explanation from weaker alternatives.
03
Choose the next move
Convert the diagnosis into a bounded action with a named owner, deadline, expected signal, and checkpoint.
04
Set the escalation line
Define when escalation becomes useful, then send a status update that distinguishes the confirmed blocker from the visible delay.
Make Your Play
Find the Real Blocker Before Escalating
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Describe the task, the expected outcome, the current owner, and where it sits in the delivery plan.
0/10000
State what appears stalled and include the latest concrete status rather than an interpretation.
0/10000
List the actions already taken, what happened after each action, and any unanswered questions.
0/10000
List known dependencies, pending decisions, missing permissions, unclear requirements, and technical unknowns.
0/10000
Select the current effect on delivery.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Gather the blocker evidence
Capture the expected outcome, visible symptom, attempted actions, known constraints, and delivery impact. Keep facts separate from interpretations.
02
Trace and test the constraint
Use the compiled prompt to rank plausible blocker types and identify the fastest check that separates the leading explanation from weaker alternatives.
03
Choose the next move
Convert the diagnosis into a bounded action with a named owner, deadline, expected signal, and checkpoint.
04
Set the escalation line
Define when escalation becomes useful, then send a status update that distinguishes the confirmed blocker from the visible delay.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Use facts from tickets, messages, and recent conversations. If something is only a guess, label it as a guess. A blocker is the condition that must change before work can move, not simply the fact that work is late.
Advanced instructions
Challenge the first explanation, especially if it centers on an individual. Look for hidden approval paths, unclear ownership, environment access, interface contracts, unresolved product choices, and unknown technical behavior. Set escalation around authority and impact, not frustration.
Use this when
An engineering task has stopped moving, updates are vague, several possible causes are being discussed, or someone is asking for escalation before the constraint is clear.
You'll need
- Task context
- Visible symptom
- Attempts and results
- Known constraints
- Delivery impact
You'll get
- The visible symptom separated from the underlying constraint
- The leading blocker hypothesis supported by available evidence
- The fastest confirmation check identified
- The next owner, action, deadline, and checkpoint defined
- The escalation condition stated
- A ready-to-send blocker update drafted.
By the end of this playbook
You will have:
- The visible symptom separated from the underlying constraint
- The leading blocker hypothesis supported by available evidence
- The fastest confirmation check identified
- The next owner, action, deadline, and checkpoint defined
- The escalation condition stated
- A ready-to-send blocker update drafted.
Examples
Progress 1 of 4