01
Draft the ownership-returning reply
Turn the incoming question, decision ownership, and relevant constraints into a short response that asks for a recommendation instead of supplying one.
Made for Engineering Managers
Reply Without Taking Over
Also useful for: people in Engineering Managers, people in Technical Leads
5 min
Beginner
Boundaries
Become a Better Manager
Draft a concise response that helps an engineer move forward while keeping the technical decision in the right hands.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Keep technical ownership with the team while still providing enough context to prevent delays, confusion, or unnecessary escalation.
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
Reply Without Taking Over
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
Paste the technical question or request you received, including any options already mentioned.
0/10000
Name the person, pair, or team responsible for recommending or making this technical decision.
List only the constraints, past decisions, deadlines, or risks that should shape the response.
0/10000
Choose the tone that best fits the conversation.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Draft the ownership-returning reply
Turn the incoming question, decision ownership, and relevant constraints into a short response that asks for a recommendation instead of supplying one.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the question as it was asked. Name the person or team responsible for the technical call, then add only the context that could change the decision. Send the generated reply after checking that it doesn’t contain a hidden recommendation.
Advanced instructions
Use the context field to add constraints, prior decisions, or deadlines without steering toward a preferred implementation. If the reply still sounds like approval, replace approval language with a request for a recommendation and supporting tradeoffs.
Use this when
An engineer asks what to do, and you want to help without making the technical decision for them.
You'll need
- Technical question
- Decision owner
- Useful context
- Reply tone
You'll get
- A reply under 90 words
- Technical ownership stated or reinforced
- Relevant context included without a supplied solution
- A concrete next action requested.
By the end of this playbook
You will have:
- A reply under 90 words
- Technical ownership stated or reinforced
- Relevant context included without a supplied solution
- A concrete next action requested.
Examples
Progress 1 of 1