How to Write EOS SMART Rocks That Actually Get Completed

Daniel Madhan
6 days ago
8 min read

Most EOS™ teams create Rocks™ every quarter. But here's the truth very few teams actually complete them. The reason usually isn't laziness or lack of effort. The real problem starts with how the Rock was written in the first place.

The Quiet Death of a Rock by Week 6

Think about it this way. If a EOS SMART Rocks is vague, has no way to measure progress, or nobody can clearly tell when it's "done," it's going to slowly fall apart. Around Week 6, people stop talking about it. By the end of the quarter, it quietly gets copied onto next quarter's list.

The pattern that exposes bad Rock writing

If your team keeps rolling the same Rocks forward, the writing is almost certainly where things are going wrong.

What SMART Means in the Context of Rocks (Not Just Generic Goal Setting)

The 5 Letters Most People Already Know

SMART is an acronym for Specific, Measurable, Attainable, Relevant, and Time-bound. You've likely come across this before. However, in EOS SMART Rocks are more than just a typical goal you might write on a whiteboard or in a notebook.

SMART Rocks Five Letters, EOS-Specific Meaning

Why EOS SMART Rocks Are Different From Generic Goals

Your company's top priority for the next 90 days is a Rock. One person owns it. Your team reviews it every week at the Level 10 Meeting™. With that constant attention, a poorly written Rock doesn't simply fade away it's dragged through weekly meetings, where everyone smiles and says "on track" even when it's obviously going nowhere.

Measurable: The Letter Most EOS Teams Miss

Measurable is the area that most teams miss in EOS. Your Rock should have a clear finish line, not just a general direction to walk towards. Consider the difference between these two: "Improve onboarding" says nothing about when you're finished. The "Complete and launch an updated onboarding checklist for all new hires by September 30" is a clear indicator of what done looks like.

Attainable: Pushing vs Unrealistic

Attainable also trips people up more than you'd expect. There's a big difference between a goal that pushes you and a goal that's just unrealistic. A good Rock should challenge your team, but if it requires you to loop in six different departments, juggle three outside vendors, and endure a full system overhaul, that's not one Rock. That's a whole project in one sentence. In such a case, the obvious solution is to divide it into smaller, more specific Rocks that can be owned and completed by one person.

SMART Letter-by-Letter With the EOS-Specific Twist

	Means	The EOS-specific twist
S	Specific	Not a direction to walk toward a concrete outcome the whole team can picture
M	Measurable	The area most EOS teams miss. A clear finish line, not just a direction
A	Attainable	Pushes you but doesn't require 6 departments + 3 vendors + a system overhaul
R	Relevant	Connects directly to your V/TO and one-year plan
T	Time-bound	A real date, 90 days out not "end of quarter someday"

The Difference Between a Rock Title and a Rock Definition of Done

The Title Is Just a Name Tag

The Rock title is just a name tag. Something like "Launch referral program." A name tag doesn't tell you anything about what Done actually looks like. That's what the definition of done is for. It's the written description that tells the Rock owner and everyone else on the leadership team™ exactly when the job is complete.

What Happens When You Skip the Definition of Done

Skip the definition of Done and you're asking for trouble. Each check-in becomes a guessing game. The Rock owner feels like they're almost there. The integrator™ doesn't even know if the work has begun. Nobody's lying they just have completely different pictures in their heads. That kind of disconnect slowly erodes team trust. More than most leaders realize until it's too late.

The 3 Questions a Strong Definition of Done Answers

So what makes a strong definition of Done? It addresses three simple questions: What will be created that did not exist before? Who did what? and by when?

A Real Example: Vague Title vs Sharp Definition

In practice, it means: Referral program launched landing page is live, email sequence is running, and the first 10 referral partners have been contacted by October 1.

Why This Eliminates Quarter-End Surprises

Read that again. You know exactly what Done looks like. No place for "I thought we meant something different." No back-and-forth at the quarterly meeting. No awkward silences when someone asks for an update.

That's the power of a real definition of Done. It's not a long document or a complicated checklist. It's one or two sentences that eliminate the ambiguity and ensure everyone on your team is on the same page.

What a strong Definition of Done answer

What will be created that did not exist before? Who did what? And by when?

Before (vague)	After (SMART)
"Improve customer service."	"Reduce average customer response time from 48 hours to less than 8 hours by September 30."
"Improve the recruitment system."	"Document and implement a 5-step interview scorecard for all sales hires used in at least 3 interviews before quarter end."
"Work on company culture."	"Conduct and report results of quarterly employee pulse survey (80% participation or more) by Week 11."
"Update the website."	"Launch redesigned service pages for all 4 core offerings live and indexed by October 1."
"Grow revenue."	"Close 6 accounts in Q3 at or above $2,500 MRR each."

Why "Improve Customer Service" Means Nothing

The "before" versions sound good but have little meaning. "Improve customer service" could mean a hundred different things to a hundred different people. But "48 hours to less than 8 hours by September 30"? That's crystal clear. Either you hit it, or you didn't.

Sharp Rocks Give You a Real Finish Line

