Complete engineering management system — team building, 1:1s, performance, hiring, architecture decisions, incident management, and scaling. From IC-to-manager transition through director-level operations.
Your complete playbook for engineering leadership. Not generic management advice — this is the specific system that high-performing engineering managers run daily.
Before managing people, understand the system they work in.
team_topology:
name: "[Team Name]"
type: stream-aligned | platform | enabling | complicated-subsystem
mission: "[One sentence — what does this team exist to do?]"
boundaries:
owns: ["service-x", "domain-y", "pipeline-z"]
consumes: ["auth-service", "data-platform"]
provides: ["checkout-api", "payment-events"]
cognitive_load: low | medium | high | overloaded
interaction_modes:
- team: "[Other Team]"
mode: collaboration | x-as-a-service | facilitating
friction: low | medium | high
notes: "[What's working/not working]"
current_headcount: N
ideal_headcount: N
skill_gaps: ["observability", "mobile", "ML"]
Score 1-5 for each dimension. Track trends over time.
| Dimension | Score | Signal |
|---|---|---|
| Delivery pace | _ /5 | Are we shipping what we committed? |
| Quality | _ /5 | Bug rate, incident frequency, tech debt trajectory |
| Collaboration | _ /5 | Cross-functional work, PR review speed, knowledge sharing |
| Morale | _ /5 | Energy in meetings, voluntary contributions, retention signals |
| Learning | _ /5 | New skills adopted, conference talks, internal tech talks |
| Autonomy | _ /5 | Can the team make decisions without waiting for me? |
| Psychological safety | _ /5 | Do people raise concerns, admit mistakes, challenge ideas? |
| On-call health | _ /5 | Page frequency, off-hours burden, burnout signals |
Action rules:
The ideal team has these roles covered (not necessarily 1:1 with people):
| Role | Description | Gap Impact |
|---|---|---|
| Tech lead | Architecture decisions, code quality bar | Decisions bottleneck through you |
| Senior IC (2-3) | Carry complex work, mentor juniors | Velocity drops, quality suffers |
| Mid-level (2-3) | Reliable delivery, growing scope | No bench for senior pipeline |
| Junior (0-2) | Learning, fresh perspective | No talent pipeline |
| Domain expert | Deep knowledge of the problem space | Constantly solving wrong problems |
Rule of thumb: Never have >60% of team at same level. Mix creates natural mentorship.
| Report Level | Frequency | Duration | Focus |
|---|---|---|---|
| Direct reports | Weekly | 30 min | Career + blockers + feedback |
| Skip-levels | Monthly | 30 min | Team health + career + honesty check |
| Your manager | Weekly | 30 min | Priorities + asks + air cover |
| Cross-functional peers | Bi-weekly | 25 min | Dependencies + alignment |
one_on_one:
date: "YYYY-MM-DD"
person: "[Name]"
role: "[Title]"
tenure: "[X months on team]"
# Their agenda first — ALWAYS
their_topics: []
# Check-in (2 min)
energy_level: 1-10 # "How are you feeling about work this week?"
energy_trend: up | stable | down
# Delivery (5 min)
current_work: "[What they're working on]"
blockers: []
help_needed: "[What can I unblock?]"
# Growth (10 min — skip if urgent topics dominate, but never 3 weeks in a row)
career_conversation: "[Topic discussed]"
feedback_given: "[Specific behavior → impact → request]"
feedback_received: "[What they told me]"
stretch_opportunity: "[Current or upcoming]"
# Action items
my_actions: [] # What I committed to do
their_actions: [] # What they committed to do
# Signals (private — don't share these)
flight_risk: low | medium | high
performance_trajectory: improving | stable | declining
notes: "[Anything notable]"
Opening (rotate these — never use the same opener 3 weeks in a row):
Career development (monthly deep-dive):
Team health (probe with care):
Feedback solicitation (for YOU):
Monitor these signals — if 3+ present, have a retention conversation within a week:
| Signal | Weight | Detection |
|---|---|---|
| LinkedIn profile update | 🔴 High | Someone mentions it, or you notice |
| Declining 1:1 engagement | 🔴 High | Shorter answers, less eye contact, "everything's fine" |
| Stopped volunteering for projects | 🟡 Medium | Used to raise hand, now doesn't |
| Increased PTO without travel | 🟡 Medium | Interviewing signal |
| Disengaged in meetings | 🟡 Medium | Camera off, multitasking, no opinions |
| Complaining shifted from specific to general | 🟡 Medium | "This sprint is rough" → "This place..." |
| Stopped arguing for their ideas | 🔴 High | They've mentally checked out |
| Life event (new baby, move, partner change) | 🟡 Medium | Re-evaluating everything |
Retention conversation framework:
Rate on two axes (both matter):
Delivery Impact (What)
| Level | Description |
|---|---|
| 1 - Below | Missing commitments, quality issues, needs close oversight |
| 2 - Meeting | Delivering assigned work reliably |
| 3 - Exceeding | Delivering beyond scope, finding better solutions |
| 4 - Outstanding | Multiplying team output, solving problems no one asked them to |
Behaviors (How)
| Level | Description |
|---|---|
| 1 - Below | Creating friction, not collaborating, ignoring feedback |
| 2 - Meeting | Professional, collaborative, receptive to feedback |
| 3 - Exceeding | Mentoring others, proactively improving processes |
| 4 - Outstanding | Shaping culture, attracting talent, raising the entire bar |
Calibration matrix:
| Behavior 1 | Behavior 2 | Behavior 3 | Behavior 4 | |
|---|---|---|---|---|
| Delivery 4 | Coach behaviors | Strong | Top performer | Superstar |
| Delivery 3 | Coach behaviors | Solid | Strong | Top performer |
| Delivery 2 | PIP candidate | Meets expectations | Developing | Growing |
| Delivery 1 | Exit | PIP | Coach delivery | Coach delivery |
Template: "In [situation], when you [specific behavior], the impact was [concrete effect]. I'd like to see [specific change] because [intent/why it matters]."
Examples:
✅ Good: "In yesterday's design review, when you challenged the API schema with the versioning concern, it caught a breaking change we would have shipped. That's exactly the kind of technical leadership I want to see more of."
❌ Bad: "You're doing great work. Keep it up." (Too vague — they learn nothing)
✅ Good: "In the last two sprints, PRs have been sitting in review for 3+ days. The impact is features are merging late and we're missing sprint commitments. I'd like us to commit to <24h first review because velocity depends on review speed."
❌ Bad: "You need to review PRs faster." (No situation, no impact, no collaboration)