Management vs Leadership vs Doing the Work

The Shift That Feels Like a Demotion described the disorienting jump from doing the work yourself to being responsible for a team’s work. That shift is confusing partly because of three words we throw around as if they were the same thing: doing, managing, and leading. People say “she’s a great leader” when they mean “she ships good work,” or “he needs to manage better” when they mean “he needs a clearer vision.” The words blur, and the blur causes real damage — teams fail in specific ways, and if you can’t name which of the three is missing, you can’t fix it.

This chapter pulls the three apart. They are distinct activities with distinct purposes. Once you can see them separately, you can look at any struggling team — a software squad, a hospital ward, a warehouse shift, a cafe floor — and diagnose which one is absent. That diagnosis is one of the most useful skills a manager can own.

Three different activities, not three ranks

Here are the plain definitions. Read them slowly; the whole chapter hangs on keeping them separate.

• Doing the work is producing output yourself. Writing the code. Stitching the patient. Packing the boxes. Pulling the espresso shots. Your hands are on the thing the organization exists to produce, and at the end of the hour there is more of it because of you.
• Managing is coordinating and running the system that produces output. Who does what, by when, with what resources, to what standard — and catching problems before they cost you. You are not making the thing; you are making the thing-making work. Scheduling, prioritizing, unblocking, checking quality, keeping the pieces fitting together.
• Leading is setting direction and earning followership. Deciding where the group is going and why it matters, then being someone people choose to move with. Leadership answers “where are we headed and is it worth it?” — and it only counts if others actually come along.

DOING     →  produces the output itself         "the boxes get packed"
MANAGING  →  runs the system that produces it    "the right boxes get packed, on time"
LEADING   →  sets direction & earns followership "we know why we pack boxes, and we care"

The single most important thing to understand: these are not a hierarchy and not a career ladder. Leading is not “above” managing, and managing is not “above” doing. They are three different kinds of work, and any one person might be doing all three, two, one, or none in a given week — regardless of their title.

Title and activity come apart

Because they’re not a ladder, they detach from job titles in ways that surprise people:

• A nurse with no management title who calms a frightened patient’s family, sets the tone for the shift, and gets colleagues to rally in a crisis is leading — without a title.
• A team lead who assigns tasks, tracks the schedule, and keeps the project on the rails, but never articulates why any of it matters and inspires no one, is managing without leading.
• A senior engineer who ships brilliant work but ignores the roadmap and takes the team nowhere is doing without leading or managing.
• A department head who paints a thrilling vision but never sorts out who does what is leading without managing — and the vision quietly dies for lack of coordination.

Hold onto that: you can lead without a title, and you can manage without leading. The title on your badge tells you what the organization expects of you. It does not tell you which activities you are actually performing well.

In practice — spotting the missing one

A support team is drowning. Tickets pile up, people are stressed, the same fires keep flaring. You could assume the manager is “bad.” But which activity is missing? If tickets are chaotic and nobody knows who owns what, the managing is missing — it’s a coordination failure. If everyone knows their tasks but morale is flat and people are quitting because “what’s the point,” the leading is missing — nobody has made the work matter. If the manager is heads-down clearing tickets personally while the system stays broken, they’ve defaulted to doing and abandoned the other two. Same visible symptom, three completely different fixes.

Each one, done well and done badly

Definitions are easy to nod along to and hard to use. So here is what each looks like when it’s excellent and when it’s failing — the failing versions are what you’ll actually encounter.

Doing the work

Done well: A pharmacist double-checks a dosage, catches a dangerous interaction, and dispenses correctly. High-quality output, produced directly. Every organization needs enormous amounts of this — most of the value is created by people doing the work, not by people managing them.

Done badly: Sloppy, late, or careless output. A cook who plates food that comes back to the kitchen. This is the failure mode everyone already understands, which is exactly why the other two get neglected — bad doing is visible, while bad managing and bad leading hide.

Managing

Done well: A shift supervisor at a warehouse looks at tomorrow’s inbound volume, staffs the right number of pickers, positions the fast-moving stock near the door, and has a backup plan for the forklift that keeps breaking. When the trucks arrive, everything flows. Good management is often invisible — you notice it only by the absence of chaos.

Done badly: Two people assigned the same task while a third sits idle; a deadline nobody was told about; a quality problem caught by the customer instead of by the system. Bad management shows up as recurring, preventable friction — the same avoidable problem every week.

Leading

Done well: A clinic director explains why a painful switch to a new records system is worth it — for patients, for the staff’s own sanity in six months — and the team, though tired, chooses to push through. People move because they believe, not merely because they were told.

Done badly (two flavours): One is the leader with a grand vision that inspires no one — a poster on the wall nobody believes. The other is more dangerous: charismatic direction pointed the wrong way, taking a committed team confidently off a cliff. Leadership done badly isn’t just weak; it can be actively destructive, precisely because people follow it.

The common trap — mistaking doing for managing

The most common trap for new managers is collapsing all three into doing. Under pressure, doing feels safe: it’s concrete, you’re good at it, and it produces visible output today. So the new manager grabs the hardest task and does it themselves. The team is left uncoordinated (no managing) and directionless (no leading), while the manager feels productive because their own hands are busy. The tell: you end the week proud of what you personally finished, and unable to say what your team accomplished. That inversion is the subject of the next chapter, The Manager’s Real Output Is the Team’s Results.

The three blind spots

Because the activities are distinct, a manager can be strong at one or two and blind to the rest. Each blind spot has a signature cost.

The manager who only does the work. They’re often a promoted star performer who never let go of the craft. Output flows from their own hands, but the team is uncoordinated and uninspired. Cost: the team never grows past what one person can personally produce, and the moment that person is overloaded — which is always — the whole thing stalls. They become the bottleneck they were promoted to remove.

