The OKR framework was designed in the 1970s at Intel, popularised by Google in the 2000s, and adopted by thousands of companies since. For decades, it was the gold standard for aligning teams around strategic objectives. But the world of work has changed dramatically — and most OKR implementations haven't kept up.
The problem with static objectives
Traditional OKRs are set quarterly or annually. Teams spend weeks crafting perfect objectives, only for reality to shift within days. A new competitor launches, a key hire leaves, a market opportunity emerges — and suddenly the goals you committed to are irrelevant. But the OKR remains, gathering dust in a shared doc.
This isn't a failure of execution. It's a failure of design. OKRs were built for a world where change was slow, where strategy could be set once and executed for months. That world no longer exists.
What AI changes
AI doesn't just help us write better OKRs. It fundamentally changes what an OKR can be. With real-time signal processing, OKRs can now be dynamic — updated as conditions change, suggested based on emerging patterns, and validated against actual outcomes.
- AI-suggested objectives based on company strategy and current market conditions
- Automatic progress tracking through connected tools — no manual check-ins
- Real-time validation: does this objective still matter? Here's the data.
- Cascading alignment from company to team to individual, maintained automatically
The new principles
If we were designing OKRs from scratch today, knowing what AI can do, they'd look very different. Here are the principles we think matter most:
- Objectives should be living documents, not quarterly artefacts
- Progress should be observed, not reported
- Alignment should be inferred, not declared
- Context should be continuous, not annual
The companies that thrive in the next decade won't be the ones with the best-written OKRs. They'll be the ones with the most responsive ones — objectives that adapt as fast as the world does.
