Leadership isn't one thing — it's six things, each with its own depth. The strongest leaders aren't world-class at any single pillar; they're competent across all of them and excellent at the few that match the moment.
Take the 5-minute self-assessmentBuild trust, coach growth, and create the conditions where engineers do their best work.
Move beyond status-update 1:1s to intentional career design, talent density mapping, and high-trust environments. Learn to run 1:1s as coaching sessions, give feedback that lands, and identify the small interventions that compound over a six-month horizon. Grow engineers into the next version of themselves — not into clones of you.
Turn ambiguity into clear plans, reliable rhythms, and shipped outcomes.
Predictable delivery is a system, not a personality trait. Build the planning and review loops that ship. Scope, sequence, and signal. Replace heroics with mechanisms — weekly planning rituals, scope-cut protocols, and review cadences that catch drift before the deadline catches you. Most leadership work is choosing what not to do.
Make sound technical decisions without needing to be the deepest expert in every room.
Great leaders don't need to be the deepest expert in every area. They need to ask the right questions, evaluate trade-offs, and make sound architectural decisions with imperfect information. Build the judgment to know when to dive deep, when to delegate, and when to trust the team.
Connect engineering work to customer value, revenue impact, risk reduction, and company strategy.
Translate technical roadmaps into business outcomes — and translate business pressure into healthy team scope. Manage upward, sideways, and around. Learn the cadence of executive updates, the structure of a memo that gets a decision, and how to push back without becoming the blocker. Stop solving today's problems on repeat; start designing the conditions that prevent them.
Build systems for quality, reliability, incident response, metrics, planning, and continuous improvement.
Process is a force multiplier when it serves the team. Audit your sprint, your retro, your on-call rotation. Kill rituals that have outlived their purpose. Build lightweight scaffolding that lets engineers focus on the work. Incidents are a teacher — build a culture where they make the system stronger, not the engineer smaller. Pick the few numbers that change behaviour.
Create a team environment where ownership, accountability, learning, and collaboration become the default behavior.
Culture is what your team does when no one is watching. Design it on purpose or inherit one by accident. Define the unwritten rules that govern code review, on-call respect, and engineering quality. Codify the behaviours you want to multiply and quietly delete the ones you don't.
Leadership lessons, frameworks, and field notes for modern engineering teams. No motivational fluff.
Trouble seeing the form?Subscribe on Beehiiv instead
Free. One email a week. Unsubscribe anytime.