Rocks are one of the simplest and most powerful planning tools for growing companies. They help teams focus, align and make real progress every 90 days. But even though the concept is simple, most teams struggle to execute their Rocks consistently.

The issue is not the framework.
It is the mistakes teams make while setting, owning and reviewing their Rocks.

This article breaks down the most common Rock problems and how to fix each one with clear, practical guidance your team can implement immediately.

Why Rocks Fail in the First Place

Rocks fail for predictable reasons:

• They are vague
• They are too big
• No one owns them
• They are not reviewed weekly
• They are not tied to tasks
• They are set in isolation
• They live in scattered tools
• They compete with too many priorities

When these issues stack up, Rocks lose focus and drift into the background.

But the good news is each mistake is easy to fix with the right structure.

Mistake 1. Setting Too Many Rocks

Most teams try to do too much in one quarter.
When everything is important, nothing gets finished.

The ideal range is 3 to 7 Rocks per team.
More than that spreads your focus too thin and turns Rocks into a wish list rather than a strategic plan.

Fix:
Choose only the priorities that will truly move the company forward.
Say no to everything else.

Mistake 2. Writing Vague or Ambiguous Rocks

Vague Rocks are the fastest way to kill traction.
They lack clarity and do not define what success looks like.

Examples of vague Rocks:

• “Improve marketing”
• “Fix onboarding”
• “Work on sales process”

These cannot be measured or completed.

Fix:
Make Rocks specific, measurable and outcome focused.

Examples of strong Rocks:

• “Launch rebuilt onboarding flow by June 30”
• “Increase demo to close rate from 18 percent to 25 percent”
• “Publish 12 high value content pieces”

Clarity creates momentum.

Mistake 3. Assigning Multiple Owners

When more than one person owns a Rock, no one owns the Rock.
Shared ownership creates confusion, gaps and finger pointing.

Fix:
Assign exactly one owner per Rock.

The owner is responsible for:

• Driving progress
• Removing blockers
• Updating weekly status
• Coordinating supporting tasks

They do not have to do all the work, but they must ensure the outcome.

Mistake 4. Choosing Tasks Instead of Strategic Priorities

Many teams accidentally choose tasks instead of Rocks.

Examples of tasks disguised as Rocks:

• “Update website copy”
• “Fix bug backlog”
• “Write documentation”

These are important, but they are not quarterly priorities by themselves.

Fix:
Choose Rocks that solve problems or move the business forward in a meaningful way.

Examples:

• “Launch new website that increases conversion by 30 percent”
• “Reduce bug backlog by 40 percent to improve reliability”
• “Document top 10 core processes to support scale”

Rocks should be strategic, not tactical.

Mistake 5. Not Breaking Rocks Into Weekly Actions

A Rock without supporting actions is just a vague intention.
Many teams set Rocks but never define how to achieve them.

Fix:
Break each Rock into:

• Key milestones
• Weekly actions
• Clear deadlines

This converts strategic priorities into a predictable execution path.

Wave connects Rocks directly to tasks and meetings so weekly actions never get lost.

Mistake 6. Not Reviewing Rocks Weekly

The single biggest reason Rocks fail is that teams forget about them after the kickoff meeting. Without a weekly review, Rocks drift, momentum fades and deadlines slip.

Fix:
Discuss Rocks every week.

A weekly check in should include:

• On track or off track
• What moved forward
• What is blocked
• What support is needed
• What next step is due

Teams that review Rocks weekly are significantly more likely to complete them according to EOS Worldwide research.

Wave builds this rhythm directly into the weekly meeting flow.

Mistake 7. Setting Rocks Without Considering Capacity

Teams often underestimate the effort required to complete a Rock, especially when they are also running the business. Rocks always compete with daily responsibilities.

Fix:
Be realistic about scope and workload.

Ask:

• Does the owner have the capacity
• Are there dependencies
• Does this Rock conflict with others
• Is it achievable in 90 days

Strong Rocks are ambitious but realistic.

Mistake 8. Storing Rocks in Scattered Places

Rocks get lost when they live in:

• PDFs
• Google Docs
• Whiteboards
• Spreadsheets
• Slack messages

When Rocks are scattered, accountability disappears.

Fix:
Centralize Rocks in one operating system where the whole team sees them every week.

Wave solves this by putting Rocks, tasks, KPIs and meetings in one connected platform that updates automatically.

Mistake 9. Not Connecting Rocks to Scorecards

Rocks without measurable indicators become subjective.
Teams disagree about whether they are on track.

Fix:
Tie Rocks to one or more leading indicators in your scorecard.

Examples:

• Sales Rock → demos booked per week
• Product Rock → features shipped per week
• Retention Rock → active usage percentage

This creates objective visibility across the team.

Mistake 10. Setting Rocks That Do Not Connect to Annual Goals

Some Rocks feel important but do not actually move the company toward its long term plan. These are distractions disguised as priorities.

Fix:
Every Rock should tie directly to:

• An annual goal
• A long term vision
• A strategic milestone

Strong Rocks build toward something meaningful.

How Wave Helps Teams Avoid These Mistakes

Wave was designed to eliminate the friction that causes Rocks to fail.

Wave helps your team:

• Set clear, measurable Rocks
• Assign one owner per priority
• Connect Rocks to tasks
• Tie Rocks to KPIs
• Review Rocks in weekly meetings
• Track progress automatically
• Surface blockers early
• Bring visibility to the entire company

The result is a system where Rocks are not just planned but actually completed.

Quarterly priorities finally become predictable.

Final Thought

Rocks are powerful when set correctly, owned clearly and reviewed consistently. When teams avoid these common mistakes and build a strong quarterly cadence, execution becomes faster, alignment becomes stronger and focus becomes easier.

Great companies are built one quarter at a time.

‍