The Manager's Real Output Is the Team's Results

Management vs Leadership vs Doing the Work separated the three jobs so you could tell which one you’re in at any moment. This page takes the management job and asks the sharpest possible question about it: what does a manager actually produce? The answer is the single most important mental shift in this book, and once it lands, it changes how you judge a good day.

Here is the whole idea in one sentence, and it is worth reading twice: a manager’s output is not the work they personally do — it is the output of their team, plus the output of the neighboring teams they influence. Everything else in this book is, in some way, a consequence of that one line.

The principle, stated plainly

Most people carry a hidden formula for what “being productive” means, learned over years as an individual contributor:

my output = the things I personally made today

That formula is correct for a nurse, a warehouse picker, a barista, a developer. It is wrong for a manager. The manager’s formula is different:

manager's output = the output of my team
                 + the output of neighboring teams I influence

Notice what’s missing from the right-hand side: your own individual work. The report you wrote, the spreadsheet you cleaned up, the ticket you closed at 11pm — none of it appears in the equation directly. It only counts if it raised the output of the team or a team next door. This is the shift, and it is a genuine reversal, not a tweak.

The second term matters more than new managers expect. A good manager doesn’t only lift their own team; they make the teams around them better — the supplier team they unblock, the department they hand clean work to, the peers whose planning they improve. That influence is real output, even though you have no authority over those people. (We’ll return to that idea in Authority vs Influence.)

The evidence — where a manager’s leverage shows up

Researchers and large employers who have studied what separates strong teams from weak ones tend to find that a big share of the difference traces back to the manager — through clarity, support, and how blockers get handled — rather than the raw talent of individuals. Google’s internal people research (its Project Oxygen work, made public around 2013) reached a similar conclusion: managers mattered, and the behaviors that helped were coaching, clearing obstacles, and setting direction — not out-producing the team. Treat the exact figures loosely; the direction is the durable lesson. Your results show up through people.

Why this feels counterintuitive, and even unfair

If you’ve spent your career being rewarded for what you make, this formula feels like a trap. It means you can work hard all day — back-to-back, exhausted, no lunch — and produce, by the manager’s measure, nothing. You can also do very little visible work yourself and have your best output day ever, because the team shipped.

That is disorienting. The old scoreboard rewarded visible effort; the new one ignores it. Three feelings usually come with the shift:

• Loss of the daily “win.” As an IC you closed things — a task done, a shift finished, a patient discharged. Those little wins told you the day mattered. The manager’s wins are slower, shared, and harder to point at.
• The fear you’re not “doing anything.” Because your real work is conversations, decisions, and clearing paths, it can feel like you produced nothing you could hold up. Meanwhile the person who wrote the thing looks obviously busy.
• A quiet unfairness. You get credit when the team wins and heat when it loses, often for factors you only partly control. That comes with the role. The trade is that your ceiling is now far higher than any one person’s hands.

The way through is not to fight the feeling but to change what you’re keeping score of. You are no longer scoring effort produced. You are scoring results enabled.

The common trap — the manager who won’t let go of the doing

The most common failure of new managers is staying an individual contributor while wearing a manager’s title — grabbing the hardest task because it’s satisfying and they’re good at it. It feels productive and it is real work, but it usually lowers total output two ways: the manager becomes a bottleneck (everything routes through the one person who’s always heads-down), and the team stops growing because the interesting problems never reach them. If you notice you’re relieved to “finally get some real work done” once everyone leaves, that’s the trap talking. Your real work left with them.

The daily test

Because the formula is invisible, you need a way to apply it in real time. Here is the test, and it is small enough to use a dozen times a day:

For any activity I’m about to spend time on, ask: does this increase my team’s (or a neighboring team’s) ability to produce results? If yes, it’s likely real managerial output. If no, why am I doing it?

That’s it. Run it on your calendar, on the task you just grabbed, on the meeting you’re about to sit through. Some examples of how it sorts things:

Activity                                  Raises the team's output?
----------------------------------------  --------------------------
Clarifying a fuzzy goal for the whole team   Yes — everyone aims better
Removing a blocker 4 people were stuck on    Yes — unblocks 4 at once
A 1:1 that unsticks someone's week           Yes — one person, real lift
Rewriting a doc yourself because it's faster  Rarely — did the work,
                                              taught no one, made a
                                              bottleneck
Sitting silent in a meeting "to stay in loop" Probably not — question it
Answering an email only you can answer        Yes — but ask why only you

The last two rows are the point of the test. It doesn’t only catch obviously wasted time; it flags plausible-looking work — the standing meeting, the report you always do, the task you keep because it’s yours — and forces the question. Often the honest answer is “habit,” or “it feels productive,” or “no one told me I could stop.” Those are exactly the activities to prune.

In practice — a warehouse shift lead runs the test

A shift lead on a warehouse floor used to spend the first hour of every shift personally re-sorting a jammed pick line, because he was fastest at it. He ran the test: does this raise the team’s output? Only for that hour, only that line — and it taught no one. He spent one week instead showing two pickers how to clear the jam and giving them authority to do it. His mornings emptied out. He used the freed hour to walk the floor and catch problems early — a labeling error here, a slow lane there — that lifted the whole shift’s numbers, not one line’s. He personally touched fewer boxes and produced far more.

