By week six of most quarters, at least one of your most important priorities has quietly fallen off the agenda. Not because anyone decided it wasn’t important. Because the urgent kept arriving, the calendar kept filling, and the thing that was supposed to be a priority this quarter became the thing you’d get to next week.
EOS Rocks exist to solve exactly this problem. A Rock is a specific, 90-day priority — the most important thing one person must complete this quarter to move the business forward.
What Rocks Are
The name comes from a metaphor most commonly associated with Stephen Covey’s time-management work: if you need to fit rocks, pebbles, and sand into a jar, you have to put the big rocks in first. The pebbles fill in around them. The sand fills in around the pebbles. Start with the sand — the small urgent stuff — and the rocks never fit.
Gino Wickman adapted this metaphor in his 2011 book Traction, which introduced the Entrepreneurial Operating System (EOS). In EOS, a Rock is a specific, 90-day priority: the most important thing one person or team must complete this quarter to move the business forward.
Rocks share a few defining characteristics:
- They are specific. Not “improve the client experience” — something like “Complete onboarding documentation for all active clients and conduct a structured review session with each one.”
- They are completable in 90 days. If it would take a year, break it down.
- They are binary. Done or not done. No partial credit, no scoring ranges. When the quarter ends, a Rock is either complete or it isn’t.
- They have one owner. One person is accountable — not “the team,” not “we.”
- They are genuinely important. Not tasks that would get done anyway, but priorities that require deliberate protection to survive the quarter.
Why 90 Days
The 90-day cycle is not arbitrary. Wickman argues in Traction that the human capacity to hold a single sprint of focused effort is roughly 90 days — long enough to accomplish something meaningful, short enough to maintain urgency.
One year is too long to hold a single priority with genuine focus. One month is often not long enough to complete something substantial. Ninety days hits the practical middle: long enough to matter, short enough to keep everyone honest about progress.
The other advantage is cadence. Four quarters means four deliberate moments each year when a team steps back, asks what was actually accomplished, and decides what matters most next. That rhythm, maintained consistently, is itself valuable.
What a Good Rock Looks Like
The most common failure in Rock-setting is writing Rocks too vague to know when they’re done. A good Rock should survive the done test: at the end of the quarter, can anyone in the room, without debate, say whether this Rock was completed?
Characteristics of a strong Rock:
-
Specific enough to have a clear done state. “Implement a client onboarding checklist” is too vague. “Design, test, and deploy a client onboarding checklist with all active clients completing it by end of Q3” is a Rock.
-
Bounded in scope. A Rock that is really three projects is not a Rock — it’s a phase. Break it down until one person can own it and complete it in 90 days.
-
Important enough to protect. If this Rock could get pushed aside by business-as-usual and no one would really notice, it’s probably not a Rock. Rocks are for the things that need to happen this quarter even when everything else is pulling at your attention.
-
Tied to a longer-term goal. A Rock without a strategic connection is busy work. The team should be able to answer “why does this Rock matter?” in one sentence.
Examples:
| Weak Rock | Strong Rock |
|---|---|
| Improve the website | Rewrite the services page and launch it before the end of Q3 |
| Hire someone | Post the operations coordinator role, complete all interviews, and extend an offer by October 1 |
| Build better processes | Document the three highest-frequency client delivery processes and have each reviewed by an active client |
| Work on business development | Hold discovery conversations with five potential referral partners and document findings on each |
Write the done definition alongside each Rock before the quarter begins. It prevents ambiguity and keeps accountability honest.
The Parking Lot
Most Rocks guides skip the parking lot entirely. That’s a mistake — it’s one of the most practically important parts of the whole system. A parking lot is a deliberate holding area for ideas that are real and worth doing, just not this quarter.
Without a parking lot, every good idea competes equally for Rock slots. Teams either try to make everything a Rock — and accomplish nothing properly — or they let good ideas disappear entirely. The parking lot is the honest solution: we see this, we agree it matters, and we’ve decided it’s not one of the three to seven things we’re protecting this quarter.
What the parking lot does:
- It gives people a place to put ideas without losing them.
- It makes the Rock-selection conversation easier — once an idea is parked, the debate is settled for this quarter.
- It creates a natural agenda for next quarter’s planning session.
A parking lot can be as simple as a shared document with a list. The format doesn’t matter. The discipline does.
How the L10 Meeting Keeps Rocks Alive
Rocks without accountability are just good intentions. The mechanism that keeps Rocks alive in EOS is the L10 meeting — a 90-minute weekly leadership meeting with a fixed agenda.
The L10 agenda, in order:
- Segue — 5 minutes. A brief personal or business win to open.
- Scorecard Review — 5 minutes. Key weekly metrics — green or red.
- Rock Review — 5 minutes. Each Rock owner gives a one-word update: on track or off track.
- Headlines — 5 minutes. Good news and bad news from around the business.
- To-Do Review — 5 minutes. Review of last week’s 7-day action items.
- Issues (IDS) — 60 minutes. Identify, Discuss, Solve. This is where real work happens.
- Conclude — 5 minutes. Rate the meeting, confirm to-dos, close.
The Rock Review step is five minutes by design. It is not a progress report. It is not a conversation about what’s happening on each Rock. It is two words per Rock, per owner: on track or off track. If something is off track, it goes on the Issues list and gets addressed in the IDS segment.
That structure matters because it prevents Rock Review from becoming a status meeting. On track or off track surfaces problems fast, without consuming the agenda.
The most common L10 failure is not missing the meeting — it’s softening the update. When Rock owners consistently say “on track” when they’re genuinely uncertain, it’s usually because nobody has made it safe to say otherwise. The concern doesn’t surface until the quarter closes. The leader sets that norm in the first few cycles: “off track” is a status update, not a confession.
Rocks that are never mentioned in a weekly meeting are Rocks that die quietly by month two. The L10 cadence is the mechanism that keeps them alive.
The 80% Target
In EOS, Wickman’s target is completing 80% of your Rocks in a given quarter — a number he set deliberately to reflect how businesses actually work, not as a consolation prize for missed goals.
That number surprises people who are accustomed to goal-setting systems that treat anything less than 100% as failure. Wickman’s logic is practical: a Rock set at a level of difficulty where 100% completion is guaranteed is not ambitious enough. The value of Rocks comes partly from the discipline of protecting real priorities — and real priorities sometimes lose, especially in smaller businesses where a single unexpected client issue or hiring delay can reshape a quarter.
What your completion rate tells you:
- Consistently at 100%: Your Rocks aren’t challenging enough, or the team is underreporting off-track status in the L10.
- Consistently at 80–100%: Healthy. Your team is setting Rocks well and protecting them through the quarter.
- Consistently below 80%: Something is wrong. Either Rocks are being set too ambitiously, there are too many of them, business-as-usual is crowding them out, or accountability is absent.
A system that demands 100% will teach your team to sandbag — to set Rocks they know they’ll finish, rather than Rocks that matter. The 80% target is a more honest accounting of how businesses actually work.
Why Rock Implementations Fail
The failure patterns for Rocks are as consistent as they are predictable.
-
Rocks are set but never reviewed. Without weekly check-ins, Rocks become quarterly aspirations. You write them in the first week of January and rediscover them in the last week of March. The L10 cadence exists specifically to prevent this — but only if the meeting actually happens.
-
Too many Rocks. When everything is a Rock, nothing is. If a team has twelve Rocks, they have a task list. Three to seven is a meaningful limit. The constraint is the point.
-
Rocks are tasks, not priorities. “Update the website” is a task. “Relaunch the services section with updated positioning and a new case study before the end of Q3” is a Rock. If your Rocks read like a to-do list, they’re probably tasks dressed up as priorities.
-
No clear done definition. A Rock without a done definition produces a quarterly debate about whether it was completed. Write the done state when you write the Rock.
-
Shared ownership. Every Rock needs one owner. When a Rock belongs to “the leadership team,” it belongs to no one in particular. One person is accountable — others can contribute, but accountability is singular. In practice, shared ownership also produces a specific L10 failure: when nobody is clearly responsible, nobody wants to be the one to say the Rock is off track in the meeting. The concern sits quietly until quarter-end, when it’s too late to course-correct.
-
Rocks are disconnected from strategy. Rocks that don’t connect to a longer-term goal or company direction tend to drift. When the quarter gets hard and priorities compete, the question “why does this Rock matter?” should have a clear answer. If it doesn’t, the Rock will lose.
-
No parking lot. Without a deliberate holding area for ideas that don’t make the cut, organisations either try to do everything — too many Rocks — or lose good ideas entirely. The parking lot is the pressure valve.
Three Rocks in Practice: A Northlight Example
The clearest way to make this concrete is to see what Rocks actually look like for a practice like Northlight — a consulting and advisory business where client delivery, content, and new service development all compete for attention each quarter.
These are related in intention to the OKR examples in OKRs for Canadian Small Businesses — the same underlying priorities expressed differently. Where the OKR version stacks measurable Key Results under each Objective, the Rock version bakes the completion criteria directly into the Rock. No sub-measures, no scoring ranges. Done or not done.
Rock 1: Client Delivery Owner: Elizabeth
Complete all active client deliverables on schedule and within agreed scope for Q3, with a structured mid-quarter check-in documented for each engagement.
Done when: All deliverables for Q3 engagements are signed off by contracted deadlines, and a written mid-quarter check-in summary exists for each active client.
Rock 2: Content Owner: Elizabeth
Publish six long-form posts on bynorthlight.ca and submit the site to five Canadian business resource directories.
Done when: Six posts are live and five directory submission confirmations are on file.
Rock 3: Workshop Pilot Owner: Elizabeth
Run the AI governance workshop pilot with two clients, collect structured feedback from each, and write a one-page go/no-go recommendation on formal development.
Done when: Both pilots are complete, structured feedback is documented, and a written recommendation is on file.
What you’ll notice: there are no Key Results underneath each Rock, no scoring ranges, no aspirational or committed designations. Each Rock is a thing to be completed. The intention behind each one is the same as its OKR counterpart — the method and the accountability mechanism are entirely different.
If that comparison is useful, EOS Rocks vs. OKRs goes deeper on when to use each one and how they can work in tandem.
Getting Started: A Practical Sequence
If you’re running Rocks for the first time:
-
Set company Rocks first. Before individuals set their own Rocks, the leadership team aligns on no more than seven company-level priorities for the quarter. Not every important thing — the most important things.
-
Write the done definition alongside each Rock. Before the quarter begins, every Rock should have a written answer to: “What would we need to see to call this done?” Do this together, not individually.
-
Assign one owner per Rock. Name them. Write the name next to the Rock. One person is accountable — others contribute, but accountability is singular.
-
Build the parking lot before you start. Capture every good idea that didn’t make the Rock set. It makes the selection conversation cleaner and gives you a natural input list for next quarter’s planning session.
-
Get the L10 meeting on the calendar before day one. Rock accountability depends on weekly check-ins. A Rock that isn’t reviewed each week is a Rock already in trouble.
-
Grade honestly at the end of the quarter. Done or not done — for each Rock. Then ask: what got completed, what didn’t, and what does that tell us about how we set and protected Rocks this quarter? The retrospective is where the most useful learning happens. What completed and what didn’t also become the natural input list for next quarter’s Rock-setting session — you don’t need to start from scratch.
Your first quarter will be imperfect. That’s expected and fine. Rock-setting gets meaningfully better once the team develops shared intuition for what a well-formed Rock looks like — and that only comes from doing it.
To help you get your first set of Rocks on paper, we’ve put together a Rocks Quarterly Planning Template with structure for company Rocks, individual Rocks, and your parking lot.
Download the Rocks Quarterly Planning Template
If you’re weighing Rocks against OKRs — or wondering which framework fits where your business is right now — read EOS Rocks vs. OKRs: Which Goal-Setting Framework Is Right for Your Business?