OKRs and KPIs are the mechanism through which Business Strategy shows up as concrete, measurable targets for the product org — e.g., 'a third of revenue from Europe by year end.'
A business-strategy shift doesn't tell product teams what to build; it sets the target. It's then up to Discovery (Product Discovery Process) to determine what, if anything, the product actually needs to change to hit that target, and up to Product Strategy to decide which of those changes is the most important to pursue right now.
Apply: Translate a business-strategy shift into a concrete OKR/KPI first, then run discovery to find out how hard hitting it will actually be, before committing a strategy to it.
Palace Hotels attached a pilot team to a single measurable key result — the share of bookings made online versus through the call center — rather than a feature backlog. The team's funding and evaluation were tied directly to movement on that one metric: a concrete instance of the general pattern of picking one number tied to a business result and holding the team accountable to moving it rather than to shipping a list of outputs.
A common failure mode is leaders believing OKRs alone will drive an entire transformation — that adopting the framework is the transformation. OKRs are one piece nested inside a rethought whole ecosystem of product creation (vision, strategy, empowerment, trust), not a stand-alone fix; see High-Alignment/High-Autonomy Model for the fuller cascade OKRs sit inside.
Per Cagan, Andy Grove designed OKRs as a mechanism for handing a product team a problem plus a success measure — the input side of Three Conditions for Empowerment — not as a personal or team goal-tracking ritual, which is how most companies now use them.
Cagan traces OKRs back to Andy Grove's original intent: a mechanism for handing a team a problem and a measure of success, then leaving the solution to them — not a personal goal-tracking ritual. He frames most companies' individual-goal use of OKRs as drift from that intent, and ties the original meaning back to Three Conditions for Empowerment and High Integrity Commitment (HIC) — the team is accountable for the outcome, not for executing a prescribed output.
OKRs originated with Andy Grove as a tool for handing a team a problem to solve plus a measure of success — deliberately not a prescribed solution. Cagan's application: assign OKRs to teams, not individuals, as a problem-plus-success-metric pairing, then let the team run Discovery (Product Discovery Process) to find the solution.