If your team keeps losing focus in the weeds of daily work, you're not alone. Most organizations are drowning in to-do lists while their real priorities drift. EOS Rocks are designed to fix exactly that: a 90-day system for deciding what matters most and making sure it actually gets done.
This article covers what EOS Rocks are, how they work, how to write good ones, and how they compare to OKRs — so you can decide which system fits your team best.
What are EOS Rocks?
EOS Rocks are 90-day priorities set within the Entrepreneurial Operating System (EOS), a business operating framework popularized by Gino Wickman in Traction. The name comes from a Stephen Covey metaphor: if you fill a jar with big rocks first, you can still fit pebbles and sand around them. If you start with sand, the big rocks never fit. Rocks are your biggest quarterly priorities.
Big rocks = priorities
Sand, pebbles = small tasks, BAU, distractions
Start with the priorities and the small stuff will find a way to fit in; if you start by focusing on the small stuff, you'll never be able to fit in the bigger priorities.
In EOS, every leadership team member owns 3–7 Rocks each quarter — the commitments that, if completed, will move the business forward most. Everything else (the pebbles and sand) still gets handled, but it never crowds out the Rocks.
Rocks cascade across three levels:
- Company Rocks: the 3–7 highest priorities for the whole organization this quarter
- Departmental Rocks: team-level priorities that roll up to company Rocks
- Individual Rocks: owned by a specific leadership team member
How EOS Rocks work: The 90-day cycle
Rocks run on a quarterly cycle. At the start of each quarter — in a dedicated Quarterly session — the leadership team reviews what was accomplished last quarter, identifies the most important things to achieve this quarter, and assigns clear ownership.
The key mechanics:
- 90-day window: Short enough to stay focused, long enough to accomplish something meaningful.
- Single owner: Every Rock has one person accountable. Not a team — one name.
- On track / off track: At the weekly Level 10 (L10) meeting, each person reports Rocks status in one word. No long updates.
- Quarterly close-out: Rocks are marked done or not done. Incomplete Rocks carry into the next quarter's planning discussion.
The L10 meeting is central to how Rocks stay visible. It's a 90-minute weekly meeting where the first 5 minutes cover Rocks status. Simple, disciplined, consistent. Without the weekly review, Rocks quietly die.
How to write good EOS Rocks
Poorly written Rocks are the most common reason the system fails. Good Rocks are specific, measurable, and completable within 90 days. EOS recommends SMART criteria:
- Specific: "Launch the new onboarding flow" is a Rock. "Improve onboarding" is not.
- Measurable: "Reduce onboarding time from 14 days to 7 days" gives you a clear finish line.
- Attainable: Achievable within 90 days with available resources.
- Relevant: It must link to a company priority. If it doesn't move the needle on something that matters, it's not a Rock.
- Time-bound: The 90-day quarter is the boundary.
Here’s the difference in practice:
Each good Rock has a clear outcome, a deadline, and could be assigned to a single owner.
EOS Rocks vs OKRs: What's the difference?
If you've heard about both EOS Rocks and OKRs (Objectives and Key Results), you're probably wondering how they compare. Both are quarterly goal-setting systems. Both emphasize focus and accountability. But they're meaningfully different.
The honest answer: if your company runs EOS, use Rocks. If you want more measurement rigor or you're building a system from scratch, OKRs give you more precision. Some mature EOS teams layer OKR-style Key Results into their Rocks — using measurable outcomes to define what "done" looks like.
Rocks are also worth comparing to Wildly Important Goals (WIGs) from the 4DX framework and BHAGs. All three solve the same focus problem at different time horizons: BHAGs are 10–25 years, WIGs are annual, Rocks are quarterly.
Not sure whether EOS is the right operating system for your business at all? We've put together a direct comparison of EOS, Scaling Up, and OKRs — including when each makes sense and when it's probably overkill.
The EOS operating cadence
One of EOS's strongest features is its built-in rhythm: Annual Planning → Quarterly Rocks → Weekly L10 meetings → Daily huddles. The four cadences work together to keep strategy connected to execution:
That cadence maps almost exactly onto what StratOps practitioners recognize as the standard operating rhythm — annual goal architecture, quarterly priorities, weekly review loops, and continuous accountability. EOS packages this into a prescriptive system. StratOps treats it as a design principle you adapt to your context.
If you're running EOS Rocks, make the cadence stick by:
- Setting Rocks in a dedicated Quarterly: Full-day or half-day session, leadership team only, clear outputs.
- Reviewing weekly in L10s: Five minutes, green/red status only. Issues get IDSed separately.
- Scoring at quarter-end: Aim for 80% or higher. Consistently hitting 100% means Rocks are too easy. Below 70% means they're too ambitious.
The weekly check-in cadence is where EOS Rocks succeed or fail. Without it, Rocks become aspirational lists. With consistent weekly reviews, they become real commitments.
Common mistakes to avoid
- Too many Rocks: EOS recommends 3–7 per person. Teams that push 8–10 dilute focus and set themselves up for low completion rates.
- No clear owner: "Marketing team" is not an owner. One name, one person accountable.
- Rocks that are really projects: "Manage the website redesign project" is not a Rock. "Launch redesigned website" is.
- Skipping the weekly review: Skip a few L10s and Rocks quietly die by mid-quarter.
- No connection to company priorities: If a Rock doesn't connect to a company Rock or V/TO priority, question whether it belongs.
Tools for tracking EOS Rocks
EOS has a native tool ecosystem — ninety.io and EOSone are purpose-built for the full EOS framework. Both handle Rocks, L10 meeting agendas, scorecards, and issues lists.
If you want to track Rocks alongside OKRs, KPIs, and strategic initiatives in one view — or if you're running a hybrid EOS/OKR model — tools like Tability let you mix binary milestones with metric-based Key Results. Whatever tool you use, the mechanics matter more than the software: clear ownership, weekly status, quarterly review.
The bottom line
EOS Rocks work because they force a decision every quarter: what are the 3–7 things that truly matter most? Not your 30 roadmap items — the handful that will actually move the business forward.
If you run EOS, Rocks are the core of your quarterly cadence. If you want a simpler, more binary alternative to OKRs, Rocks-style 90-day priorities are worth borrowing.
The principle is universal: put the big rocks in first. Whether you call them Rocks, OKRs, WIGs, or something else, the discipline of naming your quarterly priorities and reviewing them weekly is what separates teams that execute from teams that just plan.
Want to track your quarterly priorities — Rocks, OKRs, or a hybrid — with built-in check-in cadence? Book a demo of Tability to see how it works.
.png)
.jpg)
