Transition a new lead from tactical execution to coaching

Break the habit of stepping into hands-on tasks and shift focus toward delegating and developing team members. Use this when a newly promoted lead feels overwhelmed by execution.

You getRoot Cause Diagnosis, delegation Plan and script

Prompt

Prompt
Act as an executive coach for engineering and operations managers.

First, ask me 3 short numbered questions in one message and wait for my replies:
1. What specific task did you rescue or take over this week instead of letting your report handle it?
2. What was your main fear or reason for doing it yourself instead of delegating?
3. What is the current skill level of the person assigned to that work?

After I reply, build a practical coaching plan. Focus on delegation boundaries, specific questions to guide the report without doing the work, and how to inspect progress safely.

Output format:
- Root Cause Diagnosis: Why the handoff failed
- Delegation Plan: Steps to hand the work back with clear check-ins
- Script: Exact phrases to use in your next 1-on-1 to guide without rescuing
- Inspection Cadence: Specific checkpoints to ensure quality without micromanaging

Example output

Example for: an engineering lead who took over fixing critical database bugs instead of letting a mid-level engineer debug them

Root Cause Diagnosis

You stepped in because the cost of failure felt high and debugging yourself was faster than explaining the system architecture. The underlying issue is lack of shared mental models, not the engineer's inability to learn.

Delegation Plan
  1. Scope the boundary: Assign the engineer the root-cause analysis and reproduction steps, while keeping final review authority.
  2. Schedule a 20-minute pairing session focused on observing their thought process rather than touching the keyboard.
  3. Agree on an escalation threshold: if blocked for more than 45 minutes, they document three hypotheses before asking for guidance.
Script

"I want you to own this resolution completely because handling production issues is essential for your growth. I stepped in earlier to keep things moving, but that took away your learning opportunity. Walk me through what you see right now, and let's outline your testing plan together before you deploy."

Inspection Cadence
  • Checkpoint 1: Written bug diagnosis and hypothesis within 2 hours.
  • Checkpoint 2: Draft fix reviewed asynchronously in pull request.
  • Checkpoint 3: Post-incident review draft completed within 24 hours of deploy.
Written by AI from this prompt. Your results will vary.

Paste this prompt into ChatGPT, Claude or Gemini. Answer the three questions candidly in your next message. Follow up by asking: "Provide three roleplay scenarios where the report pushes back and asks me to do it for them."

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Distribute invisible glue work across your team

Audit uncredited coordination, onboarding, and documentation duties to protect high performers from burnout. Use this when reliable contributors carry too much operational weight.