leadership
One-on-One Coaching
Run effective 1:1 meetings with direct reports — structured coaching conversations, feedback delivery using SBI framework, career growth planning, and trust-building techniques.
one-on-onecoachingfeedbackcareer-growthmanagementSBI
Works well with agents
Works well with skills
one-on-one-coaching/
SKILL.md
Markdown| 1 | |
| 2 | # One-on-One Coaching |
| 3 | |
| 4 | ## Before you start |
| 5 | |
| 6 | Gather the following from the user: |
| 7 | |
| 8 | 1. **Who is the direct report?** (Role, tenure, seniority level) |
| 9 | 2. **What type of 1:1 is this?** (Regular check-in, feedback session, career growth, or blocker resolution) |
| 10 | 3. **What happened since the last 1:1?** (Key events, deliverables, incidents, or team changes) |
| 11 | 4. **Is there specific feedback to deliver?** (Positive reinforcement or constructive feedback with a concrete situation in mind) |
| 12 | |
| 13 | If the user says "just a regular 1:1," push back: "What's the one thing you'd regret not discussing? Start there." |
| 14 | |
| 15 | ## 1:1 meeting framework |
| 16 | |
| 17 | ### Preparation (5 minutes before) |
| 18 | |
| 19 | 1. Review notes from the last 1:1 — check on any commitments made by either side. |
| 20 | 2. Pick 1-2 topics you want to raise. Your report owns the rest of the agenda. |
| 21 | 3. Write down the single most important question you want answered by the end. |
| 22 | |
| 23 | ### Opening (first 3 minutes) |
| 24 | |
| 25 | Start with a genuine, open-ended question. Rotate through these: |
| 26 | |
| 27 | - "What's on your mind?" |
| 28 | - "What's been the highlight of your week?" |
| 29 | - "What's something that frustrated you recently?" |
| 30 | |
| 31 | **Do not** open with status updates. If the report starts with a status dump, redirect: "I can read that in the standup notes — what do you actually want to talk about?" |
| 32 | |
| 33 | ### Core conversation |
| 34 | |
| 35 | Choose the conversation type that fits the meeting purpose. You can combine types within a single 1:1. |
| 36 | |
| 37 | #### Career growth conversation |
| 38 | |
| 39 | 1. Ask: "Where do you want to be in 12 months? What skills would you need to get there?" |
| 40 | 2. Identify one concrete gap between current performance and the next level. |
| 41 | 3. Co-create a 30-day action: a project, stretch assignment, or learning goal that addresses the gap. |
| 42 | 4. Write it down during the meeting — vague aspirations without written actions don't stick. |
| 43 | |
| 44 | #### Feedback conversation (use SBI framework) |
| 45 | |
| 46 | Deliver feedback using **Situation-Behavior-Impact**. Never wing it — prepare the SBI before the meeting. |
| 47 | |
| 48 | **SBI feedback template:** |
| 49 | |
| 50 | ``` |
| 51 | Situation: [When and where — be specific] |
| 52 | Behavior: [What the person did — observable actions only, not intent] |
| 53 | Impact: [The effect on the team, project, or you] |
| 54 | ``` |
| 55 | |
| 56 | **Positive example:** |
| 57 | |
| 58 | ``` |
| 59 | Situation: During Thursday's incident review |
| 60 | Behavior: You walked the team through the root cause timeline |
| 61 | with clear evidence before proposing a fix |
| 62 | Impact: The team aligned on a solution in 15 minutes instead |
| 63 | of debating hypotheticals — it saved us at least an hour |
| 64 | ``` |
| 65 | |
| 66 | **Constructive example:** |
| 67 | |
| 68 | ``` |
| 69 | Situation: In yesterday's sprint planning |
| 70 | Behavior: You committed to 4 large stories without raising |
| 71 | concerns about the migration work still in progress |
| 72 | Impact: The team now has a plan that's likely unrealistic, |
| 73 | and I'm worried we'll have to cut scope mid-sprint |
| 74 | ``` |
| 75 | |
| 76 | After delivering constructive feedback, ask: "What's your perspective on this?" Then listen. Feedback is a dialogue, not a verdict. |
| 77 | |
| 78 | #### Blocker resolution |
| 79 | |
| 80 | 1. Ask: "What's slowing you down the most right now?" |
| 81 | 2. Classify the blocker: **technical**, **process**, **people**, or **clarity**. |
| 82 | 3. For each blocker, decide who owns the resolution and by when. |
| 83 | 4. If the blocker is outside your control, commit to escalating it with a specific timeline. |
| 84 | |
| 85 | #### Regular check-in |
| 86 | |
| 87 | Use a lightweight structure when there's no specific agenda: |
| 88 | |
| 89 | 1. **Energy check**: "On a scale of 1-5, how are you feeling about work right now?" Follow up on anything below 3. |
| 90 | 2. **Wins**: "What went well since we last talked?" Acknowledge it explicitly. |
| 91 | 3. **Concerns**: "What's one thing that could go better?" |
| 92 | 4. **Support**: "What do you need from me this week?" |
| 93 | |
| 94 | ### Closing (last 3 minutes) |
| 95 | |
| 96 | 1. Summarize commitments: "Here's what I heard us agree to..." — read them back. |
| 97 | 2. Ask: "Is there anything we didn't cover that you wanted to raise?" |
| 98 | 3. Write down action items with owners and due dates before ending the call. |
| 99 | |
| 100 | ## Quality checklist |
| 101 | |
| 102 | Before ending the 1:1, verify: |
| 103 | |
| 104 | - [ ] The report spoke more than you did (aim for 70/30 split) |
| 105 | - [ ] At least one action item has a specific owner and due date |
| 106 | - [ ] You asked at least one question you didn't already know the answer to |
| 107 | - [ ] Feedback (if delivered) used the SBI format with a concrete situation |
| 108 | - [ ] Career growth topics were discussed at least once per month |
| 109 | - [ ] You did not solve problems the report could solve themselves — you coached, not directed |
| 110 | - [ ] Notes are written down, not left to memory |
| 111 | |
| 112 | ## Common mistakes |
| 113 | |
| 114 | - **Turning 1:1s into status meetings.** Status belongs in standups and dashboards. 1:1s are for the topics that don't have another venue. |
| 115 | - **Skipping or rescheduling repeatedly.** Cancelling 1:1s signals that the relationship isn't a priority. Reschedule same-week if you must, but never skip two in a row. |
| 116 | - **Giving feedback without a specific situation.** "You need to communicate better" is not feedback. Without a concrete SBI, the report has nothing to act on. |
| 117 | - **Doing all the talking.** If you're speaking more than 30% of the time, you're not coaching — you're lecturing. Ask a question and wait. |
| 118 | - **Avoiding hard conversations.** Delaying difficult feedback doesn't make it easier — it makes it stale. Deliver it within a week of the situation. |
| 119 | - **No follow-through on action items.** If you committed to unblocking something and didn't, own it at the next 1:1 before asking about their commitments. |
| 120 |