01
Build and send the delegation brief
Run the compiled prompt, check the proposed authority and escalation boundaries, then send the final handoff message to the named decider.
Made for Engineering Managers
Delegate a Technical Decision
Also useful for: people in Engineering Managers, people in Technical Leads
12 min
Beginner
Boundaries
Become a Better Manager
Need to Make a Decision
Hand off an architecture or implementation decision with clear authority, constraints, criteria, and a firm deadline.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Keep technical work moving without becoming the default answer for every choice.
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
Delegate a Technical Decision
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 architecture or implementation choice that needs an owner and decision.
0/10000
Name the engineer or technical lead who should own the decision and briefly note relevant experience.
Explain why the decision matters now, including the work it is blocking or the risk of delay.
0/10000
Choose how much decision authority the delegate should receive.
List fixed requirements, excluded areas, budget or timing limits, and decisions that remain outside the handoff.
0/10000
List the factors that should drive the choice, in priority order if possible.
0/10000
Enter the deadline, people who need input or notice, documentation location, and conditions that should trigger escalation.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Build and send the delegation brief
Run the compiled prompt, check the proposed authority and escalation boundaries, then send the final handoff message to the named decider.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Use a real decision that is currently waiting on you. Name one person, choose the authority level that matches the risk, and include any constraint that can’t be changed.
Paste the completed prompt into an AI assistant. Review every “Confirm:” item before sending the handoff message.
Advanced instructions
Add measurable thresholds for cost, latency, reliability, security, migration effort, or delivery time when they matter. Replace vague escalation rules with specific triggers, such as a missed service-level target or a change that affects another team’s contract.
Use this when
You have a pending technical decision that a capable engineer or technical lead should own, but the scope, authority, or escalation path is unclear.
You'll need
- Pending technical decision
- Named decider
- Decision context
- Authority level
- Boundaries and constraints
- Decision criteria
- Deadline and escalation details
You'll get
- A single technical decision framed as a precise question
- A named decider with explicit decision authority
- Independent decision boundaries separated from approval conditions
- Prioritized criteria tied to the technical and delivery context
- A deadline, documentation location, and escalation path
- A handoff message ready to send
By the end of this playbook
You will have:
- A single technical decision framed as a precise question
- A named decider with explicit decision authority
- Independent decision boundaries separated from approval conditions
- Prioritized criteria tied to the technical and delivery context
- A deadline, documentation location, and escalation path
- A handoff message ready to send
Examples
Progress 1 of 1