An engineering manager can hear plenty about project progress in a team meeting and still miss what an individual needs. A one-on-one meeting is a private conversation between a manager and an employee. It creates room for concerns, personal connection, career growth, feedback, and project challenges—not just a status update. section 3.1.1 section 3.3.4
Make the conversation useful to the employee:
- Meet regularly. Ask “What’s top of mind for you?”, then listen and ask questions that help the employee find solutions. If they arrive unsure what to discuss, help them get started. section 3.1.1 section 3.3.4
- Discuss motivations, blockers, and aspirations. Use what you learn to offer support and identify growth opportunities; adapt SMART goals to the individual rather than treating them as a rigid template. section 1.1.1 section 3.1.1
- Exchange specific, constructive feedback in both directions. Recognize achievements, invite concerns about your own decisions, and follow up on progress. section 2.6 section 3.3.1
- Give difficult topics room without turning every meeting into a complaint session. Explore the cause of stress or friction and agree on useful support or next steps. section 3.2.2 section 3.1.4
When feedback changes a decision
A manager introduces core working hours, then hears in routine one-on-ones that the rule clashes with personal obligations and reduces flexibility. Instead of defending the plan, the manager uses that feedback to reconsider it. The meeting gives the employee a voice and gives the manager a chance to improve. section 3.3.1
One-on-ones can also support a new manager’s introduction to a team, private conflict discussions, and career-aligned delegation. They complement rather than replace team meetings or formal performance reviews: regular feedback should make a review less surprising, while the review provides dedicated time to reflect on performance and future goals. For your next meeting, choose one open question and leave time to hear the answer. section 2.6 section 3.1.3 section 4.3.4 section 4.3.3
