Concept
Manager operating system
A manager operating system is the one page a first team's management fits on: weekly one-on-ones on the report's agenda, one team meeting that ends in decisions read aloud, a calendar planned by leverage, a feedback loop in both directions, and a quarterly look at each person's growth.
Grove argued that management is a production process with its own rhythm; Zhuo that the rhythm has to be simple enough to keep in the year when everything is new. The page is where they meet, and every idea on the road fills one of its five lines. One-on-ones: every direct report, weekly, their agenda, never cancelled. The team meeting: one a week with a stated purpose, closing with decisions, owners and dates. The calendar: high-leverage hours protected first, last week's low-leverage blocks moved into teaching. The feedback loop: one piece of criticism asked for and one given each week, praise in public the same day. The people review: each person once a quarter, where they are growing and what they need next. It is run for four weeks before being judged, because the first two feel artificial, and then changed only for reasons from the team, a new hire, a new goal, and never because a week was uncomfortable.
A real-life example
Four weeks in, Ege's page reads: one-on-ones Tuesday and Wednesday, six people, their agenda; team meeting Monday with the goal sentence read first; two afternoons blocked for design and one hour for teaching; one criticism asked for and one given each week; quarterly review booked. He has not written production code in three weeks, and the team shipped a migration without him.
How to use it
- 1Write the five lines tonight, by hand or in a note.
- 2Run it for four weeks before changing anything.
- 3Change a line only for a reason from your team, and write the reason next to the change.