One-on-one meetings are the foundation of your relationship with each engineer on your team. They are where trust is built, problems are surfaced, feedback is delivered, and careers are developed. This guide covers how to run one-on-ones that your engineers genuinely value.
Why One-on-Ones Are Non-Negotiable
One-on-ones are not status updates. They are the primary channel through which you understand what your engineers are thinking, feeling, and struggling with. Without regular one-on-ones, problems fester, feedback is delayed, and trust erodes. Engineers who do not have consistent one-on-ones with their manager consistently report lower engagement and satisfaction.
These meetings are for your engineer, not for you. While you may need to share information or give feedback during one-on-ones, the primary purpose is to create space for your engineer to raise concerns, discuss their growth, and get your support on whatever matters most to them.
- One-on-ones are the foundation of the manager-engineer relationship
- They surface problems early, before they become crises
- Cancelling one-on-ones signals that your engineer is not a priority
- The meeting belongs to the engineer; let them drive the agenda
Cadence and Logistics
Weekly one-on-ones of thirty minutes are the standard cadence for most engineering teams. For experienced engineers who need less support, fortnightly may work. For new hires, engineers going through a difficult period, or those on performance improvement plans, increase to twice weekly. Never go longer than two weeks between one-on-ones.
Protect this time fiercely. One-on-ones should be the last meeting you cancel. When conflicts arise, reschedule rather than skip. The pattern of how you treat one-on-ones communicates volumes about your priorities. An engineer whose one-on-one is regularly cancelled learns that they are not important to you.
Hold one-on-ones in a private space - physical or virtual. These conversations often touch on sensitive topics such as interpersonal conflict, career frustrations, or personal challenges. Privacy is essential for candour.
Structuring Effective One-on-Ones
Use a shared document where both you and your engineer can add agenda items before the meeting. This ensures the time is used efficiently and gives the engineer ownership of the conversation. A simple structure works well: the engineer's topics first, your topics second, and action items at the end.
Vary the topics across meetings. Not every one-on-one should be about current work. Rotate through career development, team dynamics, feedback, skill growth, and personal check-ins. Keep a rough rotation to ensure you cover all dimensions over the course of a month.
Take notes and track action items. If you commit to doing something - following up on a concern, providing a stretch opportunity, escalating an issue - write it down and follow through. Your credibility is built on the small commitments you keep between meetings.
Handling Difficult Conversations in One-on-Ones
Some of your most important managerial work happens during difficult one-on-one conversations - delivering critical feedback, discussing underperformance, navigating interpersonal conflict, or supporting an engineer through a personal crisis. Do not avoid these conversations. Avoidance always makes the situation worse.
Prepare for difficult conversations by clarifying your key message, gathering specific examples, and considering the engineer's likely perspective. Be direct but compassionate. State the issue clearly, share the impact, and ask for the engineer's perspective. Listen genuinely to their response. The goal is a shared understanding of the problem and a path forward, not a lecture.
- Never avoid difficult conversations - avoidance compounds the problem
- Prepare your key message and specific examples in advance
- Be direct about the issue while remaining compassionate
- Listen to the engineer's perspective and work towards a shared path forward
Common One-on-One Mistakes
The most common mistake is turning one-on-ones into status updates. If your engineer is spending the entire meeting listing what they worked on this week, something is wrong. Status can be communicated asynchronously. One-on-ones should focus on topics that require dialogue: concerns, ideas, feedback, growth, and relationships.
Another frequent error is doing all the talking. If you are speaking for more than half the meeting, you are not listening enough. Ask open-ended questions and sit with the silence that follows. Engineers often need a moment to formulate their thoughts, and filling that silence with your own words robs them of the opportunity.
Key Takeaways
- Hold weekly one-on-ones and protect them fiercely - never cancel without rescheduling
- Let the engineer drive the agenda and own the meeting
- Use a shared document for agenda items and action tracking
- Rotate topics across career development, feedback, team dynamics, and personal check-ins
- Embrace difficult conversations - avoidance always makes things worse
Frequently Asked Questions
- What do I do when an engineer says everything is fine?
- Dig deeper with specific questions. Instead of 'How is everything going?', ask 'What is the most frustrating thing about your current project?' or 'If you could change one thing about how the team works, what would it be?' If an engineer consistently reports that everything is fine, it usually means they do not feel safe being candid. Focus on building trust over time through consistency, follow-through, and vulnerability.
- How do I handle one-on-ones with remote engineers?
- Remote one-on-ones require more intentionality. Use video when possible to pick up on non-verbal cues. Start with a genuine personal check-in - remote engineers often feel isolated and this connection matters. Be more explicit about asking how they are feeling about communication, inclusion, and access to information. Consider occasionally extending the meeting to allow for the informal conversation that would happen naturally in an office.
- Should I take notes during one-on-ones?
- Yes, but be transparent about it. Let your engineer know you are taking notes to track action items and remember important context. Share the notes with them after the meeting. Some managers use a shared document that both parties can see in real-time. Avoid taking notes in a way that feels like you are building a case - this destroys trust immediately.
Download One-on-One Templates
Access one-on-one agenda templates, question banks, and action tracking tools designed to make your engineering one-on-ones more effective and consistent.
Learn More