Build a coaching plan for a skill gap

Create a lightweight, sprint-friendly coaching plan that helps a team member close a practical capability gap without burning them out.

You getObjective & Target Observable Behavior, 4-Week Milestone Schedule and 3 Coaching Questions for Weekly 1-on-1s

Prompt

Prompt
You are an engineering and talent development coach helping a manager address an employee skill gap.

- Build a practical 4-week coaching plan that fits into standard 2-week sprint cycles (1 to 2 hours of coaching per week).
- Focus on observable skills, peer shadowing, low-risk practice assignments, and concrete evidence of improvement.
- Avoid generic career development advice; make every milestone verifiable.

Output format:
- Objective & Target Observable Behavior
- 4-Week Milestone Schedule (Week, Focus Area, Manager Action, Employee Action, Success Check)
- 3 Coaching Questions for Weekly 1-on-1s
- How to Verify Independent Mastery

Employee details and the specific skill gap are below:

Example output

Example for: junior software engineer struggling with production incident communication

Objective & Target Observable Behavior

Enable the engineer to independently run customer-facing incident communications during minor outages, providing timely, jargon-free status updates every 20 minutes without manager intervention.

4-Week Milestone Schedule
  • Week 1: Shadowing & Dissection

    • Manager Action: Walk through two previous post-mortems and share the standard status update template.
    • Employee Action: Shadow the on-call engineer during any staging drill or production ticket; draft dummy updates for review.
    • Success Check: Employee drafts a mock status update within 15 minutes of a simulated alert that meets clarity standards.
  • Week 2: Co-Pilot Incident Drafting

    • Manager Action: Review and approve drafted messages during active sprint cycles before publishing.
    • Employee Action: Write all initial Slack and status page announcements during team-level maintenance events.
    • Success Check: Drafts require zero major edits for technical tone or customer impact clarity.
  • Week 3: Supervised Solo Execution

    • Manager Action: Observe in silence during a scheduled release, stepping in only if safety is compromised.
    • Employee Action: Lead communication cadence across team channels throughout a release window.
    • Success Check: Updates sent at predictable 20-minute intervals without reminders.
  • Week 4: Independent On-Call Rotation

    • Manager Action: Review post-incident communications retroactively in the 1-on-1.
    • Employee Action: Own secondary responder comms during normal on-call shift.
    • Success Check: Incident channel is updated smoothly and post-incident note is logged within 24 hours.
3 Coaching Questions for Weekly 1-on-1s
  1. "When you were writing that update, what detail felt hardest to translate for a non-technical reader?"
  2. "What signal helped you decide it was time to post an update before having complete certainty?"
  3. "Where did you feel tempted to give technical excuses rather than next recovery steps?"
How to Verify Independent Mastery

The engineer completes two consecutive on-call shifts where stakeholder updates are delivered within SLA without pre-approval from senior staff.

Written by AI from this prompt. Your results will vary.

Paste the employee's role, the skill gap, and current performance observations into ChatGPT, Claude, or Gemini. Follow up by asking the model to write an encouraging script to introduce the coaching plan during your next 1-on-1 meeting.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Build a thirty-sixty-ninety day onboarding plan

Generate a clear, phased milestone roadmap for incoming team members to eliminate ambiguity. Use this during hiring or early onboarding to set transparent expectations.