One-on-one meetings are the most important recurring meeting on your calendar. They are where trust is built, problems are surfaced early, feedback is exchanged, and career development happens. Yet many managers conduct one-on-ones poorly - turning them into status updates or skipping them when things get busy. This guide helps you make every one-on-one count.
Understanding the Purpose of One-on-Ones
One-on-ones serve three primary purposes: building and maintaining trust, providing a space for coaching and feedback, and supporting career development. They are the engineer's meeting, not yours - the agenda should be driven primarily by what the engineer needs to discuss.
Hold one-on-ones weekly for most direct reports. Bi-weekly may suffice for very senior, autonomous engineers, but weekly meetings catch problems sooner and build stronger relationships. Skipping one-on-ones sends the message that the engineer is not a priority, even when that is not your intention.
Keep one-on-ones sacred. Cancelling or rescheduling them repeatedly undermines trust and signals that other commitments are more important. If you must reschedule, do so proactively and explain why. Never cancel without rescheduling.
Preparing for and Structuring One-on-Ones
Prepare for each one-on-one by reviewing your notes from the last meeting, checking on any follow-up items you committed to, and reflecting on the engineer's recent work and any feedback you want to share. Five minutes of preparation makes the meeting significantly more productive.
Use a shared document for the agenda and notes. Both you and the engineer should be able to add topics before the meeting. This prevents the meeting from being dominated by whoever speaks first and ensures that important topics are not forgotten.
A useful structure is: check-in (how are things going, generally?), engineer's topics, your topics, and action items. Allocate roughly 30 minutes - enough time for substantive conversation without consuming too large a block of the engineer's day.
Using One-on-Ones to Build Trust
Start with genuine interest in the engineer as a person, not just as a resource. Ask about their wellbeing, their energy level, and what is on their mind. These human questions build the foundation of trust that makes professional conversations productive.
Listen more than you talk. Your primary role in a one-on-one is to understand the engineer's experience, perspective, and needs. When you do speak, ask clarifying questions rather than jumping to solutions. Engineers often need to think through problems out loud before they want advice.
Follow through on every commitment you make in a one-on-one. If you promise to look into something, do it. If you commit to addressing a concern, address it. Broken promises erode trust faster than anything else.
Providing Feedback and Coaching
Deliver both positive and constructive feedback regularly, not just during performance reviews. Specific, timely feedback helps engineers adjust their behaviour and build on their strengths in real time. Waiting months to share feedback makes it less actionable and more anxiety-inducing.
Use one-on-ones for coaching conversations - helping the engineer think through challenges, develop their skills, and grow their impact. Ask questions like 'What would you do differently next time?' or 'What support would help you tackle this?' rather than prescribing solutions.
Address performance concerns early and directly in one-on-ones. Waiting until a formal review to share that someone is not meeting expectations is unfair to the engineer and limits their opportunity to improve.
Supporting Career Development in One-on-Ones
Dedicate a portion of regular one-on-ones - and occasional full sessions - to career development. Understand the engineer's career aspirations, discuss the skills they need to develop, and identify specific opportunities for growth.
Create a written development plan for each direct report that is reviewed and updated regularly. This plan should include short-term goals (this quarter), medium-term goals (this year), and long-term aspirations. Tracking progress on the plan demonstrates your genuine investment in their growth.
Be honest about career progression within your organisation. If the engineer's goals are not achievable in their current role or company, help them understand their options rather than making false promises. Honest career advice builds trust even when the news is not what they want to hear.
Key Takeaways
- Hold one-on-ones weekly, treat them as sacred, and let the engineer drive the agenda
- Prepare with a shared document, review previous notes, and bring specific feedback
- Build trust through genuine interest, active listening, and consistent follow-through
- Deliver feedback regularly and use coaching questions rather than prescriptive solutions
- Dedicate regular time to career development with a written, actively maintained development plan
Frequently Asked Questions
- What if an engineer says they have nothing to discuss?
- This usually signals either a trust deficit or an unclear understanding of what one-on-ones are for. Start by asking open-ended questions: 'What is the most frustrating thing you dealt with this week?' or 'What would make your work easier?' If the engineer consistently has nothing to discuss, share your own observations and concerns to model vulnerability. Over time, as trust builds, most engineers open up. If they truly have nothing to discuss, use the time for career development or proactive coaching.
- How should I handle a one-on-one where the engineer is upset or emotional?
- Create space for their emotions without trying to fix things immediately. Listen empathetically, validate their experience, and resist the urge to problem-solve until they are ready. Sometimes people need to be heard more than they need a solution. If the emotion relates to a serious issue - harassment, discrimination, or severe stress - ensure the engineer knows about available support resources and follow up proactively.
- Should I take notes during one-on-ones?
- Yes, but do so in a way that does not interfere with the conversation. Shared notes in a running document are ideal - they provide accountability, prevent important topics from being forgotten, and give both parties a record of commitments and decisions. Let the engineer know you are taking notes and share them after the meeting. Avoid the appearance of documenting for disciplinary purposes - notes should feel like a collaboration tool, not a surveillance mechanism.
Download One-on-One Templates
Access our one-on-one meeting templates with question banks, career development frameworks, and feedback delivery guides for engineering managers.
Learn More