EOS and Traction
EOS, the Entrepreneurial Operating System (Gino Wickman, Traction, 2011), is the most widely installed operating system in the SMB world: six components run through standard artefacts, 90-day Rocks, a weekly Scorecard, the Issues List, and the Level 10 weekly meeting. Its genius is adoptability: an entire operating rhythm a fifty-person company can install from a book.
What it teaches, and what we carry
EOS saw two things earlier and more clearly than most of the shelf. First, issues are a component of the operating system, not an embarrassment: a standing Issues List, worked every week through IDS (identify, discuss, solve), made issue-processing a scheduled habit rather than a crisis response. Our Issues and Obstacles Log carries that heartbeat forward with gratitude, adding the escalation rule and the cross-team reading that a bigger organism needs. Second, the Scorecard split: weekly operational numbers kept deliberately separate from Rocks is the same wall we build between the KPI scorecard tracking business-as-usual and OKRs tracking change, and Hoshin Kanri drew the same line a generation earlier. Three systems, one wall: that convergence is a finding. The Level 10 meeting, likewise, is a well-designed check-in by another name, and its discipline transfers directly.
The natural hybrid
EOS and OKRs meet constantly in the wild, because EOS companies that scale often want more reach than a Rock provides. The join is clean: keep the EOS rhythm (the weekly meeting, the scorecard, the issues habit) and let Rocks mature into OKRs where ambition matters, gaining aspirational targets, confidence assessment and graded retrospectives on top of the delivery culture EOS built. Rocks are commitments and OKRs are bets; a healthy portfolio holds both, and knowing which is which is most of the trick. Above the V/TO, the strategy library, Where to Play, How to Win and Strategic Pillars, supplies the choosing layer EOS deliberately keeps light.
One line to keep: EOS built the habit; OKRs raise what the habit aims at.
Credited to Gino Wickman (Traction, 2011). Machinery connections are ZOKRI methodology.
We run EOS. Should we switch to OKRs? +
Keep the rhythm, raise the ambition. The weekly meeting, scorecard and issues habit EOS built are assets; the join is letting Rocks mature into OKRs where reach matters, gaining stretch targets, confidence assessment and graded retrospectives on top of the delivery culture you already have.
What is the difference between Rocks and OKRs? +
Rocks are commitments; OKRs are bets. A healthy portfolio holds both, knowingly, and knowing which is which is most of the trick.
EOS built your habit. We raise what it aims at, with an implementation that respects the rhythm you already run and adds the strategy layer EOS keeps light.