Why Quarterly Rocks Fail: Execution Pitfalls Every Leadership Team Hits in Week 6

Your leadership team left the quarterly planning session fired up. The whiteboard was full, the Rocks were set, everyone committed. Six weeks later, half the Rocks are off track, two haven’t been touched, and nobody wants to talk about it in the weekly meeting.

This pattern is so common that I’ve started calling it “the Week 6 wall.” It happens in $8M professional services firms, $20M construction companies, and $50M SaaS businesses alike. The planning session felt productive. The execution didn’t follow.

If you’re running on EOS or any business operating system, Rocks are supposed to be the mechanism that translates vision into quarterly traction. When they fail, the problem is almost never the concept itself. It’s how the team sets, owns, and tracks them.

What Quarterly Rocks Are (and What They’re Not)

Rocks are the three to seven most important priorities your company must accomplish in the next 90 days to stay on track toward your annual goals. The term comes from Stephen Covey’s analogy: if you fill the jar with sand first (daily tasks, email, meetings), there’s no room for the big rocks. You have to drop the rocks in first.

In the EOS framework, Rocks live at two levels: company Rocks (owned by the leadership team collectively) and individual Rocks (owned by one person who is accountable for completion). Each Rock should be specific, measurable, and achievable within the quarter.

What Rocks are NOT: annual goals chopped into four pieces. They’re not aspirations, and they’re not ongoing responsibilities repackaged with a 90-day label. “Improve customer satisfaction” is not a Rock. “Implement a post-project survey for all clients completing engagements over $25K, with a 70% response rate by end of quarter” is a Rock.

Why Rocks Fail: The Five Execution Pitfalls

I’ve facilitated or reviewed hundreds of quarterly planning sessions across companies ranging from 25 to 200 employees. The same failure patterns appear regardless of industry, revenue, or how long the team has been running on a business operating system. Here are the five that account for nearly every stalled Rock I’ve encountered.

1. Too Many Rocks, Not Enough Focus

The most common failure. A leadership team sets 12 company Rocks and each individual carries five or six personal Rocks. By week three, everyone is stretched. By week six, the team is quietly triaging which Rocks they’ll actually finish and which they’ll explain away at the quarterly review.

The discipline is counterintuitive: fewer Rocks produce more results. Three to seven at the company level. One to three per person. If your leadership team pushes back on this limit, that’s a sign they haven’t yet learned to prioritize, which is exactly the muscle that Rocks are designed to build.

2. Vague Rocks That Can’t Be Scored

A Rock must be binary at the end of the quarter: done or not done. If your team argues about whether a Rock was completed, it was written poorly. “Improve our sales process” will generate a 15-minute debate in the quarterly review about whether it’s 60% done or 80% done. That debate is wasted time.

The fix: make every Rock SMART (Specific, Measurable, Attainable, Realistic, Timely). A well-written Rock has a clear deliverable. “Document the five-step sales process, train all account executives, and run two full cycles using the new process” leaves no room for interpretation. Tools like Ninety.io help teams track Rock completion status in real time, which eliminates the ambiguity that kills execution.

3. Shared Ownership (No Single Throat to Choke)

When a Rock is assigned to two people, it belongs to neither. I’ve watched this play out dozens of times: both owners assume the other is driving, neither builds a plan, and the Rock drifts until week eight when someone finally asks, “Where are we on this?”

Every Rock gets one owner. That doesn’t mean one person does all the work. It means one person is accountable for the outcome, builds the project plan, and reports status in the weekly Level 10 meeting. If a Rock requires cross-functional effort, the owner coordinates it. If it requires resources they don’t control, they escalate early, not in week 10.

4. No Milestones Between Week 1 and Week 13

This is where the Week 6 wall comes from. The team sets Rocks at the quarterly planning session and then doesn’t break them into intermediate milestones. For 13 weeks, the only checkpoint is the weekly “on track / off track” report in the Level 10 meeting. That binary status update masks the real problem: the Rock owner hasn’t built a plan with discrete steps and deadlines.

The solution is milestones. Every Rock should have three to five milestones mapped to specific weeks. “By week 4, complete vendor evaluation. By week 7, sign contract. By week 10, begin implementation. By week 12, first cohort trained.” Now the weekly status report means something. “Off track” at week 6 triggers a specific conversation about which milestone slipped and what needs to change.

5. Rocks That Aren’t Connected to the Vision

Some Rocks fail because they shouldn’t have been Rocks in the first place. They’re pet projects, inherited commitments, or reactive responses to last quarter’s fire drill. A real Rock flows directly from the company’s one-year plan, which flows from the three-year picture, which flows from the 10-year target.

If a proposed Rock doesn’t clearly advance the company’s annual goals, it’s either a to-do (handle it in the weekly meeting) or a distraction (kill it). The Vision/Traction Organizer is the tool that makes this alignment visible. If you can’t point to the V/TO and show how a Rock connects, it doesn’t belong on the list.

