Effective One-on-Ones for Engineering Managers

The one-on-one meeting is the most important management tool an engineering manager has. It is the primary mechanism for building trust with direct reports, understanding their motivations and concerns, coaching their professional development, and detecting problems before they escalate. Yet most managers treat one-on-ones as status updates — asking "What are you working on?" and "Do you have any blockers?" for 30 minutes. This wastes the meeting's potential and signals to the engineer that the manager cares about output, not about them.

Effective one-on-ones are owned by the engineer, not the manager. The engineer sets the agenda, raises topics they want to discuss, and drives the conversation. The manager listens, asks questions, provides coaching, and removes obstacles. This inversion of control communicates respect and builds psychological safety — engineers who feel heard in one-on-ones are more likely to raise problems in team settings and push back on unrealistic commitments.

A productive one-on-one follows a flexible structure: Check-in (5 minutes — "How are you doing? How was your weekend?" — builds rapport and catches personal circumstances affecting work), Engineer's Topics (15 minutes — the engineer raises concerns, ideas, requests, or feedback — this is the core of the meeting), Manager's Topics (5 minutes — the manager shares context, organizational updates, or feedback — keep this brief), Action Items (5 minutes — agree on specific next steps with owners and deadlines).

TaptiPM's one-on-one module provides a shared agenda document that both parties can add topics to before the meeting. The document persists between sessions, showing previous action items and their completion status. Starting each meeting with a 2-minute review of previous action items closes the loop and demonstrates that commitments made in one-on-ones are taken seriously. When engineers see their manager following through on promised actions, trust compounds rapidly.

The one-on-one is the appropriate venue for difficult conversations: performance concerns, behavioral feedback, career disappointments, and interpersonal conflicts. These conversations are uncomfortable but essential — avoiding them signals that the manager either does not notice the problem or does not care enough to address it. Both interpretations erode trust.

The SBI framework (Situation, Behavior, Impact) structures difficult feedback objectively: "In yesterday's code review [Situation], I noticed you dismissed two comments without explanation [Behavior]. This made the reviewer feel their input was not valued and may discourage them from providing thorough reviews in the future [Impact]." This format focuses on observable behavior and its consequences rather than character judgments, making the feedback specific, actionable, and defensible. TaptiPM's feedback module supports SBI-structured feedback notes that can be referenced in performance reviews for consistency.

At least one one-on-one per month should focus on career development. The career conversation covers three time horizons: near-term (next 3 months — what skills are you developing? what stretch assignments interest you?), medium-term (next 1-2 years — what role are you growing toward? what gaps need to be addressed?), and long-term (3-5 years — what is your career aspiration? how can this organization help you get there?). These conversations demonstrate investment in the engineer's growth beyond their current output.

TaptiPM's career development module tracks career goals, development plans, and progress over time. Each engineer has a development plan with specific goals, target competencies, learning resources, and milestone dates. The one-on-one module links directly to the development plan, making it easy to review progress during career conversations. Engineers who see their manager actively tracking and supporting their career growth are 3x more likely to stay with the organization through challenging periods.