Book

The Making of a Manager

Julie Zhuo

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?

The Making of a Manager Find this on the mind-map

Introduction

Zhuo became a manager young, at a fast-growing company, with no formal training and a vague sense that the job meant "being in charge." Her honest answer, arrived at slowly, is that a manager's job is to get better outcomes from a group of people working together than they'd get working separately. Almost everything else in the role is in service of that one sentence. The book is less a framework and more a field guide through the specific, often embarrassing confusions of actually doing the job for the first time.

A Team Needs Purpose, People, and Process

Zhuo's organizing idea: a team's output depends on three things. Purpose: does everyone understand why this work matters and what "great" looks like? People: are the right people in the right roles, growing, and supported? Process: does the way the team actually works (meetings, decisions, handoffs) help, or does it get in the way without anyone noticing? Most team problems that look like a "people problem" or a "motivation problem" turn out to trace back to a gap in one of these three, and fixing the wrong one wastes a lot of effort.

The Shift from Doing to Enabling

The hardest adjustment for a new manager, especially one promoted for being great at the work itself, is that your own output stops being the measure of your value. Your job becomes making other people better at the work, which can feel slower and less satisfying than just doing it yourself.

Manager A, a strong former engineer, keeps rewriting her reports' code herself before it ships, without telling anyone, because it's faster and she's better at it. Manager B resists that urge, coaches the same gaps instead, and six months later has a team that doesn't need her to rewrite anything. A is still doing two jobs; B has actually scaled.

Running a Real One-on-One

Zhuo treats the weekly 1:1 as the single most valuable tool a manager has, and the most commonly wasted. A good one isn't a status update. Status can be read off a doc. It's where you learn what's actually going on with someone: what's blocking them, what they're worried about, how they're feeling about their own growth. Skipping real 1:1s in favor of "we're all so busy" is a classic way a manager loses the ability to notice a problem before it's already serious.

Giving Feedback People Can Actually Use

Vague feedback ("great job," "needs more polish") feels kind in the moment and helps nobody improve. Zhuo pushes toward feedback that's specific, tied to a concrete example, and delivered close to when it happened. She also pushes toward treating hard feedback as a sign of investment in someone, not an attack on them, which changes both how you give it and how it's likely to land.

Hiring Is a Skill, Not a Gut Feeling

New managers often treat hiring as an intuition test ("do I like this person") rather than a structured evaluation of specific signals against what the role actually needs. Zhuo's push is toward defining what you're actually looking for before the interview, not during it, since a strong gut reaction to a charismatic candidate is one of the easiest ways to hire the wrong person for the job that's actually open.

Developing Your Own Management Philosophy

There's no single "correct" management style. Zhuo is explicit that she spent years borrowing other managers' approaches before realizing the ones that didn't fit her own values never worked as well as the ones she actually believed in. The long-run project of being a manager is figuring out, through a lot of trial and error, what you actually believe about people and work, and building a consistent style around that instead of imitating whoever seems most successful.

Putting It Together

Purpose, people, and process are the levers; the shift from doing to enabling is the mindset change that makes pulling them possible; and 1:1s, feedback, and hiring are the three highest-frequency moments where that mindset either shows up or doesn't. None of it is complicated in the way a strategy framework is complicated. It's just a lot of unglamorous, repeated attention, which is exactly why so many new managers underrate how much work the job actually is.

The Making of a Manager mind-map: Purpose, People, Process, From Doing to Enabling, Real One-on-Ones, Feedback People Can Use, Hiring as a Skill, and Your Own Management Philosophy, branching from the book's cover

Why It Matters for Leaders

Most new managers fail slowly and without much notice, not dramatically. Nobody tells them they're doing the job wrong, because the job still looks like it's getting done. The product ships, the standups happen, the reports get filed. What's missing shows up later, as a team that can't operate without the manager in the room, or a strong performer who leaves without warning because nobody ever asked how they were actually doing.

The useful move this book hands you is a diagnostic one: when something on your team is going wrong, stop before you act and ask whether it's a purpose problem, a people problem, or a process problem. A manager who treats every dip in output as a motivation issue and responds with a pep talk will miss it every time the real cause is that nobody's clear on what "great" looks like for this project, or that the handoff between two roles has broken down without anyone flagging it. The three-way split isn't decoration. It tells you where to actually look before you spend political capital fixing the wrong thing.

The harder shift is personal, not structural. A manager promoted for being the best individual contributor on the team has to give up being the best individual contributor on the team, and that trade rarely feels good in year one. The job stops rewarding you for your own output and starts rewarding you for everyone else's, which means the honest measure of your week is no longer "what did I ship" but "what did my team get better at because I was in the room."

Picture a manager named Priya who was promoted off the strength of her own code. Six months in, she's still the fastest fix for any hard bug on the team, and she knows it, so she keeps taking the hard bugs herself instead of routing them to the engineer who needs the practice. Her team ships fine this quarter. Next quarter, when she's out for two weeks, nothing moves on the one system only she understands. The fix isn't working harder. It's handing the next hard bug to someone else and coaching them through it, even though it's slower, because that's the only way the team gets better at the thing she's currently the bottleneck on.

Your chat with Kyoshi about the book The Making of a Manager

What to do next

Reinforce your understanding of The Making of a Manager

Books related to The Making of a Manager

Coaching for Performance

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

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

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

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

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

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 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

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 Manager's Path

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.

Turn the Ship Around!

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 Making of a Manager

Frameworks related to The Making of a Manager

Dunning-Kruger Effect

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

Goldilocks Principle

Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.

Hawthorne Effect

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

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

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

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

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

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

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

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

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

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

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

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

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.