What a Manager Actually Does All Day

Authority vs Influence explained how a manager gets things to happen — mostly through influence, rarely through orders. This page zooms all the way in to the smallest scale: an ordinary Tuesday. What does the job actually consist of, minute to minute? If you have never managed, the honest answer is often surprising — and if you are new to it, the shape of your day may feel like proof you are doing it wrong.

This chapter strips away the mystique. It describes the real texture of a manager’s day, names the handful of activities that fill it, and makes one reframing that changes everything: the interruptions and meetings are not the things stopping you from doing your job. For a manager, they are the job.

The activities that fill the day

If you recorded a week of a manager’s time and sorted it into buckets, almost everything would fall into four recurring activities. They are not glamorous. They repeat endlessly. Together they are the work.

1. Gathering information

Before a manager can do anything useful, they need to know what is actually happening — not the tidy version in the status report, but the real state of the work, the mood of the team, the problem nobody has named yet. So a large share of the day is spent taking in information: reading messages, listening in a meeting, catching a worried expression, asking “how’s it going?” and actually attending to the answer.

This is not passive. A manager who only reads the dashboard is flying on instruments in fog. The richest information is verbal, informal, and often accidental — the offhand comment that reveals two people are quietly stuck, the tone that says a “fine” is not fine.

Sources of what a manager knows, roughly ranked by richness:
  a hallway conversation        ← rich, fast, often the real signal
  a one-on-one
  a team meeting
  a chat thread
  a written status report        ← tidy, slow, already filtered

2. Making and communicating decisions

Some of what a manager does is decide — which of two priorities wins this week, whether to ship now or wait, who takes the new project. But the decision itself is usually the small part. The large part is communicating it: explaining the why, making sure the right people heard it, checking it landed the way it was meant to.

A decision that lives only in the manager’s head has changed nothing. A hospital ward manager can decide to change how handovers work, but until every nurse across three shifts understands the new routine and why it matters, the decision is just an intention. Most of the “deciding” day is actually the communicating.

3. Coaching people

A chunk of the day goes to making the people around you more capable: asking the question that helps someone find their own answer, giving feedback, walking a new hire through something, reviewing work not to fix it but to develop the person who did it. This is slow, compounding work. It rarely shows a result today. It is also, over months, one of the highest-value things a manager does — because it raises what the whole team can do without you.

4. Being a role model for standards

This one is invisible and constant. A team watches what its manager does far more than what they say. How you treat a mistake, whether you cut a corner under pressure, how you speak about a customer or a colleague who is not in the room — these set the actual standard, silently, all day. You are modelling whether you mean to or not. A cafe manager who wipes a dirty table without being asked teaches more about standards in three seconds than a laminated checklist teaches in a month.

In practice — one hour, sorted

An operations lead, 9am–10am: skims overnight messages and spots a shipping delay (gathering); replies to a supplier and tells the team which order to prioritise today (deciding + communicating); spends ten minutes helping a new coordinator think through how to phrase a difficult email, without writing it for them (coaching); and, when a mistake surfaces, responds with “okay, what do we learn?” instead of blame (role-modelling). Four activities, one ordinary hour. None of it looks like “output” — all of it is the job.

The great reframe: interruptions are the work

Here is the belief that makes new managers miserable. They carry over the mental model of an individual contributor (IC) — the person whose value is the work they personally produce — where a good day means uninterrupted blocks to do the thing: write the code, build the report, treat the patients, make the coffee. In that world, an interruption is an enemy. It breaks flow, it steals the hour, it stops the real work.

So a new manager arrives, gets interrupted forty times, ends the day having “produced nothing,” and concludes they are failing.

They are not failing. They are misreading the job. For a manager, coordination is the product, and coordination happens through interaction. The question someone brings to your desk, the meeting where two teams align, the quick “have you got a sec?” — these are not obstacles between you and your work. They are your work. A manager’s day is supposed to be interrupt-driven, because a manager is the mechanism by which a group stays coordinated, and a group generates its coordination needs unpredictably, in real time.

This does not mean every interruption is valuable — plenty are noise, and later parts of the book are largely about shaping which interactions reach you. But the category is not the enemy. Once you stop resenting interaction as theft and start seeing it as the medium you work in, the whole day stops feeling like a war against your calendar.

The common trap — treating meetings as the opposite of work

“I had no time to work today, I was in meetings.” Almost every new manager says this, and it hides a mistake. For an IC, that sentence is true — meetings took time away from producing. For a manager, the meetings often were the producing: the alignment reached, the decision made, the person unblocked. The trap is keeping an IC’s scorecard while doing a manager’s job, so you feel unproductive precisely when you have been most useful. The fix is to redefine “work” to include coordination — then judge whether this particular meeting earned its place, not whether meetings in general are a waste.

The evidence — meetings are expensive, which is the point

Studies of organisational time generally find that meetings consume a large and rising share of managers’ and senior staff’s weeks, and that a meaningful fraction of that time is judged unproductive by the people in the room. It is easy to read this as “meetings are bad.” The sharper reading: meetings are expensive, and expensive things deserve scrutiny, not blanket avoidance. A meeting that aligns ten people for an hour has spent ten hours of the organisation’s time — so it should be worth ten hours. The lesson is to make each one earn it, not to pretend coordination is free.

Your scarcest resource is attention

An IC’s scarcest resource is usually time-on-task. A manager’s scarcest resource is attention — where you point your finite focus, and what you point it at.

