Grove taught Intel managers that their output isn't theirs
Andrew Grove ran one of the most successful technology companies in history and wrote its management handbook. The first lesson is almost insulting.
Andrew Grove joined Intel as employee number three, built it into the world's dominant semiconductor company, and wrote High Output Management to explain how he thought about running people. He opened with a concept that managers tend to resist on first hearing: a manager's output is not what the manager personally produces. It is the output of the entire organization the manager oversees.
If a team is underperforming, the manager's own hard work is beside the point.
Grove illustrated his framework with a breakfast factory -- a thought experiment about boiling eggs, toasting bread, and pouring coffee that had to arrive simultaneously. The lesson was about identifying the limiting step in any process, because the bottleneck controls the whole system. Fixing the fastest step while the slowest idles solves nothing.
The same logic applies to people. Grove believed one-on-one meetings were among the highest-leverage activities a manager could do -- not status updates, but the direct report's meeting, a space where the subordinate surfaces what the manager can't see from above. He held them weekly and prepared for them as seriously as external reviews.
He also helped develop Objectives and Key Results -- the OKR framework later adopted by Google -- as a tool for keeping an entire organization's effort pointed at the same destination. Two questions in writing: where do we want to go, and how will we know we're getting there.