A Tribute to Andy Grove: The Intel Legend Who Pioneered OKRs

Key Takeaway: Andy Grove invented OKRs in the 1970s at Intel and explained them in less than 5 pages in his book High Output Management. His simple, focused, employee-led philosophy still anchors how Perdoo thinks about goals and OKRs today. If you want to understand why OKRs actually work, start by reading Grove's 2 questions: where do I want to go, and how will I pace myself to see if I'm getting there?

Andy Grove passed away on March 21, 2016, at the age of 79. A decade later, his legacy hasn't faded. If anything, it's grown. The framework he developed at Intel in the 1970s now powers how thousands of companies around the world set and execute their strategy. Perdoo is one of them. Most of what we believe about goals, focus, and execution traces back, directly or indirectly, to him.

This is our tribute, refreshed for 2026.

Who Andy Grove was

Born András István Gróf in Hungary in 1936, Grove survived the Holocaust under a false identity, then escaped Communist Hungary at age 20 with little English and no money. He made his way to the United States, finished his education, earned a PhD in chemical engineering, and joined Fairchild Semiconductor, where he worked alongside Gordon Moore of Moore's Law.

In 1968, Moore left Fairchild to co-found Intel with Robert Noyce. Grove joined them as employee number three. He became Intel's president in 1979 and CEO in 1987. During his tenure, Intel's revenues grew from $1.9 billion to $26 billion, turning what had been a memory chip startup into one of the defining technology companies of the 20th century.

What's worth pausing on isn't the financial outcome. It's the operating philosophy that produced it. Grove was famously demanding and exacting, but also warm and empathetic. He believed in what he called "constructive confrontation," the idea that open and honest debate was the only way to solve real problems. He believed managers should delegate what they know best, not what they know least, so they could monitor progress effectively. And he believed in something he called "managerial leverage," the idea that the best leaders dramatically multiply the output of everyone around them.

Most of all, he believed in execution. As Grove himself put it: "It almost doesn't matter what you know. It's what you can do with whatever you know."

This is exactly the conviction that sits underneath OKR.

How OKR was born

The term "Management by Objectives," or MBO, was first coined by Peter Drucker in his 1954 book The Practice of Management. But MBO in practice had become something Grove described as a tool to control employees with tired annual performance reviews and misaligned bonuses. He saw a better way to use the underlying ideas.

In his 1983 book High Output Management, Grove introduced what he called Intel Management by Objectives, later shortened to Objectives and Key Results. He explained the whole concept in less than 5 pages. That's worth emphasizing. The framework that now powers companies from Google to Spotify was first described in a tiny fraction of a book most people had never heard of.

Grove distilled OKR into 2 questions:

1. Where do I want to go? (The answer provides the Objective.)
2. How will I pace myself to see if I'm getting there? (The answer gives us milestones, or Key Results.)

That's it. 2 questions. Everything else, the cascading, the alignment, the cadence, the scoring, the individual versus team ownership debates, is downstream of that core insight. Get the 2 questions right, and you have OKR.

Grove handed the baton to John Doerr, who was an engineer at Intel in the 1970s and one of the first people taught the OKR system in Intel University. Doerr later took the framework to Google, where it shaped how Larry Page and Sergey Brin ran the company in its earliest years, and from there into thousands of organizations worldwide. Doerr's 2018 book Measure What Matters brought it to a global audience. But Doerr, by his own admission, was the messenger. Grove was the inventor.

The quotes that still shape how we think about OKR

What I find remarkable, reading High Output Management now, is how much of what Grove wrote in 1983 still applies word-for-word to companies in 2026. Here are some of the lines that have stayed with me:

"The one thing an MBO system would provide par excellence is focus."

This is still the single most important promise of OKR. Not better tracking. Not nicer dashboards. Focus. The discipline of choosing what matters most, then defending that choice against everything else competing for attention.

"We see a nesting hierarchy of Objectives: if the subordinate's Objectives are met, the supervisor's will be as well."

This is the cascading principle, decades before anyone called it that. It's why we obsess over making sure team OKRs flow from company OKRs, and why misalignment between levels is one of the most common reasons OKR programs fail.

"Key Results can come in like clockwork, but the Objectives can still be missed. So it is entirely possible for a subordinate to perform well and be rated well even though he missed his specified Objective."

This one is profound. Grove understood, in 1983, that judging OKR achievement purely by the numbers misses the point. The Objective is what matters. Key Results are how you pace yourself. Hitting all your Key Results without moving the Objective forward is a clear sign something's wrong with the design.

"The MBO system is meant to pace a person, to put a stopwatch in his own hand so he can gauge his own performance. It is not a legal document upon which to base a performance review."

This is, in my view, the single most important sentence Grove ever wrote about OKR. The moment you tie OKR achievement to bonuses or performance reviews, you've turned the system into something else entirely. People stop setting ambitious goals. They start gaming the numbers. The whole framework collapses into a defensive exercise. We still see companies make this mistake constantly, and the warning has been in print for 40 years.

"To be useful a Key Result must contain very specific wording and dates, so that when the deadline time arrives, there is no room for ambiguity."

Specificity is non-negotiable. Vague Key Results are the most common failure mode I see when auditing OKR programs, and it's the easiest thing to fix.

Why Grove's thinking still anchors Perdoo

OKR has been packaged, repackaged, productized, gamified, and consultant-ized hundreds of times since Grove first wrote about it. Most of that packaging has drifted away from his original intent. Some of it explicitly contradicts it.

What we believe at Perdoo, and what we've believed since we started over a decade ago, is that the best version of OKR is the closest version to Grove's original. Simple. Employee-led, not management-imposed. Focused on learning and adjustment, not on judgment. A tool for the person doing the work to pace themselves, not a control mechanism imposed from above.

That belief shapes everything we build. It's why we focus on connecting strategy, OKRs, and KPIs in one system rather than treating OKRs as a standalone goal-tracking layer. It's why we built our AI coach (Vince) and AI assistant to help people write better Objectives and Key Results rather than to police whether they're being "done correctly." It's why we keep pushing companies toward genuine OKR maturity instead of just selling them software and calling the job done.

In a real sense, every line of Perdoo's code, every blog post we publish, every customer conversation we have is built on what Grove laid out in those 5 pages.

Worth reading, again

If you've never read High Output Management, the easiest way to honor Grove's legacy is to read it. It's still the best book on management that exists, in my opinion. Mark Zuckerberg, Brian Chesky, Ben Horowitz, and many others have publicly cited it as foundational. It's not long, it's not difficult, and you'll come away with a fundamentally clearer view of what good management actually looks like.

If you've already read it, read it again. Different chapters land differently at different points in your career, especially the ones on operational reviews, 1-on-1s, and the role of the middle manager.

The advice worth taking today

Here's the concrete move you can make this week.

Pick your current most important Objective, whether you call it that or something else. Ask yourself Grove's 2 original questions. Where do I actually want to go? And how will I pace myself to see if I'm getting there? Write the answers down in a sentence each.

If the answers are crisp, congratulations. You're using OKR the way Grove intended.

If they're fuzzy, you've just found the most important thing to work on this week. Refining those 2 answers does more for your strategy execution than almost any other single act of management.

Andrew Grove may have passed, but the framework he left behind is still doing its job 40 years later. The least we can do is keep using it the way he meant.