Zum Inhalt springen

Effektive One-on-Ones für Engineering Managers

Wie du One-on-Ones führst, die Vertrauen schaffen und Wachstum fördern: Fragerahmen, Karrieregespräche, schwieriges Feedback und Nachverfolgung.

5 Min. Lesezeit
Zwei Personen in einer entspannten Besprechungssituation führen ein fokussiertes Gespräch mit Notizen und einem Laptop

Das Einzelgespräch ist der wichtigste Termin im Kalender eines Engineering Managers. Nicht Standups, nicht Sprint-Planung, nicht Architektur-Reviews. In Einzelgesprächen baut man Vertrauen auf, Probleme kommen früh ans Licht, Karrierewachstum passiert und Menschen entscheiden, ob sie bleiben oder gehen. Ein 30-minütiges wöchentliches Gespräch hat mehr Einfluss auf die Retention als jedes Benefit oder jede Richtlinie.

Die meisten Einzelgespräche werden verschwendet. Sie werden zu Status-Updates, die als Gespräche getarnt sind. "Woran arbeitest du gerade?" "Das Feature ist on track." "Super, bis nächste Woche." Das sagt dir nichts darüber, ob die Person struggelt, gelangweilt ist, wächst oder gehen will.

Ein effektives Einzelgespräch ist ihr Gespräch, nicht deins. Status-Updates gehören in Standups. Einzelgespräche sind für Dinge, die in Gruppensituationen nicht ans Licht kommen.

Das Fragen-Framework

Gute Fragen eröffnen Gespräche. Schlechte schließen sie. "Läuft alles gut?" bekommt ein Ja. "Was ist der schwierigste Teil dessen, woran du gerade arbeitest?" bekommt eine echte Antwort.

tstypescript
interface OneOnOneQuestion {
  category: string;
  questions: string[];
  when: string;
}
 
const questionFramework: OneOnOneQuestion[] = [
  {
    category: "Opening — set the tone",
    questions: [
      "What's on your mind this week?",
      "Is there anything you'd like to talk about that's not on the agenda?",
      "How are you feeling about your work right now?",
    ],
    when: "Start of every 1:1 — let them set the agenda first",
  },
  {
    category: "Work and blockers",
    questions: [
      "What's the hardest thing you're dealing with right now?",
      "Is there anything slowing you down that I can help remove?",
      "What decision are you stuck on?",
      "What would you do differently if you had more time?",
    ],
    when: "When you sense frustration or slow progress",
  },
  {
    category: "Team and relationships",
    questions: [
      "How is the collaboration with [teammate] going?",
      "Is there anyone on the team you'd like to work with more?",
      "Do you feel like your ideas are heard in team discussions?",
      "Is there a team dynamic that's bothering you?",
    ],
    when: "Monthly, or after team changes / conflicts",
  },
  {
    category: "Growth and career",
    questions: [
      "What skills do you want to develop in the next 6 months?",
      "What kind of work energizes you most?",
      "Where do you see yourself in 2 years?",
      "Is there a project or responsibility you wish you had?",
      "What feedback have you gotten recently that stuck with you?",
    ],
    when: "At least monthly for career conversations",
  },
  {
    category: "Feedback and management",
    questions: [
      "What could I do differently to support you better?",
      "Is there something I'm doing that's not helpful?",
      "Do you feel like you have enough context on why decisions are made?",
      "Is there anything about our team's process that frustrates you?",
    ],
    when: "Quarterly — give them space to critique you",
  },
];

Das Meeting strukturieren

Eine lockere Struktur verhindert, dass das Meeting rein reaktiv wird, und lässt gleichzeitig genug Raum für organische Gespräche.

markdownmarkdown
# 1:1 Template (30 minutes)
 
## Their Agenda (10-15 min)
- What they want to discuss (ask at the start)
- Follow up on items from last session
 
## Your Observations (5-10 min)
- Specific feedback on recent work
- Things you noticed (positive or concerning)
- Context on upcoming changes that affect them
 
