OKRs (Objectives and Key Results) are a management method that sets, for a given period (often a quarter), a few qualitative objectives, each paired with two to five measurable key results that prove it has been reached. The method was formalized by Andy Grove at Intel, then brought to Google by John Doerr.
A good objective says where you want to go; a good key result measures an effect (conversion rate, response time, retention), not a completed task. Team OKRs connect to company OKRs and are visible to everyone.
The method is widespread in tech. Its classic failure: OKRs that simply list the backlog, or results always hit at 100%, a sign they lacked ambition.
Why it matters when hiring
OKRs mostly matter for product and management roles (Product Manager, Engineering Manager, VP). Ask the candidate for an OKR they owned and missed: what it measured, what they learned. A candidate who confuses key results with a list of deliverables is probably working in roadmap mode, not impact mode.
