The leader who only asks for status isn't leading

A mid-size Brazilian clinic network (figures in Brazilian reais), 220 people, 11 units. Every Monday, from nine to noon, the regional manager gathers the unit leads. Each one speaks for eight minutes about the previous week. At the end, he consolidates it into a spreadsheet and sends it to the board. Thirty-three person-hours a month to produce information that already existed — scattered — in the scheduling, billing and inventory systems.

Across those three hours, almost no decision gets made. Decisions happen afterward, by message, when someone notices an outlying number that slipped past in the presentation.

01The idea: a manager's output isn't their own #

Andy Grove wrote High Output Management in 1983, while he was president of Intel. The book starts from an uncomfortable, productive definition: a manager's output is the output of the organization under their supervision, plus the output of the neighboring organizations they influence.

The consequence is direct. Nothing the manager does is worth anything on its own. A meeting only produces a result if it changes what the team does afterward; a report only matters for what it triggers. And if the manager's output is the team's, their time should go to activities that affect many people or many hours of work at once — what Grove called high-leverage activities.

He gives concrete examples of high leverage: training whoever executes, because the effect repeats in every execution afterward; intervening early in a process, when correcting is still cheap; and the regular one-on-one, which he treated as the highest-return meeting per minute on a manager's calendar. He also describes negative leverage: the manager who steps in without context, or who delays a decision many people depend on.

Grove also worked with the idea that a manager should measure operational output with pairs of indicators. Speed alone gets optimized against quality; volume alone gets optimized against rework. Measuring both together prevents the apparent improvement that just pushes the problem to the next stage.

02Why it still holds #

Because the status meeting is today the biggest consumer of managerial time at the average company — and it's an extremely low-leverage activity. It trains no one, intervenes early in nothing, and produces information that ages on the way to the board.

There is an honest reason it exists: without it, the manager can't see progress. The meeting isn't a behavioral vice; it's a prosthesis for a lack of information. As long as the state of the work only lives in people's heads, someone will have to gather them to extract it — and Mintzberg already showed, in 1973, that a manager's day is made of short fragments, which makes that extraction even more expensive in attention.

A warning about the lazy reading of Grove is worth adding. Reducing the argument to personal productivity misses the point. The book is about what the manager does with the leverage they have — and the first lever is the shared objective, exactly what he addressed with the objective-and-key-result pair, in the line that runs from Drucker and that we describe in from MBO to OKR.

03The math on the status meeting #

At the scale of the 220-person network, with 11 units. Explicit assumptions:

Want to see how this looks inside a real operation? Explore the platform.

The math: 36 meeting hours + 16.5 prep hours make 52.5 weekly hours; × 44 weeks make 2,310 hours a year; at R$ 180 per loaded managerial hour, around R$ 415 thousand, plus the cost of consolidation at the regional level, getting close to R$ 490 thousand. The point isn't ending the meeting: it's that today it spends that much to transport information, not to decide.

04Where this gets stuck in practice #

1. The meeting exists so the manager can know. As long as that's its function, it can't be cut down — only replaced by available information.
2. A metric on its own. Deadline gets measured without quality, or volume without rework, and the team optimizes exactly what's measured.
3. The one-on-one is the first thing cancelled. It's the highest-leverage activity on the calendar, and the one that gives way when the week gets tight.
4. Late intervention. The manager gets involved once the customer complains — the most expensive possible moment to fix things.
5. Delegation without criteria. A task gets handed off without stating the limit, and it comes back as a question two days later.
6. Presence gets confused with follow-up. Being in every meeting feels like control and eats the time that would produce the real effect.

05What data-driven management answers #

When work progress is logged where the work happens, status stops needing a meeting. The manager arrives already knowing what's late and why, and the group's time goes to what can only be done together: deciding, prioritizing and unblocking. That was the trade the clinic network in the example made — the three-hour meeting became 50 minutes of decision-making.

Paired metrics also get simpler when they come from the same source: deadline and rework measured in the same flow can't be dressed up against each other. The counterpoint on the fragmented calendar is in the manager's shattered day, and the repertoire for following up without it turning into pressure is in the six leadership styles.

At Relevanti, that's the tasks, operations and metrics modules of the platform, with the breakdown by department under solutions. If your Mondays look like the clinic network's, a conversation usually shows how much time can be given back.

Asking for status is management's most comfortable activity: it looks like work, fills the calendar, and changes nothing. Leading is what's left once it stops being necessary.