## Growth Check-in (5-10 min)
- Progress on development goals
- Opportunities coming up (projects, talks, training)
- Career conversation (at least once per month)
 
## Action Items (2 min)
- What each of you will do before next session
- Write these down and review next time
tstypescript
// ❌ One-on-one anti-patterns
const antiPatterns = [
  {
    pattern: "Status update meeting",
    symptom: "You ask 'what are you working on?' and they list tickets",
    fix: "Get status from standups/tools. Use 1:1 for what's not visible",
  },
  {
    pattern: "Monologue",
    symptom: "You talk for 25 of the 30 minutes",
    fix: "Aim for 70% them, 30% you. Ask questions, then listen",
  },
  {
    pattern: "Skipping / rescheduling constantly",
    symptom: "1:1s are the first meeting to get cancelled when busy",
    fix: "Never cancel. If truly impossible, reschedule same week",
  },
  {
    pattern: "No follow-through",
    symptom: "You commit to actions and forget by next session",
    fix: "Write action items, review them first thing next 1:1",
  },
  {
    pattern: "Surface-level only",
    symptom: "'How's it going?' 'Fine.' Every week.",
    fix: "Ask specific, open-ended questions. Tolerate silence",
  },
  {
    pattern: "Surprise feedback in reviews",
    symptom: "Performance review contains feedback they never heard before",
    fix: "Deliver feedback in 1:1s. Reviews should contain zero surprises",
  },
];

Schwieriges Feedback geben

Feedback in Einzelgesprächen sollte spezifisch, zeitnah und auf Verhalten fokussiert sein — nicht auf Persönlichkeit. Das SBI-Framework (Situation, Verhalten, Auswirkung) beseitigt Mehrdeutigkeit.

tstypescript
// ❌ Vague feedback that doesn't change behavior
const vagueExamples = [
  "You need to communicate better",
  "Your code quality needs improvement",
  "You should be more proactive",
  "You seem disengaged lately",
];
 
// ✅ SBI Framework: Situation → Behavior → Impact
interface SBIFeedback {
  situation: string;
  behavior: string;
  impact: string;
}
 
const specificExamples: SBIFeedback[] = [
  {
    situation: "In yesterday's design review meeting",
    behavior:
      "you interrupted Alex twice while they were explaining " +
      "their approach to the caching layer",
    impact:
      "Alex lost their train of thought and didn't finish presenting " +
      "their idea. The team missed potentially valuable input",
  },
  {
    situation: "On the last three PRs you reviewed",
    behavior:
      "your review comments focused only on style preferences " +
      "(naming, formatting) and didn't address the logic or architecture",
    impact:
      "the PR authors feel the reviews aren't helpful, and two bugs " +
      "in error handling paths made it to production",
  },
  {
    situation: "This sprint",
    behavior:
      "you picked up three additional tasks beyond your sprint " +
      "commitment without flagging that your committed work would slip",
    impact:
      "the team didn't know the auth feature was behind schedule " +
      "until the last day, and we couldn't adjust the release plan",
  },
];
tstypescript
// After delivering feedback, shift to collaborative problem-solving
const feedbackConversation = {
  step1_deliver: "Share the SBI feedback clearly and pause",
  step2_listen: "Ask 'What's your perspective on this?' and listen fully",
  step3_explore: "Understand their context — there may be reasons you don't see",
  step4_agree: "Agree on what 'better' looks like specifically",
  step5_support: "Ask 'What support do you need from me to make this change?'",
  step6_followUp: "Check in on progress in the next 1:1",
};

Karrieregespräche

Karrieregespräche sollten monatlich stattfinden, nicht jährlich. Sie helfen dir zu verstehen, was Menschen motiviert, und deren Wachstum mit den Team-Bedürfnissen in Einklang zu bringen.

tstypescript
interface CareerConversation {
  topic: string;
  questions: string[];
  managerAction: string;
}
 
