Straight to the Point
- Rocks should build great businesses, not just generate green checkmarks.
- Black-and-white Rock completion creates terrible incentives: sandbagging, playing it safe, hiding problems, and making bad decisions just to get a Rock done.
- Separate execution from outcomes. Someone can do an outstanding job and still miss a result outside their control.
- Build living 13-week plans, and change, postpone, or cancel a Rock when it makes sense. That’s a leadership team decision, not the Rock owner’s alone.
- Accountability still matters: do the work, raise problems early, involve the team, and decide what’s best for the business.
I love Rocks. I love the clarity they bring and having a team focused on the handful of things that will make the biggest difference to their business over the next 13 weeks.
But something about how we measure Rock success drives me nuts.
We confuse achieving an outcome with executing a great plan.
And when we do that, we can accidentally punish great execution, reward bad decisions, and teach our teams to play it safe.
Yes, this is grey. It’s closer to OKRs than to traditional Rocks, and that’s intentional. Black and white doesn’t make sense when you don’t know what you don’t know. Agile does.
What’s Wrong with Black-and-White Rocks?
Black-and-white Rocks can punish exactly the decisions we want leaders to make.
Imagine your IT leader has a Rock: Complete the ERP rollout by the end of the quarter.
The team works hard, hits their milestones, and everything looks good. Then, in Week 10, testing uncovers a critical issue. Going live could create serious problems for the business.
So the IT leader makes the right call. They delay the launch.
Failed Rock.
They just protected the business from a potentially disastrous implementation. They made exactly the decision we’d want a great leader to make.
The ERP example is extreme, but I’ve seen variations of it dozens of times.
Now imagine that Rock completion is part of how we evaluate that leader’s performance. Maybe it even affects their bonus.
What behaviour are we encouraging? Do what’s right for the business, or do whatever it takes to get the Rock across the finish line?
That’s a pretty dangerous choice to put in front of someone.
Why Does Rock Completion Create the Wrong Behaviours?
People respond to how they’re measured. If Rock completion becomes the measure of individual success, don’t be surprised when people start playing the game.
They sandbag their Rocks, choosing things they’re confident they can complete. They avoid ambitious projects with uncertain outcomes. They negotiate easier goals, protect their completion rates, and become reluctant to take risks.
And sometimes, they make bad decisions because the price of failure is too high.
Think about HR with a Rock to hire a new Operations Leader.
They do the postings, screen candidates, conduct interviews, and build a shortlist. But nobody is quite right. Or the hiring manager is overwhelmed and won’t make a decision, even after HR raises the issue with the leadership team.
The quarter ends without a hire.
Failed Rock.
Yet HR may have done everything reasonably within their control, including escalating the problem. The business didn’t get the outcome it wanted, but that doesn’t mean HR failed.
Now imagine they hire someone they know isn’t quite right, just to complete the Rock.
Green checkmark. Terrible decision.
We’ve confused accountability for results with accountability for performance.
And they aren’t the same thing.
What Does a Great Rock Look Like?
A great Rock states an intention, defines what success looks like, and tracks the activities you can actually drive.
Let’s use sales as an example. A sales leader creates a Rock:
“Sign up five referral partners and generate five referrals this quarter.”
Nice and measurable. But is it a good Rock?
Maybe.
Have they done this before? Do they know how many outreach attempts produce a conversation, how many conversations produce a partner, or how long it takes a new partner to generate a referral?
If not, they’ve just committed to a bunch of assumptions.
Maybe 50 outreaches will generate five partners. Maybe it’ll take 500. Maybe their offer is fantastic. Maybe nobody wants it.
They don’t know yet. And that’s okay.
The problem isn’t uncertainty. It’s pretending uncertainty doesn’t exist.
I’d rather see the Rock written as:
I intend to increase lead generation through referral partners.
Now we define what success looks like. We want five new partners and five qualified referrals. Fantastic. Those are the business outcomes we’re shooting for.
But we’re also tracking the activities that should get us there: outreach, conversations, and partners signed up.
Then we build the 13-week plan.
What Is a Living 13-Week Plan?
A living 13-week plan focuses on executing and learning, not predicting exactly what will happen every week.
Instead of forecasting how many partners and referrals we’ll have each week, we focus on doing the work and learning from it. Our initial plan might be simple:
- Conduct ten outreach attempts every week.
- Track conversations, partners, and referrals.
- Every second week, evaluate what’s working and what isn’t.
- Adjust the remaining 13-week plan based on what we discover.
After two weeks, we’ve made 20 outreaches and had zero conversations.
Uh-oh.
Is the messaging wrong? Wrong audience? Bad offer? Wrong approach entirely?
Let’s figure it out, change something, and try again.
Maybe we double the outreach. Maybe we completely change the offer. Maybe we discover that referral partners aren’t a viable channel for this business.
I’d much rather discover that in Week 3 than at the end of the quarter.
Can You Change a Rock Mid-Quarter?
Yes. Rocks are malleable, but the leadership team makes the call, not the Rock owner alone.
Rocks aren’t set in stone. (Ha, pun intended.) Just like every other plan in your business, your annual plan, quarterly plan, and 13-week execution plan are all living plans. They’re based on what you know today, and what you know tomorrow might change everything.
A Rock might need to be adjusted. It might be postponed. It might turn out that the original intention was completely wrong, or that the outcome simply isn’t feasible.
Who knows?
But here’s the important part: you don’t get to change your Rock on your own.
Your Rocks are commitments to the team, and changes need to be discussed with the team.
You bring forward what you’ve learned, explain what’s changed, and make a recommendation. Then the leadership team decides whether changing, postponing, or cancelling the Rock makes the most sense and delivers the most value to the business.
If the team agrees, make the change. Plain and simple.
That’s not an escape hatch. That’s good leadership.
And it’s why we have weekly meetings. Problems get raised, assumptions get challenged, and decisions get made before we waste another six weeks heading in the wrong direction.
And change it in Week 12, you’re toast either way. A change that late tells me you didn’t learn fast and adjust. It’s sandbagging for failure.
A Rock should be stronger than a line in the sand, but it should never become a prison.
How Do You Keep People Accountable Without Black-and-White Rocks?
You hold people accountable for how they perform and respond, not only for whether the outcome landed.
Here’s the pushback I expect. “If we don’t hold people accountable for completing their Rocks, aren’t we just rewarding activity?”
Nope. Not even close.
Activity without results should absolutely raise questions.
That’s why we have weekly leadership meetings. In our Momentum Framework, the weekly meeting is where we check progress, identify problems, and use the collective intelligence of the team to figure out what to do next.
Imagine that HR leader again. At the end of the quarter, they tell us they couldn’t hire the Operations Leader because there weren’t any qualified candidates.
Okay. What did you do about it?
“We changed the posting, adjusted the salary, and tried different recruitment channels.”
Did that work?
“No.”
Did you bring the problem to the leadership team?
“No.”
Then you failed.
Not because you didn’t hire someone. Because you knew things weren’t working and didn’t bring the problem forward.
That’s poor execution.
Now, if they did raise it, worked through the options, made adjustments, and the leadership team collectively decided not to compromise on the quality of the hire? Very different conversation. The Rock didn’t achieve its original outcome, but the person may have executed brilliantly.
This is how I coach on Rock completion. “You didn’t meet this metric. What did you do? Did you talk to the team? Did you reset your 13-week plan to the new reality?” If not, it failed. If yes, I turn to the team: “Do you think they succeeded?”
And no, this isn’t a popularity vote. The team isn’t deciding whether they like the person or feel sorry for them. They’re looking back and deciding one thing: did this Rock achieve what we intended?
Yes, this system can be gamed. Making sure it isn’t is the coach’s job, the “game master’s” job.
Accountability means taking ownership, doing the work, identifying problems early, adapting, and involving the team when you need help.
It doesn’t mean blindly delivering an outcome regardless of what happens along the way.
Why Do Faster Feedback Loops Matter?
The faster you learn what works, the faster you get results. Faster, not sloppier.
One of the things I push hardest with leadership teams is the need to think and move faster. Do something, see what happens, learn, and adjust. That’s the OODA loop: Observe, Orient, Decide, Act. We want that loop running constantly.
We don’t want people spending thirteen weeks following a plan that’s clearly not working. We want them discovering problems early, making decisions, and getting on with it.
And that requires three competencies I believe every organization needs to develop: speed, ambiguity, and autonomy.
People need to get comfortable making decisions without perfect information, moving quickly, and taking ownership of the results.
You don’t develop those competencies by punishing people every time an uncertain outcome doesn’t materialize. You develop them by challenging people to do great things, supporting them when things get difficult, and holding them accountable for how they respond.
What Are Rocks Really For?
Rocks exist to build clarity, confidence, and a better business, not impressive completion percentages.
We don’t do quarterly planning because we want beautiful plans or high Rock completion rates. We do it because we want three things:
- Clarity. Everyone knows what’s important and what we’re trying to accomplish.
- Confidence. People believe they can tackle big challenges, solve problems, and do awesome things.
- A better business. We’re making meaningful improvements and getting things done.
And along the way, we’re building a stronger, smarter, more capable team. That’s the real win.
So when someone takes on an ambitious Rock and fails, what does that tell you?
And when someone takes on an ambitious Rock and adjusts as they go?
A team that takes on challenging Rocks, learns quickly, makes great decisions, and occasionally misses an outcome is far more valuable than a team that consistently completes easy Rocks.
Of course we want results. Of course we want to complete our Rocks. But we also want people who have the confidence to tackle things they haven’t figured out yet.
Fail fast. Fail often. Learn faster.
Make Your Rocks Rock
The next time you’re building your quarterly plan, think beyond whether a Rock can be marked complete.
What’s the intention? What business outcome are we trying to create? What activities can we control, and what assumptions do we need to test?
Build the 13-week plan, execute it, measure what’s happening, and adjust as you learn. When things aren’t working, raise the issue and use your team to solve it.
And if the Rock itself needs to change, make that decision together based on what’s best for the business.
When the quarter ends, don’t just ask whether the Rock was completed. Ask whether the person executed well, made good decisions, and helped move the business forward.
Because a completed Rock isn’t always a success, and an incomplete Rock isn’t always a failure.
The goal isn’t to get more green checkmarks.
It’s to build great businesses with great people.
And that’s how you build Momentum.