That's what SMART rewriting is all about. You're not only making goals sound good, but you're giving them a finish line. A number, a date, and a tangible thing that you can point to and say, "Done".

No Guesswork, Just Yes or No at Quarter End

If a Rock is written like this, the person responsible will never have to ask themselves if they are on track. They count, see the date, and know where they are. No guesswork, just a clear yes or no at the end of the quarter.

A number, a date, and a tangible thing that you can point to and say, "Done".

Why Even Perfectly Written Rocks Fail Without Enforcement

Goal Quality Isn't What Determines Completion

Having the right EOS SMART Rock is a good start, but it's only half the battle. Research on goal implementation has revealed an interesting fact: it's not the quality of the goal that matters, it's the quality of the implementation. What actually determines whether someone gets it done is whether another person is checking in on them.

The 25% vs 95% Study That Changes Everything

The accountability multiplier (ASTD 2015)

When people wrote goals but never revisited them, they finished about 25% of the time. When they pledged to someone else and established regular check-ins, that figure rose to 95%.

A 2015 study by the American Society of Training and Development confirmed this with facts and figures. When people wrote goals but never revisited them, they finished about 25% of the time. However, when they pledged to someone else and established regular check-ins, that figure rose to 95%. That's a huge gap, and it's all about accountability.

Why the L10 Meeting Is Supposed to Close the Gap

The Level 10 Meeting is supposed to be the accountability moment in EOS. It is where Rocks are looked at, and people are called to account for their progress. But here's the problem: a lot of teams turn this into a quick checkbox. When someone says "on track," everyone nods, and you move on. No one asks what really happened that week. No one takes the time to examine the obstacles.

The 60-Second Update That Tells You Nothing Is Working

Consider this: If it takes less than 60 seconds to update your Rock, and no one ever asks for an "on track" answer when that Rock hasn't moved in three weeks, something is broken. But the issue isn't how the Rock was written. The problem is that no one is being held accountable.

Rock Hardening: The Collaborative Process Most Teams Skip

Why 10 Minutes Now Saves a Whole Quarter Later

Rock hardening is essentially a "stress test" of your Rocks before the quarter even begins. Most teams avoid this step as it seems like additional work that slows them down. Skipping it actually costs you way more time later. It takes 10 minutes to catch a weak Rock before the quarter begins. If you break one in Week 8, you lose the whole quarter.

Rock Hardening The 3-Question Stress Test

Question 1: Can the Owner Do This by Themselves?

So how does it work? You ask three simple questions for each Rock on your list.

First question: Can the owner do this by themselves? If they require another person's approval, budget or sign-off to proceed, then that's a problem. They don't truly "own" it yet.

Question 2: Are There Hidden Dependencies?

Second question: Are there hidden dependencies? Perhaps the Rock needs another project to be completed first, or a hire that hasn't occurred yet. If you don't bring these hidden blockers to the surface now, they will quietly kill progress.

Question 3: Is the Finish Line Clear Enough?

Third question: Is the finish line clear enough? If you read the Rock out loud and two people picture two different outcomes, it's too vague. A good Rock should have a definition of "done" that everyone on the team would agree on.

If Any Answer Is No, Rewrite Right There

If a Rock answers any of these three questions negatively, do not proceed. Rewrite it right there, before the quarter starts. A few minutes of honest conversation upfront will save your team from a very frustrating quarter-end scramble.

The 3 Hardening Questions at a Glance

#	Question	If the answer is no…
1	Can the owner do this by themselves?	They don't truly own it. Approval/budget/sign-off requirements are blockers in disguise.
2	Are there hidden dependencies?	Surface them now or they will quietly kill progress mid-quarter.
3	Is the finish line clear enough?	If two people read it and picture different outcomes, it's too vague rewrite it.

From SMART Rocks to Completed Rocks: The Execution Gap

What the Execution Gap Actually Is

There's a big difference between writing a great Rock and actually finishing it. That gap is known as the execution gap, and it shows in pretty much every team that fails to follow through.

The 3 Habits That Close the Gap

Closing that gap comes down to three simple habits. First, track progress where everyone can see it, every single week. Secondly, have a real conversation with the owner as soon as a Rock begins to fall behind. Thirdly, don't let your team get away with half-truths, such as "it's in progress" or "almost there." Demand clarity.

Writing Isn't Enough You Need the Hard Talk in Week 7

It is a good start to have your EOS SMART Rocks written the right way, but writing alone won't get you across the finish line. The teams crushing their goals completing 80% or more of their Rocks each quarter aren't just skilled at writing goals. They're happy to have the hard talk in Week 7 when it's clear things are going sideways.

Why "On Track" Lasts Until the Final Week

That's when most teams shy away. That avoidance is why so many Rocks are at "on track" until the final week and then they're not.

How the Best Teams Treat Every Quarter

The best teams treat every quarter like it counts. They show up, speak up, and hold one another accountable, rather than waiting for it to all fall apart first.

The Bottom Line

Writing alone won't get you across the finish line. The teams crushing their goals are happy to have the hard talk in Week 7.