The Leadership Library Mutaaf Aziz

The Leadership Library: Books that shape how I think. Lessons that shape how I lead.

A collection of books on engineering, leadership, teams, strategy and personal growth, with summaries, key ideas, my reflections, and how I’m applying them in real life.

Explore the Library Work with me
  1. AccelerateForsgren & Humble & Kim by Nicole Forsgren, Jez Humble and Gene Kim
  2. Clean CodeRobert C. Martin by Robert C. Martin
  3. The 48 Laws of PowerRobert Greene by Robert Greene
  4. Radical CandorKim Scott by Kim Scott
  5. DriveDaniel H. Pink by Daniel H. Pink
  6. The Five Dysfunctions of a TeamPatrick Lencioni by Patrick Lencioni
  7. Extreme Programming ExplainedBeck & Andres by Kent Beck and Cynthia Andres
  8. PeoplewareDeMarco & Lister by Tom DeMarco and Timothy Lister
  9. The Manager’s PathCamille Fournier by Camille Fournier
  10. An Elegant PuzzleWill Larson by Will Larson
  11. Become an Effective Software Engineering ManagerJames Stanier by James Stanier

The more you learn, the more you see how much there is to learn.

— Imam Ali (AS)

Recently Added

See all
  1. Become an Effective Software Engineering ManagerStanier
  2. An Elegant PuzzleLarson
  3. The Manager’s PathFournier
  4. PeoplewareDeMarco & Lister
  5. Extreme Programming ExplainedBeck & Andres
  6. The Five Dysfunctions of a TeamLencioni
  7. DrivePink
  8. Radical CandorScott
  9. The 48 Laws of PowerGreene
  10. Clean CodeMartin
  11. AccelerateForsgren & Humble & Kim

A portrait in spines

You can tell who someone is by the books on their shelf.

So I put mine together into the shape of the person they made. Every stripe is a book, as thick as the book. Tap one to see what it gives away about me.

BECOME AN EFFECTIVE SOFTWARE ENGINEERING MANAGERAN ELEGANT PUZZLETHE MANAGER’S PATHPEOPLEWAREEXTREME PROGRAMMING EXPLAINEDTHE FIVE DYSFUNCTIONS OF A TEAMDRIVERADICAL CANDORTHE 48 LAWS OF POWERCLEAN CODEACCELERATE
Tap a spineEach book gives something away.

Eleven books, one person. Still being written.

My leadership philosophy

Build the system. Earn the trust. Let autonomy do the rest.

Give engineers, and people, the space and autonomy to succeed, with the right tools and systems in place, and you can reach a great result every time. The craft is the balance between alignment and autonomy. But the true value of a team is whether its people trust each other: a psychologically safe place where making mistakes, asking questions and moving forward are all part of the work.

Anyone can be successful here. Partnership and collaboration are how we get there.

  1. The foundation

    Trust & psychological safety

    Mistakes, questions and moving forward are all part of it. Everything else runs on this.

    Shaped byThe Five Dysfunctions of a TeamPeoplewareRadical Candor

  2. 01

    Alignment

    Take the complexity of everything we know and put it into a systemic process: clear goals, clear constraints, shared context.

    Shaped byAn Elegant PuzzleThe Manager’s PathAccelerate

  3. 02

    Systems & tools

    The right tools and systems make the right thing the easy thing, so success never depends on heroics.

    Shaped byAccelerateExtreme Programming ExplainedClean Code

  4. 03

    Autonomy

    Autonomy flows from that alignment: room to decide, own and solve, inside guardrails everyone understands.

    Shaped byDriveBecome an Effective Software Engineering Manager

  5. 04

    Learn & grow

    A cycle of learning and growing: we ship, we look honestly at what happened, we get better, and we go again.

    Shaped byExtreme Programming ExplainedAcceleratePeopleware

How I read

Every block on a book’s page says whose claim it is.

  1. Book's argument

    A summary of what the book argues, and its own model. Never a long quotation.See an example →

  2. My interpretation

    What I take from it, for engineering teams and for the AI agents I run.See an example →

  3. My application

    What I do with it, and the questions I ask my own teams.See an example →

  4. My critique

    Where it’s dated, overreaches, or is only true in some rooms.See an example →

All Books

