Most engineers become leads because they were good at shipping software. Then the job quietly changes. The highest-leverage hour of your week is no longer the one you spend in the code, it is the 30 minutes you spend with each person on your team.

The evidence for this is unusually consistent. Gallup reports that managers account for at least 70% of the variance in employee engagement scores across business units. Google's Project Oxygen, which set out to prove that managers did not matter much in an engineering culture, found the opposite, and "be a good coach" topped its list of what its best managers did. Regular one-on-ones and specific feedback are the most concrete form that coaching takes.

Yet one-on-ones are often the first meeting to be cancelled, and feedback is the conversation most leads postpone. This cheatsheet is the version I wish I had when I started: what a 1:1 is for, how to run it, what to ask, how to give and receive feedback, and what to say in the awkward situations.

1. What a one-on-one is (and is not)

A one-on-one is a recurring, private conversation between a lead and one report, owned primarily by the report. Andy Grove framed it in High Output Management (1983) as the subordinate's meeting: their agenda, their concerns, with the manager there to listen, coach and unblock.

A 1:1 is A 1:1 is not
Their time to raise what matters to them A status update (use the standup, the board or a written update)
A place for career, growth, friction and feedback in both directions A performance review, though it should mean reviews contain no surprises
Recurring and protected Something you cancel whenever a "real" meeting appears
Mostly listening (aim for them talking 60-70% of the time) Your monologue about priorities
Where small problems surface early The only place problems are allowed to surface

The simplest test: if the meeting could be replaced by reading a ticket board, it was a status meeting.

2. Cadence and logistics