The manager who only leads with vision. All inspiration, no operations. Big speeches, exciting direction, and then… nothing lands, because no one turned the vision into who-does-what-by-when. Cost: a demoralizing gap between the promised future and the shambolic present. Teams under a vision-only leader burn out chasing goals with no working system beneath them, and eventually stop believing the speeches.

The manager who only administers process. All coordination, no direction and no hands. Meetings run on time, spreadsheets are immaculate, tasks are assigned — but nobody knows why, and the manager can’t help when the work itself gets hard. Cost: a team that is efficient at doing things that may not matter, with flat morale and no sense of purpose. Process becomes the point instead of the outcome.

Only DOING      → bottleneck; team can't scale past one person
Only LEADING    → inspiring vision, chaotic reality; burnout
Only MANAGING   → orderly, purposeless, uninspired; efficient at the wrong things

Notice that each blind spot is someone’s strength taken alone. The doer’s craft, the leader’s vision, the administrator’s order — each is genuinely valuable, and each becomes a liability when it crowds out the other two.

Case study — Apollo 13, April 1970

When an oxygen tank exploded on the Apollo 13 spacecraft in April 1970, flight director Gene Kranz’s ground team had to bring three astronauts home alive with almost no margin. The response is a clean picture of all three activities at once. Leading: Kranz set an unambiguous, believed-in direction — “failure is not an option” — that steadied a frightened room. Managing: he coordinated dozens of specialists, sequenced the problems, and allocated scarce power and time. Doing: engineers on the ground physically built and tested the improvised carbon-dioxide filter fix — hands on the actual problem. Remove any one of the three and the crew doesn’t make it. The lesson isn’t the heroics; it’s that a high-stakes result required direction, coordination, and hands-on work, held together at the same time.

Most real roles blend all three

So which should a manager do? In almost every real managerial role, the honest answer is all three — the question is the mix. You will do some hands-on work, run the coordinating system, and set and sell direction. Pretending you can pick just one is how the blind spots form.

And the right blend is not fixed. It shifts with the situation and with the team:

• A new or junior team needs more managing — tight coordination, clear standards, close guidance — because the system isn’t yet self-running. It also needs visible doing from you, to set the bar for what “good” looks like.
• A mature, senior team needs less hands-on managing and more leading — set direction and get out of the way. Over-managing a capable team reads as distrust and drives good people out.
• A crisis compresses all three and tilts toward decisive leading plus hands-on doing — as Apollo 13 showed — because there’s no time to build slow consensus.
• A steady, healthy operation tilts toward managing and light-touch leading — keep the system humming, keep purpose alive, resist the urge to meddle.

The skill is not picking one activity forever. It’s reading which one the moment needs and shifting your weight toward it — the same diagnostic muscle from the support-team example above, turned on yourself.

The evidence — matching your style to the situation

A long line of leadership research (the “situational” and “contingency” schools that grew up from the 1960s onward) converges on a simple, well-supported idea: there is no single best way to lead or manage across all conditions. What works depends on the maturity of the people and the demands of the task — a capable, motivated team needs a lighter hand than a brand-new one, and a crisis needs faster, more directive calls than a calm quarter. Treat any “one true style” advice with suspicion; the durable finding is that the mix must move with the situation.

How it connects

This three-way split runs under the rest of the book. Why Management Exists is really about why the managing activity is necessary at all — coordination doesn’t happen for free. The Manager’s Real Output Is the Team’s Results explains why you must stop defaulting to doing. Authority vs Influence is the mechanics of the leading activity — how followership is actually earned, with or without a title. And What a Manager Actually Does All Day shows where the three activities land in a real calendar.

Try this

This week, keep a rough time log split into three buckets: doing, managing, and leading — even five-minute notes are enough. At the end of the week, add up roughly how your time landed across the three, and ask one question: does this mix match what my team actually needs right now? If you’re managing a new team and spent the week heads-down doing, or leading a senior team and spent it micro-coordinating, you’ve found your gap. Pick one bucket you underspent on and deliberately move an hour into it next week.

Reflect

1. In the past week, which of the three — doing, managing, leading — did you spend the most time on? Which the least? Was that the right mix for your team’s situation?
2. Think of the best boss you’ve had. Which of the three were they strongest at, and which (if any) did they neglect?
3. Recall a struggling team you’ve seen. Using the diagnosis above, which activity was actually missing — and was it being misdiagnosed as something else?
4. Which of the three blind spots — only doing, only leading, only administering — is your most likely default under pressure, and why?
5. Have you ever seen someone lead without a title, or hold a title without leading? What did that reveal about the difference between the two?

Show reflections

1. The value is in the honest tally, then the match test. Time spent isn’t good or bad in itself — heavy doing is right for some moments and wrong for others. A strong answer names both the mix and whether the situation justified it.
2. Great bosses are rarely elite at all three; usually they’re strong at two and aware of the third’s importance, so they compensate (delegate the managing, borrow a vision, etc.). Naming what they neglected is often more instructive than naming their strength.
3. This is the core diagnostic skill of the chapter. The best answers catch a misdiagnosis — “we thought the manager was lazy, but really nobody had set direction” — because that’s exactly the error the three-way split is designed to prevent.
4. Most people default to their old strength: doers keep doing, visionaries keep visioning, organizers keep organizing. Knowing your default is what lets you catch yourself reaching for it when the moment needs something else.
5. This separates title from activity — the load-bearing idea of the page. Leadership without a title proves it’s about followership, not authority; a title without leadership proves the badge guarantees nothing. Both point to Authority vs Influence.