Explore the full collection, organized by themes and categories.

  1. Become an Effective Software Engineering ManagerJames StanierManagement is a separate craft from engineering, built from deliberate everyday habits.In progress
  2. An Elegant PuzzleWill LarsonTreat engineering management as a system of constraints you can diagnose and redesign.Revisiting
  3. The Manager’s PathCamille FournierEach step up the technical leadership ladder is a different job that asks for new skills.Completed
  4. PeoplewareTom DeMarco and Timothy ListerMost project problems are about people, not technology.Completed
  5. Extreme Programming ExplainedKent Beck and Cynthia AndresShort feedback loops and technical discipline make change cheap and safe.Completed
  6. The Five Dysfunctions of a TeamPatrick LencioniTrust makes conflict safe, which makes commitment, accountability and shared results possible.Completed
  7. DriveDaniel H. PinkFor creative work, autonomy, mastery and purpose motivate better than carrots and sticks.Completed
  8. Radical CandorKim ScottGood bosses care personally and challenge directly, at the same time.Completed
  9. The 48 Laws of PowerRobert GreeneA historical map of how power is gained, kept and lost, read critically rather than as a manual.Completed
  10. Clean CodeRobert C. MartinCode is read far more than it is written, so write it for the next reader: small, named, tested, honest.Completed
  11. AccelerateNicole Forsgren, Jez Humble and Gene KimSpeed and stability aren’t a trade-off: four metrics and a set of capabilities predict high-performing delivery.Completed

My Reading Journey

A timeline of books, insights, and how my thinking has evolved.

  1. Clean CodeAug 2022
  2. The Manager’s PathMar 2023
  3. PeoplewareJun 2023
  4. Radical CandorSep 2023
  5. The Five Dysfunctions of a TeamFeb 2024
  6. Extreme Programming ExplainedJun 2024
  7. DriveOct 2024
  8. AccelerateMay 2025
  9. The 48 Laws of PowerDec 2025
  10. Become an Effective Software Engineering ManagerIn progress
  11. An Elegant PuzzleRevisiting

Key Themes Across Books

How ideas from different books connect, complement, or challenge each other.

High-performing teams

Latest Insights

View all
  1. Accountability has to be built inWhen we counted, only about a quarter of my agent fleet’s pull requests had been reviewed before they merged. Nobody was hiding anything; the system simply let work land without the check. Lencioni puts accountability near the top of the pyramid, and agents taught me that it has to be designed into the pipeline, not requested.From: The Five Dysfunctions of a Team
  2. Autonomy on a leashThe same rule I use for engineers works for AI agents: real freedom inside clear boundaries. My reviewer agent can block a change but never approve it, and self-healing stops after two tries and asks a human. Autonomy without a leash isn’t trust, it’s abdication.From: Drive
  3. Counting found the gapWhen I started recounting my agent fleet's numbers every night, the uncomfortable one was that only about a quarter of agent pull requests were reviewed before they merged. The fix wasn't a reminder; it was a capability: review became a required check. Accelerate's lesson, applied to AI.From: Accelerate
  4. Design the week, or it designs youA manager’s calendar fills itself with other people’s priorities. Protecting time for hiring, unblocking and writing down decisions is the most leveraged thing I do each week.From: Become an Effective Software Engineering Manager
All 14 insights
  1. Diagnose the state before the fixA team that is falling behind needs capacity; a team treading water needs less work in progress. Applying the right fix to the wrong state is how good managers make things worse. I name the state out loud before I change anything.From: An Elegant Puzzle
  2. Each rung is a different jobEvery promotion I’ve had looked like more of the same job and turned out to be a new one. The skill that got me promoted was usually the one I had to put down first.From: The Manager’s Path
  3. Protect the room, not just the roadmapMost schedule slips I’ve seen started as interruptions nobody counted. I now treat engineers’ focus time like a production dependency: if it goes down, delivery goes down with it.From: Peopleware
  4. CI lands the work, not the agentEvery change in my fleet merges only when the checks are green, and every merge deploys. It’s Kent Beck’s feedback loop with a new kind of teammate. Tests are the clearest contract you can give a model.From: Extreme Programming Explained
  5. Trust is the foundationWithout trust, teams spend their energy managing perceptions instead of solving problems. I have watched good engineers go quiet in reviews because admitting a gap felt riskier than shipping one. The fix starts with the leader saying “I don’t know” first, and meaning it.From: The Five Dysfunctions of a Team
  6. Autonomy drives better workPeople do their best work when they have control over how they work, room to get better, and a reason that matters. My job is to make the what and the why unmistakable and then stay out of the how.From: Drive
  7. Feedback is a giftCaring personally while challenging directly builds stronger teams and better outcomes. Coaching kids made it obvious: they can tell in seconds whether you believe in them, and only then will they hear the correction.From: Radical Candor
  8. Know the games, don’t play themPolitics exists in every large organization, and leaders who refuse to see it get blindsided. My answer isn’t to play the games better; it’s to make my work public, measurable and easy to check.From: The 48 Laws of Power
  9. Readable code is a kindness to the next readerThe next person to change this code might be a teammate, a new hire, or an agent working from a fresh checkout. Names that reveal intent, small functions and tests you can read are what let any of them change it safely. That's why I hold agent-written code to the same bar as human code.From: Clean Code
  10. Measure the system, not the peopleFour honest numbers (how often we deploy, how long a change takes, how often it breaks, how fast we recover) tell me more about a team than any status meeting. The moment they become targets for individuals, they stop meaning anything, so I use them only to talk about the system.From: Accelerate

