The Manager's Path
Camille Fournier's map of the actual career ladder from doing the work to leading an organization of leaders, written for engineering managers, but mostly a clear-eyed account of how the job itself changes at every rung, which almost nobody explains to you before you climb it.
Find this on the mind-map
Introduction
Fournier wrote the book she wished someone had handed her at each step of her own path from individual contributor to CTO. Her central observation is that "management" isn't one job that scales up with seniority. It's a series of distinct jobs, each requiring you to let go of something that made you good at the last one. Most of the pain in a management career comes from trying to keep doing the old job while also doing the new one.
Mentoring Before You Manage
Long before an official title, the first management skill most people practice is mentoring a newer colleague, and Fournier treats this as real management training, not a side activity. The skill being built is patience with someone else's pace of learning, and the discipline of explaining your reasoning instead of just supplying the answer, which is the seed of everything coaching and feedback will later require at scale.
The Tech Lead (or Working Lead)
The first formal step up usually isn't "manager." It's leading the work itself: setting technical or project direction for a small group while still doing hands-on work yourself. The failure mode here is specific: tech leads who can't stop being the best individual contributor on the team end up as a bottleneck, because every important decision still routes through their own hands instead of being genuinely delegated.
Becoming a New Manager
The real inflection point, and the one Fournier is most direct about: your job output is no longer your own work, it's your team's work, and the two can feel completely disconnected for months. New managers often keep score using their old metric (what did I build this week) long after that's stopped being the right question, which produces a nagging, misleading sense of having accomplished nothing.
Manager A, fresh into the role, spends her hardest hours each week still writing code, because it's the work she knows how to measure herself by. Manager B spends those same hours in 1:1s and removing blockers, and can't point to a single thing she personally built, but her team ships twice as much as A's.
Managing Multiple Teams
One level up, and the job changes again: you're no longer close enough to the daily work to catch problems by osmosis, which means you need systems (regular check-ins, clear escalation paths, trust in the managers reporting to you) to know what's actually happening across teams you can't personally watch. The temptation here is to over-rely on whichever team happens to be loudest or most visible, at the expense of a quieter team that's actually struggling.
Managing Managers
The job becomes almost entirely indirect: your direct impact on any one team now runs entirely through the manager in between, which means your most valuable skill becomes developing other managers' judgment, not substituting your own for theirs. Fournier is blunt that this is where the job stops resembling anything from earlier in a career and starts requiring patience with influence that's two steps removed from the actual work.
Director and Above: Organizational Design
At the top of the ladder, the job shifts again, toward shaping the organization itself: how teams are structured, how decisions get made across the whole group, hiring at scale, and setting a technical or organizational vision that other leaders will execute without your daily involvement at all. The feedback loop on your own decisions gets slower and noisier here, which makes self-doubt a much more common hazard than at any earlier level.
Putting It Together
Each rung on Fournier's ladder requires giving something up: individual output, hands-on technical control, direct visibility, and eventually direct influence itself. The managers who struggle most at a given level are usually the ones trying to hold onto the skill set that made them succeed one level down, instead of building the different one the new level actually requires.

