LThe Lead Playbook
The Playbook · 5 Stages

Engineering Leadership Playbook

A step-by-step journey from leading yourself to leading the business. Each stage builds on the last — with the skills to develop, the mistakes that derail most leaders, and the practical exercises that actually move the needle.

Start with Stage 01Jump to frameworks
  1. 01Lead yourself
  2. 02Lead one person
  3. 03Lead a team
  4. 04Lead through process
  5. 05Lead beyond engineering
  1. Stage 01 · Lead yourself

    Start with Self-Leadership

    Step 1/5

    Before you can lead anyone else, you have to be a reliable, regulated operator. Self-leadership is the foundation everything else stands on — your emotional state, your defaults under pressure, and your relationship with your own time.

    Key skills to build
    • Emotional maturity
    • Accountability
    • Communication clarity
    • Time management
    • Context switching discipline
    Common mistakes to avoid
    • Reacting from emotion in high-stakes conversations
    • Blaming the team, the org, or the roadmap instead of owning outcomes
    • Treating your calendar as something that happens to you
    • Performing busyness instead of producing leverage
    Practical exercises
    • Run a weekly self-review: what did I avoid, what did I overreact to, what did I own?
    • Audit one week of calendar and label every block as create, decide, or react
    • Write the email you wanted to send angry — then delete it and rewrite from a regulated state
  2. Stage 02 · Lead one person

    Learn to Lead Individuals

    Step 2/5

    Leadership becomes real the moment another person's growth depends on you. This stage is about the craft of the one-to-one relationship — the conversations, the coaching, and the trust that make engineers do their best work.

    Key skills to build
    • 1:1s
    • Coaching
    • Career development
    • Feedback
    • Trust building
    Common mistakes to avoid
    • Turning 1:1s into status updates
    • Giving feedback only when something goes wrong
    • Solving problems for engineers instead of coaching them through
    • Promising career growth you can't actually influence
    Practical exercises
    • Rewrite your 1:1 template to start with their agenda, not yours
    • Deliver one piece of specific, behavioral feedback within 48 hours of observing it
    • Co-author a growth plan with each direct report and revisit it monthly
  3. Stage 03 · Lead a team

    Learn to Lead Teams

    Step 3/5

    A team is more than the sum of its 1:1s. At this stage you design the rituals, ownership models, and cross-functional relationships that turn a group of engineers into a unit that ships predictably and learns continuously.

    Key skills to build
    • Team rituals
    • Sprint planning
    • Delivery ownership
    • Quality mindset
    • Collaboration with QA, Product, Support, and Design
    Common mistakes to avoid
    • Keeping rituals alive long after they've stopped producing value
    • Letting planning become a negotiation theatre instead of a commitment
    • Treating quality as QA's job rather than the team's standard
    • Optimizing for engineering's comfort over the customer's experience
    Practical exercises
    • Kill or merge one recurring meeting this month — keep only what produces decisions
    • Run a post-sprint retro focused on one question: what slowed us down most?
    • Shadow a support or QA teammate for a day and bring three insights back to the team
  4. Stage 04 · Lead through process

    Learn to Lead Through Systems

    Step 4/5

    Eventually you outgrow what you can hold in your head. Leading through systems means encoding your judgment into metrics, processes, and feedback loops — so the team's quality, speed, and resilience no longer depend on you being in the room.

    Key skills to build
    • Metrics
    • Prioritization
    • Incident response
    • Engineering excellence
    • Process improvement
    Common mistakes to avoid
    • Measuring activity (PRs, tickets) instead of outcomes
    • Adding process every time something breaks, never removing any
    • Skipping postmortems when the incident felt embarrassing
    • Confusing 'we've always done it this way' with engineering excellence
    Practical exercises
    • Choose three north-star metrics and kill any dashboard that doesn't ladder up
    • Run a blameless postmortem on a near-miss, not just an outage
    • Audit your team's processes and retire one this quarter
  5. Stage 05 · Lead beyond engineering

    Learn to Lead the Business

    Executive

    At the senior level your job stops being engineering management and starts being business leadership through an engineering lens. You make tradeoffs across customer, revenue, and risk — and you translate them in language executives actually act on.

    Key skills to build
    • Customer impact
    • Revenue impact
    • Stakeholder management
    • Strategic tradeoffs
    • Executive communication
    Common mistakes to avoid
    • Pitching technical work without naming the customer or revenue it serves
    • Saying yes to every stakeholder request to avoid friction
    • Treating strategy as a doc instead of a sequence of bets
    • Bringing problems to executives without options and a recommendation
    Practical exercises
    • Rewrite your current roadmap as a one-page memo for the CEO
    • For every major initiative, write the one sentence that connects it to revenue or risk
    • Practice the SBR pattern (Situation, Bets, Recommendation) in your next exec update
After Stage 05

You don't graduate — you re-enter.

Great leaders cycle back through every stage as their scope grows. Use the frameworks library as your operating toolkit, and the articles as your continuing education.

Open frameworksRead articles

Leadership in your inbox.

Weekly systems-thinking and practical frameworks for modern engineering leaders. No motivational fluff.

Joined by 12,000+ leaders at Stripe, Vercel and Linear