People Leadership
Coaching engineers, building trust, giving feedback, creating psychological safety, and helping people grow.
Practical frameworks, leadership lessons, and operating principles for engineers, managers, and directors who want to lead high-performing teams with clarity, empathy, and execution discipline.
It isn't the loudest voice in the room or the best debugger on the team. It's the person who builds the system that predictably produces high-quality outcomes through others.
Great leaders treat their team as the primary product. They optimize for clarity, trust, and execution velocity. They invest in the few decisions that compound — and learn to ignore the many that don't.
This site is the operating manual: ten pillars, forty frameworks, and a growing library of essays from people who have actually run the playbook in production.
Ten foundations every engineering leader has to develop. Start anywhere — they reinforce each other.
Move beyond status-update 1:1s to intentional career design, talent density mapping, and high-trust environments.
Predictable delivery is a system, not a personality trait. Build the planning and review loops that ship.
Culture is what your team does when no one is watching. Design it on purpose or inherit one by accident.
Translate technical roadmaps into business outcomes — and translate business pressure into healthy team scope.
Remove friction without adding bureaucracy. Process is a force multiplier when it serves the team.
Six disciplines that separate the leaders teams quietly respect from the ones they quietly outlast. Master each one — they compound.
Coaching engineers, building trust, giving feedback, creating psychological safety, and helping people grow.
Turning ambiguity into clear plans, managing priorities, driving delivery, and creating reliable team operating rhythms.
Making sound architectural and engineering decisions without needing to be the deepest expert in every area.
Connecting engineering work to customer value, revenue impact, risk reduction, and company strategy.
Building systems for quality, reliability, incident response, metrics, planning, and continuous improvement.
Creating a team environment where ownership, accountability, learning, and collaboration become the default behavior.
The transition from individual mastery to organizational impact happens in four distinct shifts.
Mastery of craft. Success is measured by technical depth and the ability to solve ambiguous problems autonomously.
Multiplier mode. Success becomes the technical alignment, code quality, and growth of the people around you.
Systems architect of teams. Success is a sustainable, high-output engine built through coaching, hiring, and process.
Organizational strategist. Success is aligning technical investment with company goals and leading through other leaders.
Battle-tested templates you can run on Monday morning.
A repeatable structure that splits the meeting into status, growth, friction, and signal — so coaching always gets time.
Three pre-agreed levers (scope, quality, date) and the conversation that decides which one moves before crunch begins.
A four-tier incident model with response expectations, escalation paths, and what's allowed to interrupt focus time.
Sort reversible from irreversible calls. Spend the deliberation budget on the ones that compound.
Deep dives into the mechanics of leading well.
Most 1:1s are wasted on information that belongs in Slack. A field-tested structure for turning thirty minutes a week into the highest-leverage coaching surface you have.
What to listen for in week one, what to commit to in week six, and the trap of trying to prove yourself with output instead of judgement.
A working framework for tech debt vs. velocity, build vs. buy, and the irreversible architectural calls that compound for years.
Weekly systems-thinking and practical frameworks for modern engineering leaders. No motivational fluff.
Joined by 12,000+ leaders at Stripe, Vercel and Linear