Leverage: the reason some actions count for far more

If your output is the team’s output, then not all of your actions are equal. The ones that matter most are the ones that raise many people’s output at once. That multiplier is called leverage, and it’s the manager’s most important idea after the output formula itself.

A single action can have wildly different leverage:

• Low leverage: doing one person’s task for them once. It helps a little, today, for one person, and creates dependence.
• High leverage: clarifying a goal the whole team was quietly confused about. Ten people now aim at the right target for weeks. One conversation, enormous return.
• High leverage: removing a shared blocker — the broken tool, the missing approval, the vague hand-off — that was silently taxing everyone. You spend an hour; you give back an hour to each of eight people, every day, indefinitely.
• High (or dangerously negative) leverage: a hiring decision, or how you handle a struggling team member. These touch the team for months. Done well they compound; done badly they compound too.

This is why “clarify the goal” and “remove the shared blocker” appear so often in this book. They aren’t nice-to-haves. They are the highest-return moves available to you, because a fix applied once, upstream flows into everyone’s work downstream.

The practical instruction: when you have an hour, spend it on the thing that lifts the most people, not the thing that’s most satisfying to finish. Seek the shared blocker, the shared confusion, the shared bottleneck. That’s where leverage lives.

Case study — Toyota’s andon cord

On Toyota’s production lines (a practice widely documented from the 1970s and 1980s onward), any worker who spots a defect can pull the andon cord and stop the line. It sounds like the opposite of productivity — one person halts everyone. But the manager’s leverage is in the system, not the personal firefighting: by making it safe and expected to stop the line, managers ensured a single defect got fixed at the source instead of being built into hundreds of cars downstream. The manager’s real output wasn’t any car they built. It was a floor full of people who could catch and fix problems without them — a high-leverage change to how the whole team produced results. Treat the specifics as illustrative; the lesson holds.

The contrast that makes it concrete

Two managers, same week.

Manager A shuts their door and writes a genuinely excellent report — the best on the team, sharp and complete. It’s their work, start to finish. Output: one great report.

Manager B writes nothing themselves. They spend the week in short conversations — showing five people how to tighten their thinking, catching a flaw here, sharpening a point there. Each of the five ends up with a report roughly 20 percent better than it would have been.

Now count. Manager A produced one report’s worth of value. Manager B produced five reports, each meaningfully better — call it the equivalent of a full extra report’s worth of quality, spread across the team, plus five people who now write a little better next time too. Manager B never wrote a word and out-produced Manager A several times over.

Manager A:  1 report  (their hands)          → 1 unit, once, no spillover
Manager B:  5 reports × 20% better           → ~1 extra report's worth now
            + 5 people who improved          → compounds every future report

If your instinct is that Manager A “did more” because they have something to show for it, that instinct is the exact thing this page is asking you to retrain. Manager A produced more personal work. Manager B produced more results — which, for a manager, is the only output that counts. And Manager B’s gains keep paying out long after the week ends, because people, unlike reports, carry the improvement forward.

Try this

Pick one normal workday this week and, before it starts, run the daily test on your calendar. For every meeting, task, and recurring commitment, write one word next to it: “lifts” (it raises the team’s or a neighbor’s ability to produce results) or “mine” (it’s personal work with little spillover). At the end of the day, add up roughly how many hours went to each. Then pick the single biggest “mine” block and ask honestly: could this be delegated, deleted, or turned into a “lifts” activity — for example, by teaching someone to do it instead of doing it yourself?

Reflect

1. Think about yesterday. By the manager’s formula — team output plus neighboring-team output — what did you actually produce, and how does that compare to how busy you felt?
2. Which task do you keep doing yourself mainly because you’re good at it or it’s satisfying, even though it doesn’t lift the team? What would it take to let it go?
3. Where is the highest-leverage move available to you right now — a goal you could clarify or a shared blocker you could remove that’s quietly taxing several people?
4. Are you more of a Manager A or a Manager B this month? What’s pulling you toward the one you don’t want to be?
5. What “win” did being a manager take away from you, and what could you count as a win instead so your good days still feel like good days?

Show reflections

1. The gap between felt busy and actually produced is the whole lesson made personal. Many people find a hard day produced little team lift, or a quiet day produced a lot. Naming that recalibrates your internal scoreboard away from effort and toward results.
2. This surfaces the “won’t let go of the doing” trap. The honest blocker is usually emotional — the task is where you feel competent — not practical. Letting go often means teaching someone once, which is itself high-leverage output.
3. A strong answer names something shared: a confusion or obstacle that touches several people, not a single person’s task. If you can only think of one-person fixes, spend a day looking upstream for the common bottleneck — that’s where leverage hides.
4. Most managers drift toward A under pressure, because personal work is visible and controllable while enabling work is slow and shared. Naming the pull — a demanding week, a need to feel productive, distrust that others will do it well — tells you what to manage in yourself.
5. Losing the daily “done” is real and worth mourning honestly. Good substitutes are enabling wins: someone unblocked, a goal that finally clicked, a person who did something this week they couldn’t do last week. Counting those keeps you motivated on the new scoreboard instead of secretly chasing the old one.