Concept
Output of a manager
The output of a manager, in Andrew Grove's equation, is the output of the organisation under them plus the output of the neighbouring organisations they influence. The manager's personal work counts only insofar as it raises what those people produce.
It is the single sentence a new manager most needs and least wants. The expert who was promoted measures the week by what they finished; Grove's equation says that number is zero unless it changed what the team finished. The consequences run through everything else in his book. Because the team's output is the measure, the manager's time is judged by leverage, how much each hour changes the team's production. Because the neighbouring organisations count too, the manager's job includes the people their team depends on and the people who depend on it, which is why so much of the work is meetings and information. And because the equation is about output rather than effort, the busiest manager is often the one producing least: their hours went into tasks that felt productive and multiplied nothing. Zhuo's version of the same idea is the Friday question: what did the team do this week that they could not have done without me, and what did they do that they could?
A real-life example
Ege, four weeks into leading a backend team in Maslak, notes in his Friday review that the team shipped the payments migration without him on the call. He had to stop himself from joining. By Grove's equation, it was his most productive week, and he had written no code.
How to use it
- 1Write the equation at the top of the weekly plan: my output is the team's output.
- 2Judge the week by what the team finished, not by what you finished.
- 3Ask on Friday what the team did without you, and count that as yours.