const careerTopics: CareerConversation[] = [
  {
    topic: "Aspirations",
    questions: [
      "What does your ideal role look like in 2-3 years?",
      "Do you see yourself going deeper technically or moving into management?",
      "What kind of problems do you want to be solving?",
    ],
    managerAction:
      "Map their aspirations to concrete opportunities on the team. " +
      "If their goals don't align with what's available, be honest about it",
  },
  {
    topic: "Skill gaps",
    questions: [
      "What's the biggest gap between where you are and where you want to be?",
      "What skill would have the biggest impact on your effectiveness?",
      "Is there something you avoid because you're not confident in it?",
    ],
    managerAction:
      "Create specific development opportunities: pairing, projects, " +
      "training, stretch assignments. Write them down and track progress",
  },
  {
    topic: "Energy and motivation",
    questions: [
      "What type of work gives you energy?",
      "What type of work drains you?",
      "What's the ratio of energizing to draining work right now?",
    ],
    managerAction:
      "Adjust task allocation to increase energizing work. " +
      "If draining work is necessary, acknowledge it and rotate it fairly",
  },
];

Über Sitzungen hinweg nachverfolgen

Ohne Notizen werden Einzelgespräche zu isolierten Gesprächen ohne Kontinuität. Einfaches Tracking macht Nachverfolgung automatisch.

markdownmarkdown
# 1:1 Notes: [Name] — 2022-11-26
 
## Discussion
- Frustrated with the deployment process — takes 45 min to get
  a fix to production. Wants us to invest in faster CI/CD
- Interested in the upcoming observability project
- Wants to improve system design skills
 
## Action Items
- [ ] @me: Talk to infra about CI/CD pipeline optimization
- [ ] @me: Assign them to the observability project starting next sprint
- [ ] @them: Read "Designing Data-Intensive Applications" chapters 1-3
- [ ] @them: Present system design for the cache invalidation RFC
 
## Follow-up from 2022-11-19
- [x] @me: Connected them with Sarah for pairing on Kubernetes ✓
- [x] @them: Completed the load testing spike ✓
- [ ] @me: Still pending — get budget approval for conference (carry forward)
tstypescript
// Simple tracking structure
interface OneOnOneEntry {
  date: string;
  attendee: string;
  topics: string[];
  actionItems: Array<{
    owner: "manager" | "report";
    description: string;
    status: "open" | "done" | "carried";
    dueDate?: string;
  }>;
  careerNotes?: string;
  flaggedConcerns?: string[];
}
 
// Review cadence:
// - Action items: every session (first 2 minutes)
// - Career goals: monthly
// - Performance patterns: quarterly prep for reviews
// - Retention signals: always watching (energy, engagement, complaints)

Wichtigste Erkenntnisse

  1. Einzelgespräche sind ihr Gespräch, nicht deins — Status-Updates gehören in Standups; Einzelgespräche bringen Probleme ans Licht, bauen Vertrauen auf und beschleunigen Wachstum
  2. Stelle spezifische, offene Fragen — "was beschäftigt dich gerade?" öffnet Türen; "läuft alles gut?" schließt sie; ertrage Schweigen, während sie nachdenken
  3. Nutze SBI für schwieriges Feedback — Situation, Verhalten, Auswirkung beseitigt Mehrdeutigkeit und fokussiert auf beobachtbare Handlungen, nicht auf Persönlichkeitsurteile
  4. Karrieregespräche sollten monatlich stattfinden — verstehe ihre Ambitionen, identifiziere Skill-Gaps und schaffe spezifische Entwicklungsmöglichkeiten; warte nicht auf jährliche Reviews
  5. Aktionspunkte nachverfolgen und einhalten — schreibe Zusagen auf, bespreche sie zu Beginn der nächsten Sitzung; nichts zerstört Vertrauen schneller als ein Manager, der seine Versprechen vergisst
Wilfredo Rujel

Wilfredo Rujel

Full-Stack-Softwareentwickler

Diesen Beitrag teilenX