Made for Engineering Managers
Unblock the Team Without Solving the Problem
Also useful for: people in Engineering Managers
Guide a blocked engineer toward a workable next step without taking over the technical decision or becoming the permanent escalation point.
We'll use them to write your prompt.
Make Your Play
Give us the situation. We’ll build the prompt.
Keep work moving while strengthening technical ownership.
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.
Make Your Play
Unblock the Team Without Solving the Problem
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 what is blocked, what decision is needed, and what can't move forward yet.
0/10000
Select the level that best reflects the current time pressure and impact.
Name the person or team expected to make the decision, including any uncertainty about ownership.
List the facts, test results, constraints, and assumptions already available.
0/10000
List the options raised so far and the stated tradeoffs for each one.
0/10000
Describe deadlines, approval limits, safety concerns, and conditions that require escalation.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Start with the facts you know. If the engineer hasn’t suggested any options, write that plainly instead of filling the gap yourself. Remove passwords, access tokens, customer data, and other sensitive details before submitting.
Advanced instructions
Use the sequence during an active escalation. Push for a reversible experiment when possible, define an escalation threshold, and note whether repeated blockages point to unclear ownership, missing standards, or an unhealthy approval path.
Use this when
An engineer brings you a technical problem and expects an answer, but the decision should stay with the team unless the risk or urgency requires escalation.
You'll need
- Blocked work
- Urgency
- Current owner
- Known context and evidence
- Options already considered
- Decision boundaries and risks
You'll get
- The blockage separated into facts, assumptions, and unknowns
- The decision owner confirmed or reassigned
- Critical missing context listed
- Coaching questions ready for the conversation
- A bounded next move with an escalation threshold
- A named owner, deadline, and check-in point.
By the end of this playbook
You will have:
- The blockage separated into facts, assumptions, and unknowns
- The decision owner confirmed or reassigned
- Critical missing context listed
- Coaching questions ready for the conversation
- A bounded next move with an escalation threshold
- A named owner, deadline, and check-in point.