Real-World Application: How One Team Broke Through the Week 6 Wall

I worked with a 45-person professional services firm running on EOS. They had been setting Rocks for six quarters and completing about 60% of them. The CEO was frustrated. “We’re disciplined about the process,” she told me. “We set them, we review them weekly. They just don’t get done.”

When I sat in on their quarterly planning session, the problem was obvious within the first hour. The leadership team of six was setting 14 company Rocks per quarter. Each leader carried four to five individual Rocks on top of that. They were drowning in priorities, which meant they had no priorities at all.

We cut to five company Rocks. Each leader got two individual Rocks, maximum. The pushback was immediate: “But we need to do all of these things.” My response: “You haven’t been doing all of these things. You’ve been starting all of them and finishing 60%. Let’s start fewer and finish 90%.”

The next quarter, they completed 80% of their Rocks. The quarter after that, 90%. The discipline wasn’t about working harder. It was about choosing less and executing more.

A second pattern I see in $15M to $30M companies: the leadership team writes clear Rocks but never builds milestones. A director named Priya owned a Rock to “launch the new client onboarding process by end of Q2.” She reported “on track” in every Level 10 meeting for seven weeks. In week eight, she admitted she hadn’t started because two other priorities kept jumping the line. There was no milestone at week four to catch the drift.

We rebuilt that Rock with four milestones, each with a specific deliverable and a date. The next quarter, Priya completed her Rock three days early. The milestones didn’t just track progress; they created urgency at regular intervals instead of one cliff at week 13.

Signs Your Rocks Are Failing (Even If Nobody’s Saying It)

You don’t need to wait until the quarterly review to know your Rocks are in trouble. Watch for these signals:

• The “on track” report is always on track. If every Rock is green every week for the first six weeks, nobody is being honest. Real execution surfaces obstacles early.
• Rock owners can’t describe their next milestone. If someone owns a Rock but can’t tell you what they’re delivering by the end of next week, the Rock has no plan.
• The same Rock appears two quarters in a row. A rolled Rock is a failed Rock. If it wasn’t important enough to finish, question whether it’s important enough to carry forward.
• Rocks keep getting added mid-quarter. This signals that the leadership team is reacting to fires instead of holding the line on quarterly priorities.
• Weekly meeting Rock updates take less than 30 seconds per person. If the update is “still on track,” with no detail, the tracking isn’t real. A meaningful update references the current milestone and what’s next.
• Leadership team members treat Rocks as “extra work.” Rocks should represent the most important work, not additional work layered on top of an already full plate. If your team sees Rocks as a burden, the priorities are wrong.

How to Get Started: Fix Your Rocks This Quarter

You don’t need to wait for the next quarterly planning session. Start this week:

1. Audit your current Rocks. How many does the company have? How many does each person own? If anyone has more than three, you have a focus problem.
2. Rewrite any vague Rocks. Apply the SMART filter. If you can’t score it as done or not done with zero debate, rewrite it.
3. Add milestones. Every Rock gets three to five intermediate checkpoints with dates. Review these in the weekly Level 10 meeting, not just the on-track/off-track status.
4. Confirm single ownership. If any Rock has two names on it, pick one. That person drives; the other supports.
5. Connect each Rock back to the one-year plan. If you can’t make the connection, drop the Rock and replace it with one that advances the annual goals.

Frequently Asked Questions

How many Rocks should a leadership team set per quarter?

Three to seven company Rocks is the standard range. Individually, each leader should own one to three. Teams that consistently exceed this range complete fewer Rocks overall because attention gets diluted across too many priorities. The discipline is choosing what NOT to do.

What do you do when a Rock is off track at the midpoint of the quarter?

Surface it in the Level 10 meeting using the IDS framework (Identify, Discuss, Solve). Determine whether the Rock needs more resources, a reduced scope, or a different owner. Do not wait until week 12 to have this conversation. The earlier you catch the drift, the more options you have.

Should Rocks carry over if they aren’t completed?

Only if the Rock is still strategically relevant to the one-year plan. A rolled Rock should be the exception, not the pattern. If a Rock rolls more than once, it’s either too large (break it into smaller Rocks), not truly a priority (drop it), or assigned to someone who doesn’t have the capacity or capability to own it (reassign it using the GWC framework).

What’s the difference between a Rock and a to-do?

A Rock is a 90-day priority that moves the company toward its annual and long-term goals. A to-do is a shorter-term action item, usually completable in one to two weeks, that surfaces during the weekly meeting. If something can be done in two weeks, it’s a to-do. If it requires sustained effort over the full quarter, it’s a Rock.

How do you handle Rocks that depend on external factors outside your control?

Build the external dependency into your milestones with buffer time. If a Rock requires a vendor contract, the milestone should be “vendor contract signed by week 4” so that any delay surfaces early. Rocks that are entirely dependent on external factors (waiting on a regulatory decision, for example) probably shouldn’t be Rocks at all. Only set Rocks where your team controls the outcome.