Why It Matters for Leaders
The question this book answers isn't "am I doing a good job." It's "am I still doing last year's job." Those feel like the same question from the inside, and they aren't. A manager who's slipping usually isn't failing at the current role, they're still excelling at the previous one, and nobody told them the scorecard changed.
That's why the useful move isn't more effort, it's a specific kind of audit. Look at how you actually spent your hours this week, and ask which of them only you could have done, and which of them you did simply because you were faster at it than the person you should have handed it to. The second category is where a manager's growth stalls without much notice, because it feels productive in the moment and shows up as a real cost only months later, in a team that still routes everything through you.
This shows up hardest at the exact moment someone gets promoted, because the thing they're best at is precisely the thing the new role asks them to stop doing. A brand-new engineering manager who was the team's strongest coder keeps grabbing the trickiest pull requests herself, because reviewing them is slower than just fixing them, and she can feel her own competence while she does it. Six months in, her team still brings her every hard problem instead of working through it themselves, her own backlog of "quick fixes" never shrinks, and she's working the longest hours on the team while wondering why the team isn't getting any faster. The fix isn't trying harder at the old job. It's sitting on her hands through the discomfort of watching someone else solve it slower than she would have, until the team can actually solve it without her.
Use this book as a mirror for whichever rung you're on right now, not just the one you're aiming for next. The skill that made you good enough to get promoted is rarely the skill the new seat is asking for, and the manager who notices that gap early loses a lot less time than the one who finds out from a bad engagement survey two years later.
What to do next
Reinforce your understanding of The Manager's Path
Books related to The Manager's Path
Coaching for Performance
Sir John Whitmore's foundational case for coaching-style management over command-and-control, built on a single idea: performance is limited less by skill than by interference, and a manager's job is to remove the interference, not supply the answer.
Elevate
Robert Glazer's case, from his book "Elevate: Push Beyond Your Limits and Unlock Success in Yourself and Others," that performance isn't a willpower problem. It's a capacity problem across four specific domains, built like a muscle, not willed into existence overnight.
First, Break All The Rules
A large-scale look at what the best managers actually do differently, and the uncomfortable finding that most of it runs against conventional management wisdom, starting with the idea that you shouldn't try to fix people's weaknesses.
Multipliers
Liz Wiseman's case that the biggest lever on a team's output isn't headcount or talent density, it's whether the leader in the room makes people smarter or slowly makes them smaller.
Team Topologies
Skelton and Pais's case that most team structures are drawn to fit an org chart, not the actual flow of work, and a small set of team shapes and interaction rules for fixing that, built around a resource every leader habitually overspends: people's cognitive load.
The Coaching Habit
Michael Bungay Stanier's pitch that most managers have an "advice monster" problem, and a short list of deceptively simple questions designed to starve it, a little at a time, in conversations that already happen every day.
The First-Time Manager
The unglamorous, practical handbook for the specific week your job title changed and nothing else came with instructions. Less a framework, more a set of answers to the questions new managers are usually too embarrassed to ask out loud.
The Five Dysfunctions of a Team
Patrick Lencioni's pyramid of the five behaviors that sink teams without much notice, stacked so that each one is actually caused by the dysfunction beneath it, which means fixing results or accountability first almost never works.
The Making of a Manager
Julie Zhuo's field notes from becoming a manager in her twenties with no idea what the job actually was. A clear-eyed answer to the question most new managers are too embarrassed to ask out loud: what am I actually supposed to be doing all day?
Turn the Ship Around!
A submarine captain's account of giving up the one thing every leader is taught to protect, being the person who gives the orders, and turning the worst-performing submarine in the fleet into one of the best by making every sailor think like a captain instead.
Skills related to The Manager's Path
Frameworks related to The Manager's Path
Dunning-Kruger Effect
Knowing little makes you feel unstoppable; knowing more makes you hesitate — the loudest voice is rarely the most reliable one.
Goldilocks Principle
Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.
Hawthorne Effect
People change how they behave when they know they're watched — your attention is an intervention that changes what you see.
Maslow's Hierarchy of Needs
Abraham Maslow's five-level model of motivation, applied to leadership as a stack — mastery, trust, belonging, up through recognition and vision.
McKinsey 9-Box Model
A 3x3 grid that plots each person on performance against potential, giving nine distinct calls instead of one blurry verdict.
Multipliers and Diminishers
Liz Wiseman's split between leaders who bring out best thinking in people around them, and those who shut it down.
Situational Leadership
There's no right way to lead — only the right way for this person right now: direct, coach, support, or delegate.
The 6 Human Needs
Every behavior at work is really an unmet need in disguise — six needs, popularized by Tony Robbins, worth checking first.
The Architecture of High-Performing Teams
Six elements, built like a temple — culture as the base, four pillars, vision as the roof — name the missing piece.
The Bannister Effect
One person breaking a barrier makes it stop being fixed for everyone else — break the unspoken belief in public first.
The Five Dysfunctions of a Team
Lencioni's pyramid of five team-killing behaviors — a lack of trust at the base drags everything above it down.
The Inner Drive
A leadership take on Daniel Pink's *Drive* that turns three conditions for motivation — autonomy, mastery, purpose — into habits for 1:1s.
The Pygmalion Effect
What you expect from someone leaks into how you treat them, which shapes what they become — for better or worse.
The Thomas-Kilmann (TKI) Model
Five conflict styles, two dials — how hard you push, how much room you give — chosen on purpose, not by default.
Tuckman's Stages of Team Development
Every team moves through five predictable stages — forming, storming, norming, performing, adjourning — each demanding a different move from you.