This matters for a reason that is easy to miss: where a manager spends attention is a signal the team reads constantly. If you ask about numbers every day and never about how people are doing, the team learns that numbers are what matters here. If you drop everything for one loud stakeholder and let quiet requests wait, you teach people to be loud. You are not just spending your attention — you are broadcasting your priorities with it. A team calibrates itself to what its manager actually notices, not to what the manager says is important.

So attention is doing double duty all day: it is how you get information and make decisions, and it is a continuous message about what counts. Spend it carelessly and you will find the team optimising for the wrong things — not out of disobedience, but because they read your attention accurately.

High-leverage vs busywork that feels productive

Because attention is scarce and signalling, what you point it at is the central skill. The trouble is that low-value activity often feels more productive than high-value activity, because it produces visible, finishable results.

Answering forty messages feels great — look at that empty inbox. Rewriting a document yourself feels efficient — it is done, and done well. But these are often low-leverage: they help a little, once. Compare them to a good one-on-one, an hour spent clarifying a fuzzy goal so twelve people stop pulling in different directions, or removing the blocker that has quietly stalled a project for a week. These feel slow and rarely produce a tidy artefact — but each one multiplies across the whole team.

Low leverage (feels productive)      High leverage (feels slow)
--------------------------------     --------------------------------
clearing your inbox                  a real one-on-one
doing a task yourself                clarifying a vague goal
attending a meeting to be seen       removing a blocker
polishing your own slides            coaching someone to do it next time

The rule of thumb: leverage is how many people or how much future your hour touches. An hour that only affects your own to-do list is low leverage. An hour that changes what twelve people do all week, or that prevents a problem from recurring, is high leverage — even if it leaves your inbox untouched and gives you nothing to cross off. Protecting attention for the second column, against the constant pull of the first, is most of the discipline of managing well.

Case study — Andy Grove and the manager’s output

In High Output Management (1983), Intel’s Andy Grove argued that a manager’s output is not their own activity but the output of the teams they influence — so the leverage of an activity is how many people it affects and how deeply. His practical conclusion was that seemingly “soft” activities like one-on-ones and setting clear direction are among the highest-leverage things a manager can do, precisely because they quietly shape many people’s work for a long time. The dated specifics of 1980s Intel matter less than the durable lesson: judge your hours by their reach, not by how finished they feel.

The honest part: the emotional texture

No description of the day is honest without this. Managing feels different from doing, and the difference is uncomfortable in ways nobody warns you about.

• You context-switch constantly. A budget question, then a personal problem, then a technical decision, then a hallway crisis — often within one hour. The deep, single-focus flow you may have loved as an IC largely disappears. This is not a scheduling failure; it is the nature of a role whose input arrives from many people at once.
• You live in ambiguity. ICs often have problems with right answers. Managers mostly get problems with only trade-offs — decide with half the information, knowing you might be wrong, and own it anyway.
• You rarely finish anything cleanly. Few managerial tasks end with a satisfying done. People, priorities, and problems are ongoing. You tend the garden; you do not complete it.

If your day feels fragmented, ambiguous, and never quite finished — that is not a sign you are bad at this. It is a sign you are doing the actual job. The IC’s clean sense of completion is one of the real losses of the transition (the shift that feels like a demotion named it). Grieving it a little is normal. Expecting the manager’s day to feel like the IC’s day is the setup for feeling like a failure at something you may actually be doing well.

How it connects

This page is the ground-level view of ideas the rest of the book builds on. The claim that coordination is the product is the argument of why management exists; the claim that your output is the team’s results is the manager’s real output; and using attention as a signal is influence in miniature (authority vs influence). Later parts turn today’s rough sketch into craft — how to run a one-on-one, how to make a meeting earn its cost, how to give attention deliberately instead of reactively.

Try this

For three working days, keep a rough tally of where your attention actually goes — not planned, actual. Every time you finish an activity, jot one word for which bucket it was: info, decide, coach, model, or busywork. At the end, look at the shape. Notice two things: how much of your “unproductive” time was real coordination, and how much of your “productive” time was low-leverage busywork that merely felt good. You are not trying to fix anything yet — just to see the real distribution before you judge it.

Reflect

1. When you finish a day of managing feeling like you “got nothing done,” what were you actually doing during those hours — and was any of it high-leverage coordination in disguise?
2. Which of the four activities (gathering information, deciding and communicating, coaching, role-modelling) comes most naturally to you, and which do you quietly avoid?
3. What does your team read from where you spend attention? If they optimised purely for what you notice, what would they do more of — and is that what you actually want?
4. Name one low-leverage activity that feels productive to you and one high-leverage activity that feels slow. Which one is winning for your hours right now?
5. Which part of the emotional texture — constant context-switching, living in ambiguity, or rarely finishing — is hardest for you, and have you been treating it as a personal failing rather than the nature of the job?

Show reflections

1. The aim is to catch the IC scorecard in the act. Most “got nothing done” days are full of interruptions that were the real coordination — the honest move is to re-examine those hours before concluding they were wasted, then keep the reframe.
2. Everyone leans toward one or two buckets. The one you avoid is usually the one that would help the team most — coaching and role-modelling are the common blind spots because they show no immediate result.
3. This is the attention-as-signal idea made personal. If the honest answer is “they’d chase numbers and get loud,” that is feedback on where your attention actually points, regardless of your stated priorities. Adjust what you notice, not just what you say.
4. Good answers name the specific pull — usually inbox-clearing or doing a task yourself feeling better than a slow one-on-one. Naming it is the first step to protecting the high-leverage hour against the seductive low-leverage one.
5. The point is permission. Whichever is hardest, the reframe is that it is structural, not personal — the manager’s day genuinely is fragmented, ambiguous, and unfinished. Treating that as normal frees the energy you were spending on feeling like a failure.