Work with me

Mutaaf Aziz

Engineering Director · 3× CTO · Disney+ · Amazon · AWS Certified

Engineering leader with 15+ years of progressive experience scaling software organizations at Fortune 500 companies and early-stage startups. Presently Senior Manager, Software Engineering at Disney directing consumer experience engineering for Disney+ and ESPN+ across web, mobile, and TV platforms.

Seeking Director / VP / CTO roles at organizations where engineering drives competitive advantage. Dallas, TX · Open to Remote / DFW Hybrid

  1. 2022 – Present

    Walt Disney Company

    Senior Manager, Software Engineering

    The end-to-end Disney+ and ESPN+ streaming experience across web, mobile, and TV devices.

  2. 2021 – 2022

    Amazon

    Senior Manager, Software Engineering

    Last Mile: IoT, real-time data streams, and AI/ML to deliver global fleet management solutions.

  3. 2018 – 2021

    Avigilon (Motorola Solutions)

    Senior Manager, Software Engineering

    Computer Vision and IoT security platforms; Digital Transformation using CI/CD, Containerization, and DevSecOps.

  4. 2014 – 2022

    Overwatch Digital Health · ProVilla · Skrible

    CTO & Co-Founder

    3× startup CTO with direct board-level reporting.

Email me LinkedIn +1 972.352.3293 Download résumé PDF

mutaaf.aziz@gmail.commutaafaziz.com

Reading is the slow part.

The shelf grows as I read. Nothing here pretends to be finished.

About meBack to the books
Become an Effective Software Engineering ManagerIn progress · Stanier

The Leadership Library

The Leadership Library is Mutaaf Aziz's collection of books on engineering leadership, at mutaafaziz.com/library. It covers 11 books, including The Manager's Path, An Elegant Puzzle, Peopleware, Extreme Programming Explained, The Five Dysfunctions of a Team, Drive, Radical Candor, Clean Code and Accelerate. Each book has a labelled summary of its argument, and the owner's own interpretation, applications, critique and dated reflections are added as he writes them; every block says whose claim it is. It is static HTML that works without JavaScript, and on the iPhone Duo and other foldables it becomes a two-page book. The code is MIT-licensed.

Features

Questions

What is the Leadership Library?
It is Mutaaf Aziz's collection of the books on engineering leadership he keeps coming back to, each with a labelled summary of its argument and his own notes added as he writes them.
Which books are in it?
Eleven, including The Manager's Path, An Elegant Puzzle, Become an Effective Software Engineering Manager, Peopleware, Extreme Programming Explained, The Five Dysfunctions of a Team, Drive, Radical Candor, The 48 Laws of Power, Clean Code and Accelerate.
Are the summaries written by AI?
A summary of a book's argument that an assistant drafted is marked as such on the page. Personal content, such as ratings and reflections, is written only by the owner.
Is it free to read?
Yes. Every page is free to read in a browser, and works without JavaScript. Ad banners may appear on the home and book pages, served by the site's own ad server.
Does it work on foldable phones?
Yes. On the iPhone Duo it reads as a book, one page closed and a two-page spread open, and half-folded foldables get a tabletop layout.

Made by Mutaaf Aziz. Source: github.com/mutaaf/library.

Also from the same collection: Mutaaf Aziz, Chalk Talk.