Situation Cadence Length
Default for a direct report Weekly 30 min
New hire (first 90 days) or someone going through a hard time Weekly, never skip 30-45 min
Senior, autonomous report who prefers less Every two weeks 45-60 min
Skip-level (your reports' reports) Every 1-3 months 30 min
Peer leads, your own manager Every 1-2 weeks 30 min

Rules that pay off:

  • Weekly beats long and rare. Gallup's research on manager conversations found that short, frequent check-ins (it suggests 15-30 minutes weekly) work better than long, infrequent ones, and that 80% of employees who received meaningful feedback in the past week were fully engaged.
  • Reschedule, never cancel. A cancelled 1:1 tells the person exactly where they rank. If you must move it, move it in the same week.
  • Same time, same place. Predictability lets people save things up for it instead of interrupting you.
  • Keep a shared doc per person. Both of you add topics during the week. It becomes the history of the relationship.
  • Budget it. With 8 reports, weekly 30-minute 1:1s cost 4 hours a week. That is the job, not overhead.

3. An agenda template

Keep the structure light. The report's topics go first, always.

1:1 - <Name> / <Lead> - <date>

1. Their topics (they add these during the week)
   -
2. Check-in: how are you, really? energy 1-5 and why
3. Blockers: anything I can remove or escalate?
4. Lead's topics (only after theirs)
   -
5. Growth: (monthly) progress on goals, next stretch opportunity
6. Feedback: (both directions) one thing to keep, one to change
7. Actions
   - [ ] owner - action - due

Not every section happens every week. Career and growth topics deserve a dedicated 1:1 roughly once a month, otherwise they get crowded out by the urgent.

4. Questions by goal

Good questions are specific and open. "Any problems?" gets "no". "What was the most frustrating part of last week?" gets an answer.

Goal Questions
Opening / morale What is on your mind this week? On a scale of 1-5, how is your energy, and what would move it up one? What was the best and worst part of the last two weeks?
Blockers What is slowing you down that I might not see? Is anything waiting on a decision from me or someone else? If you had one extra day this sprint, what would you spend it on?
Work and context Is there anything about our priorities that does not make sense to you? Which meeting would you delete?
Career Where do you want to be in 2-3 years, and what would you need to learn to get there? What work energizes you, and what drains you?
Recognition What are you proud of recently that I might have missed?
Team health Is there anyone you find hard to work with? Do you feel safe disagreeing in design reviews?
Retention What would make you consider leaving? What would make this the best job you have had?
Feedback on you What is one thing I could do differently that would help you? What should I stop doing? What did I do recently that was unhelpful?

The questions about yourself only work if you ask them regularly and react well the first time (section 7). Ask the same question in a slightly different form for several weeks; the honest answer often comes on the third try.

5. Feedback models: SBI, Radical Candor, feedforward

Three models cover nearly every situation. They are complementary, not rival schools.

SBI: Situation, Behavior, Impact

Developed by the Center for Creative Leadership (CCL), SBI is the most practical structure for a single piece of feedback, positive or negative.

Step What to say Example
Situation When and where, specifically "In Tuesday's incident review..."
Behavior What the person observably did. No adjectives about character "...you interrupted Ana twice while she was explaining the timeline..."
Impact The effect on you, the team or the outcome "...and she stopped contributing. We missed the detail about the config change until the next day."
Intent (optional, CCL's SBII extension) Ask, do not assume "What was going on for you in that moment?"

The value of SBI is that it removes the two things that trigger defensiveness: vague generalities ("you always...") and judgments of character ("you are rude"). Use it for praise too: "In the design review, you wrote down the rollback plan before anyone asked. That made the approval a five-minute conversation."

Radical Candor: care personally, challenge directly

Kim Scott's Radical Candor (2017) gives the stance rather than the script. Feedback lands when you care personally and challenge directly at the same time. The four quadrants:

Challenge directly: low Challenge directly: high
Care personally: high Ruinous Empathy (too nice to say it, so they never learn) Radical Candor
Care personally: low Manipulative Insincerity (neither kind nor honest) Obnoxious Aggression (honest but harsh)

Most new engineering leads fail in Ruinous Empathy: they like their team, so they soften feedback until it disappears. The fix is not to become harsh, it is to be clear and to show you are on their side.

Feedforward

Marshall Goldsmith's feedforward (Leader to Leader, 2002) flips the direction: instead of dissecting what went wrong, ask for or offer suggestions for the future. "Next time you run an incident review, try asking each person for one observation before opening the floor." You cannot change the past, and suggestions about the future are easier to hear. Feedforward is especially useful for peers, for skills (presenting, writing, estimating) and when asking for input on yourself.

Rule of thumb: SBI for a specific event, Radical Candor as a check on whether you are saying it at all, feedforward for developing a skill over time.

6. Giving feedback: the mechanics

  • Soon. Within a day or two. Feedback saved for the quarterly review is a history lesson.
  • Praise in public, correct in private. Unless the person dislikes public praise. Ask.
  • One message at a time. A list of seven issues is a performance review, not feedback.
  • Specific beats nice. "Good job on the release" is noise. "The migration plan with the dry-run step meant zero rollbacks" is information.
  • No sandwich. Wrapping criticism between two compliments trains people to brace whenever you say something nice.
  • End with a question. "How do you see it?" turns a verdict into a conversation, and you may be missing context.
  • Follow up. Notice when they change the behavior and say so. That closes the loop.

7. Receiving feedback

Your reports see your blind spots every day. Whether they tell you depends on what happened the last time someone did.

Do Do not
Say "thank you" first, and mean it Explain why you did it
Ask one clarifying question: "Can you give me an example?" Debate whether the example counts
Write it down where they can see Promise a big change you will not keep
Come back within a week with what you changed Bring it up later as a counter-argument
Ask a specific question to make it easy: "What should I stop doing in planning?" Ask "any feedback for me?" and accept "no"

Separate hearing from agreeing. You can thank someone for feedback and decide later, with reasons you share, not to act on it.

8. Documenting

Short notes protect both of you and make reviews fair.

  • After each 1:1: 3-5 bullets in the shared doc: topics, decisions, actions with owners.
  • Private notes (yours only): observations for performance discussions, written as SBI facts, not opinions. Assume the person may one day read them.
  • Wins log: a running list of their accomplishments. At review time you will remember the last six weeks; the log remembers the year. Encourage them to keep their own too.
  • Do not record personal or health details beyond what is needed to act (and follow your HR rules on this).

9. Skip-levels

When you lead leads, skip-level 1:1s are how you learn what is actually happening, two levels down.

  • Purpose: listen, give context about the bigger picture, and spot systemic problems. Not to manage around the middle manager.
  • Tell the manager first and share themes, not attributions. If people fear their words travel back verbatim, you will only hear good news.
  • Useful questions: What is getting in the way of the team? What do you wish leadership knew? Is there anything we are doing that seems pointless? What is one thing your manager does that you would want every manager to do?
  • Never reverse a manager's decision in a skip-level. Take it to the manager.
  • Act on themes and say so publicly ("Several people mentioned the on-call load, here is what we are changing"). Otherwise the next round is silent.

10. Remote and hybrid specifics

  • Camera on, if they are comfortable, and no multitasking. In remote teams the 1:1 may be the only time someone has your undivided attention all week.
  • More frequent, shorter touches. Remote work removes hallway signals. Gallup has found that engagement is highest among employees who have some form of daily communication with their manager, whether face to face, by phone or digital.
  • Watch for time zones. Rotate inconvenient slots, so the same person is not always taking the call at 8 p.m.
  • Say the quiet things out loud. "How are you finding the workload?" replaces the stressed face you would have noticed in the office.
  • Meet in person when you can, especially for difficult conversations, onboarding and career discussions.

11. Anti-patterns

Anti-pattern Why it hurts Fix
Status-update 1:1 Wastes the one private channel you have Move status to async updates; open with "What is on your mind?"
Cancelling repeatedly Signals they are low priority Reschedule in the same week, never cancel twice in a row
Lead talks 80% of the time You learn nothing Their topics first; count your sentences
Feedback only at review time Surprises destroy trust Feedback within days, reviews summarize what was already said
Ruinous empathy They keep repeating the mistake and find out late Say it clearly, with SBI, once
Solving every problem for them They stay dependent on you Ask "What options do you see?" before offering yours

12. Situations: what to say

Situation What to say
They have nothing to discuss "No problem. Can I ask you something I have been curious about: what part of the codebase would you rewrite if you could?"
Repeated missed deadlines "The last two sprints, the API work slipped by about a week each time. That pushed the mobile release. What is getting in the way? What would make estimates more reliable?"
Great work you want to reinforce "Your write-up of the outage was the clearest postmortem we have had. Other teams are now copying the format. Can I share it at the all-hands?"
Behavior in meetings "In yesterday's planning, you dismissed Sam's proposal before he finished. He went quiet for the rest of the meeting. What was going on?"
They want a promotion you do not think they are ready for "I want to help you get there. Here is the gap I see against the next level, with two examples. Let us pick one project where you can show it, and review in six weeks."
They seem burned out "You seem more tired than usual lately. How are you, honestly? What could we take off your plate?"
Bad news from above (reorg, cancelled project) "Here is what I know, here is what I do not know yet, and here is when I expect to know more. What questions do you have?"
They say they are thinking of leaving "I appreciate you telling me. What is driving it? Is there anything we could change that would make you want to stay?"

Why this matters

  • Managers are the biggest lever on engagement. Gallup's 70% figure means the team's experience of work is largely the lead's experience to shape.
  • 1:1s are the cheapest early-warning system you have. Attrition, burnout and bad technical decisions usually show up there weeks before they show up in metrics.
  • Specific feedback compounds. Each concrete, timely message saves months of someone repeating a mistake or not knowing what to repeat.
  • Feedback that flows up makes you better. Your team is the only group that sees your management every day.
  • It is a skill, not a personality trait. Google's research turned good management into a list of trainable behaviors. Structure and habit beat charisma.

Final Thoughts

You do not need to be a natural people person to run good one-on-ones. You need a recurring slot that you protect, a shared doc, a few good questions, the discipline to give specific feedback soon, and the humility to ask for it back.

Start next week: put a weekly 30-minute 1:1 with every report on the calendar, open each one with "What is on your mind?", and give one piece of SBI feedback, positive or negative, before Friday. In three months, your team will tell you things you would otherwise have learned from a resignation letter.

Sources