One-on-ones are the backbone of engineering leadership. Done well, they build trust, surface problems early, and align individual growth with team goals. Done poorly, they feel like a checkbox—and your reports will disengage fast.
Here’s how to run effective engineering 1:1s: get the frequency right, use a simple agenda, and focus on outcomes instead of status updates.
Why Engineering 1:1s Matter
1:1s are not status meetings. If the only goal is “what did you do this week?”, you’re wasting time. The real goals are:
- Trust: A safe space to raise concerns, ideas, and career questions.
- Context: You understand what’s blocking or motivating each person.
- Alignment: You can tie their work and growth to team and company goals.
- Retention: People leave when they feel unheard. Regular, meaningful 1:1s reduce that risk.
Treat 1:1s as the primary channel for the human side of management. Status belongs in standups, tickets, or async updates.
How Often Should You Run 1:1s?
Weekly is the default that works for most teams. For senior engineers and stable contexts, biweekly can work if you keep the slot and protect it. For new joiners or people in a critical project or personal moment, weekly is non-negotiable.
- Duration: 30 minutes is enough for most. Use 45–60 minutes only when you’re doing deeper career or feedback conversations.
- Consistency: Same day and time every week. Cancelling often signals that 1:1s are low priority.
- Ownership: The report owns the agenda; you own the time and the follow-up. Make that explicit so they come prepared and feel in charge.
What to Put on the 1:1 Agenda
A light structure helps without turning the meeting into a form. Share this with your reports so they can prep.
1. Wins and blockers (5–10 min)
What went well? What’s blocking them (technical, process, or people)? This is not a full status report—just enough to know where to dig in or escalate.
2. Priorities and focus (5 min)
What are they focusing on next? Is that aligned with what you expect? Quick alignment here avoids surprises and overload.
3. Feedback and growth (5–10 min)
One thing they did well and one thing to improve. Also: what do they want to learn or get better at? Tie this to projects or opportunities when you can.
4. Career and wellbeing (remaining time)
Goals, concerns, or anything they want to talk about that isn’t “work in progress.” Leave room for silence; not every 1:1 needs a big topic.
You don’t need to hit every section every time. The structure is a guide, not a script. If something urgent or personal takes over, go with it and skip the rest.
Turning 1:1s Into Outcomes
Effective engineering 1:1s produce clear next steps, not just a nice chat.
- Take notes (with permission). Jot down commitments, feedback, and follow-ups. Share a short summary after the call so you’re both aligned.
- Follow up in public when it matters. If you agreed to unblock something or change a process, do it and mention it (“As we discussed in our 1:1…”). That builds trust and accountability.
- Track themes over time. Recurring blockers, motivation dips, or growth requests are signals. Address them with process changes, scope changes, or career moves.
- Resist solving everything yourself. Often the best outcome is the report deciding their own next step, with you supporting. Ask “What do you want to do about it?” before jumping to solutions.
What to Avoid
- Filling the time with your own updates. Default to listening; your job is to understand and unblock, not to report.
- Skipping or rescheduling often. It tells people 1:1s don’t matter.
- Using 1:1s as the first time you give critical feedback. Hard feedback deserves a dedicated moment, not “by the way” at the end.
- Letting status take over. Redirect: “Let’s keep status for standup; here I’d rather hear how you’re feeling about the work and what you need.”
Effective engineering 1:1s are about rhythm, a simple agenda, and turning conversations into action. Get the frequency right, share ownership of the agenda with your report, and focus on outcomes—you’ll build trust and catch issues before they become resignations or missed goals.