EOS Rocks: How to Set, Track, and Actually Complete Quarterly Goals
· Zentrix OS Team
Every quarter, leadership teams sit down, set their Rocks, and walk out of the room feeling energized. Three months later? Half those Rocks are sitting untouched. Sound familiar?
If you're running EOS (the Entrepreneurial Operating System), you know the promise: set the right priorities, execute relentlessly, and watch your business move forward. But there's a gap between setting Rocks and completing them — and most EOS teams fall right into it.
This post is about closing that gap. We'll cover what Rocks actually are, why they fail more often than they should, and exactly how to set, track, and complete them quarter after quarter.
What Are EOS Rocks — And Why Do They Matter?
The term "Rocks" comes from Stephen Covey's classic time management metaphor: if you fill a jar with pebbles and sand first, there's no room for the big rocks. But if you put the big rocks in first, everything else fits around them.
In EOS, Rocks are your 90-day priorities — the most important things that must get done this quarter to move your business forward. They sit above the day-to-day operations, above the urgent fires, above the "nice to haves." They are the big rocks.
Every leadership team member owns 3–7 Rocks per quarter. The company itself has Rocks too — usually 3–7 at the company level, aligned with the 1-Year Plan and the V/TO (Vision/Traction Organizer).
Why 90 days?
Ninety days is long enough to accomplish something meaningful, but short enough to stay focused and accountable. It's the sweet spot between vision and execution. Longer horizons drift. Shorter ones don't allow for real work to happen.
When Rocks work, they create a rhythm. Every quarter, your team makes measurable progress on the things that matter most. The business moves. People feel a sense of momentum and accomplishment. That's the EOS promise in action.
When they don't work, quarters feel like Groundhog Day — same priorities, same excuses, same lack of progress. That's frustrating, and it's more common than most EOS teams want to admit.
Why EOS Rocks Fail: The 5 Most Common Reasons
Before we fix the problem, let's name it clearly. Here are the five most common reasons Rocks don't get completed:
1. The Rock is too vague
"Improve marketing" is not a Rock. "Launch redesigned website by March 31" is a Rock. If you can't draw a clear finish line, you'll never know if you crossed it — and neither will your team.
2. Too many Rocks
When everything is a priority, nothing is. Teams that pile on 10+ Rocks per person are setting themselves up for failure. Focus is the engine of execution. Without it, effort scatters.
3. No single owner
Every Rock needs one person who owns it — not a team, not a committee. When ownership is shared, accountability evaporates. "I thought you were handling that." Sound familiar?
4. No tracking between quarterly sessions
Setting Rocks in a quarterly session and then forgetting about them until the next one is a recipe for failure. Rocks need weekly visibility — specifically, at your Level 10 meetings.
5. Rocks aren't connected to the bigger vision
When people don't understand why a Rock matters — how it connects to the 1-Year Plan and the long-term vision — motivation fades. Work without meaning is hard to sustain.
The danger of "on track" theater
One of the most insidious failure modes: team members who say "on track" every week even when they aren't — because there's no real mechanism to validate progress and the culture doesn't feel safe enough to say "I'm behind." Weekly check-ins only work if they're honest.
How to Set Rocks That Actually Get Done
Good Rocks don't happen by accident. They're the result of a deliberate process. Here's a step-by-step framework for setting Rocks that are specific enough to own, meaningful enough to matter, and achievable within 90 days.
Step 1: Start From the Vision
Before you brainstorm Rocks, revisit your V/TO — specifically your 1-Year Plan. What are the three to seven things you committed to accomplish this year? Your quarterly Rocks should be direct contributors to those annual goals.
Ask yourself: "What do we need to accomplish in the next 90 days to stay on track for our 1-Year Plan?" That's where your company Rocks come from. Then cascade: what does each department or person need to own to make those company Rocks happen?
Tip: The cascade matters
Individual Rocks should visibly support company Rocks. When someone can trace their personal Rock directly to a company priority, ownership becomes natural — it's not just their job, it's the mission.
Step 2: Apply the SMART + EOS Filter
Every Rock should pass a two-part filter: the classic SMART criteria, plus an EOS-specific ownership check.
The SMART + EOS Rock Filter
- Specific: Can you describe the end result in one sentence?
- Measurable: How will you know when it's done? What does "complete" look like?
- Achievable: Is this realistic in 90 days given everything else on the plate?
- Relevant: Does this Rock support a 1-Year Plan goal or company Rock?
- Time-bound: Does it have a clear completion date within the quarter?
- Single Owner: Is there one person — and only one — who owns this?
Run every proposed Rock through this filter. If it fails on any dimension, revise it before it leaves the room. Don't move forward with a Rock that doesn't have a clear owner or a measurable finish line.
Step 3: Limit the Number of Rocks
EOS recommends 3–7 Rocks per person per quarter. In practice, most high-performing teams land closer to 3–5. If someone has 7 Rocks and they also run their regular seat responsibilities, something is going to slip.
Push back on overloading. If someone wants to take on eight Rocks, ask: "If you could only complete three of these this quarter, which three would matter most?" That usually gets to the heart of it.
Common mistake: confusing Rocks with To-Dos
Rocks are not tasks. A Rock is a significant 90-day initiative that moves the needle. A to-do is something you complete in a week or less. If your Rocks look like a task list, they're probably too small — or you're overcomplicating your weekly actions into "quarter-level" status.
Step 4: Write It as a Completion Statement
The best Rocks are written as done statements — what will be true when this Rock is complete? This eliminates ambiguity and makes the end-of-quarter review effortless.
Examples of Weak vs. Strong Rocks
| Weak Rock | Strong Rock |
|---|---|
| Improve customer onboarding | New onboarding checklist + video series live by March 31, reducing churn in month 1 by 15% |
| Hire sales team | Two senior account executives hired, onboarded, and in first sales cycle by June 30 |
| Fix the website | Redesigned homepage and pricing page launched, with A/B test running by September 15 |
Step 5: Get Buy-In in the Room
Don't assign Rocks — have people own them. There's a big difference between "You're doing this" and "Do you own this?" When someone chooses their Rock and commits to it publicly in the room, accountability is already beginning.
Close the quarterly session with everyone reading their Rocks aloud. It sounds small, but the act of verbal commitment matters. It makes the Rock real.
How to Track Rocks Week by Week
Setting great Rocks is only half the battle. The other half is consistent, honest tracking throughout the quarter. This is where most EOS teams drop the ball — and it's entirely preventable.
Make Rocks a Standing Item in Your L10
Your Level 10 (L10) meeting is the heartbeat of EOS execution. And Rocks should be on the agenda every single week — not buried at the bottom, not skipped when time runs short.
In a properly run L10, each Rock owner gives a quick status update: On Track or Off Track. That's it. No lengthy explanations during the check-in. If a Rock is off track, it gets added to the Issues List for discussion later in the meeting (during IDS — Identify, Discuss, Solve).
On Track vs. Off Track — Keep it binary
Resist the urge to create a "mostly on track" or "in progress" status. Binary forces clarity. If someone isn't sure whether they're on track, they're off track. This black-and-white framing creates urgency before it's too late.
Use Milestones to Break Down the 90 Days
For complex Rocks, waiting until week 12 to realize you're behind is a costly mistake. Break your Rock into monthly milestones — what needs to be true at week 4, week 8, and week 12?
This gives you earlier signal. If a Rock that should be 33% complete is sitting at 5% in week 4, you have time to act. Without milestones, the first honest check comes too late.
Example: Milestone Breakdown for a Rock
Rock: New client onboarding system built and live by June 30
- Week 4 (End of April): Current process documented, gaps identified, new process mapped
- Week 8 (End of May): Checklist and email templates built, internal pilot complete
- Week 12 (End of June): System live, first three clients onboarded through new process
Create a Culture of Honest Reporting
No tracking system works if the team isn't honest. If people feel judged or shamed for saying they're off track, they'll say "on track" every week and show up at the end of the quarter with half-baked results.
Leaders set the tone here. Be the first to say "I'm off track on this — here's why and what I need." When the leader models vulnerability and problem-solving, everyone else follows. The goal is to surface issues early, not assign blame at the finish line.
The Mid-Quarter Check
Around week 6 or 7 — the halfway point — do a more deliberate Rock review. This doesn't need to be a separate meeting; it can live inside your L10. But it should be deeper than the weekly on/off-track ping.
Ask: Which Rocks are in danger? What obstacles are in the way? Do we need to re-scope any Rocks, or reassign ownership? Addressing this at week 6 is far better than discovering problems at week 11.
What to do when a Rock needs to be dropped
Sometimes, reality changes mid-quarter. A Rock that made sense in January doesn't make sense in February after a major client issue or a strategic pivot. It's okay to drop or rescope a Rock — but do it explicitly and transparently, not by quietly letting it fall off the list. Name the decision in your L10 so the team understands what changed and why.
The End-of-Quarter Rock Review
At the end of every quarter, your quarterly session begins with a Rock review. Each person reports: complete or incomplete. Simple. Clean. Honest.
Completion rates matter. EOS benchmarks suggest that high-performing teams complete 80% or more of their Rocks each quarter. If you're consistently below 80%, you have a systemic problem — either in how Rocks are being set, how they're being tracked, or both.
How to diagnose low completion rates
If your team is completing fewer than 80% of Rocks, look at these common causes:
- Rocks were too ambitious for 90 days
- Rocks weren't reviewed in L10 meetings consistently
- Too many Rocks were set
- The Rock didn't have a clear definition of "done"
- The owner didn't actually have the capacity or resources to execute
For incomplete Rocks, discuss briefly: Is it still relevant? If yes, carry it forward to next quarter — but re-examine whether the scope, timeline, or ownership needs to change. If no, drop it and move on. Don't drag stale priorities into a new quarter.
Why Tracking Tools Matter More Than You Think
Many EOS teams try to track Rocks in spreadsheets, shared docs, or whiteboards. And honestly? It works — until it doesn't. The problem with manual tracking is that it requires someone to maintain it, and when things get busy, that discipline slips.
When Rock tracking lives in a disconnected spreadsheet, it's easy to forget to update it. It's easy for team members to lose visibility. And it's nearly impossible to see at a glance which Rocks are on track, which are at risk, and which are being worked on right now.
The teams that consistently complete their Rocks have one thing in common: they've made tracking effortless. Not perfect. Not elaborate. Just easy enough that it actually gets done every week.
That's exactly what Zentrix OS is built for. It's an EOS-native operating system designed specifically for leadership teams running the system — bringing your Rocks, Scorecard, Issues, and L10 meeting structure into one place, so nothing falls through the cracks.
With Zentrix OS, every Rock has an owner, a status, and visibility across the team — updated in real time, visible in every L10, and connected to your company's quarterly priorities. You spend less time maintaining the system and more time actually executing.
Pulling It All Together: The Rock Execution Framework
Here's the complete framework in one place — a repeatable process you can run every quarter:
The Quarterly Rock Execution Framework
PLAN (Quarterly Session)
- Review 1-Year Plan and previous quarter's Rock completion
- Identify 3–7 company Rocks for the quarter
- Cascade to individual Rocks (3–5 per person)
- Apply SMART + EOS filter to every Rock
- Write each Rock as a completion statement
- Confirm single ownership and public commitment
TRACK (Every Week in L10)
- Each Rock owner reports: On Track or Off Track
- Off-track Rocks go to Issues List for IDS
- Check milestone progress at weeks 4 and 8
- Mid-quarter deep review at week 6–7
CLOSE (End-of-Quarter Session)
- Each person reports: complete or incomplete
- Diagnose patterns in incomplete Rocks
- Carry forward relevant incomplete Rocks (rescoped)
- Drop Rocks that are no longer relevant
- Celebrate completions — acknowledge the wins
The Rocks That Move the Business Are the Ones You Actually Track
Here's the truth about EOS Rocks: the framework is simple. Set priorities. Own them. Review them weekly. Complete them.
But simple isn't the same as easy. The gap between knowing the process and actually living it week after week is where most teams struggle. That gap is closed by two things: discipline and visibility.
Discipline means showing up to your L10 every week and being honest about where your Rocks stand. It means having the hard conversation when something is off track instead of hoping it fixes itself.
Visibility means everyone on the team can see the Rocks, the status, the owners, and the progress — without having to ask. It means the system doesn't depend on one person maintaining a spreadsheet that might or might not be up to date.
When you have both, Rocks stop being aspirational and start being real. Quarters stop feeling like repetition and start feeling like momentum. That's the version of EOS most teams are trying to get to — and it's absolutely achievable.
The question is: what's your system for making it happen?
Ready to stop letting Rocks slip through the cracks?
Zentrix OS is built for EOS teams who want their Rocks, Scorecard, L10 agenda, and Issues all in one place — so execution is effortless and nothing gets lost between quarterly sessions.
Try Zentrix OS Free