A Rock Can Be On Track and Still Mean Different Things

The leadership team reviews its quarterly Rocks during the weekly Level 10 Meeting.
Each owner provides an update. The milestones are progressing, and a cross-functional Rock remains on track.
The more revealing test comes when that Rock reaches a downstream team and someone has to make a decision that the status update does not describe.
The Sales leader understands the priority as accelerating customer onboarding. Operations interprets it as reducing internal processing time. The service team believes success means maintaining quality while handling increased volume.
These interpretations are not necessarily contradictory. Each team is working toward a legitimate outcome.
The difficulty emerges when the teams must make a trade-off.
If moving faster requires changing an approval process, who makes that decision? If capacity becomes constrained, which result takes precedence?
A Rock can have a clear owner and a positive status while leaving important questions about execution unresolved.
For companies running on EOS, that is a useful leadership question to examine between Level 10 Meetings.
EOS Creates Accountability. Handoffs Determine How It Is Applied.
The Entrepreneurial Operating System provides a structured rhythm for moving organizational priorities into action.
Rocks establish important 90-day priorities. The Accountability Chart clarifies roles. Weekly Level 10 Meetings create a recurring opportunity to review progress and address issues through IDS: Identify, Discuss, and Solve.
These mechanisms help leadership teams maintain focus and accountability.
Their effectiveness also depends on the decisions people make between meetings.
A Rock may begin with a clearly defined outcome, but delivering it often requires several managers and functions to coordinate.
Each person must interpret what the priority means for their responsibilities, available resources, and authority to make trade-offs.
That interpretation becomes particularly important when a Rock crosses departmental boundaries.
The Rock owner may understand the intended result perfectly. A downstream manager may have a different understanding of which actions are authorized to achieve it.
Both can accurately report progress against their assigned work while working from different assumptions.
The distinction is between tracking a priority and maintaining shared understanding of how it should be executed.
The distinction matters because a Rock status and a handoff answer different questions. Status tells the leadership team whether agreed milestones appear to be progressing. A handoff reveals whether the next person can make the choices necessary to deliver the intended result. In a cross-functional Rock, it is possible for both views to be accurate at the same time: the owner is meeting milestones while a downstream team is operating with an unresolved assumption about quality, speed or decision authority.

Why This Can Happen in a Well-Run EOS Company
Gallup's August 2026 U.S. employee data found that only 19% of employees strongly agreed that senior leaders set clear priorities for their organization.
This is a broad U.S. workforce finding, not a measurement of EOS users or evidence that a particular company's Rocks lack clarity.
That workforce finding makes the narrower case for checking that a stated priority still has a usable meaning beyond the people who set it.
Even a well-led organization cannot anticipate every exception when quarterly priorities are established.
Customer requirements change. Capacity becomes constrained. Departments encounter competing commitments.
Managers must use judgment within those conditions.
The question is whether they share a sufficiently clear understanding of the outcome, the authority available to them, and the point at which a decision belongs in IDS.
A difference in interpretation does not automatically signal weak accountability. It may simply identify a decision boundary that was never made explicit.
The Three-Question Rock Handoff Check
Choose one current Rock that requires work from more than one function.
Ask the Rock owner and a downstream team leader to answer three questions independently.
What result matters most this quarter?
Ask both people to describe what successful completion means.
Look beyond the Rock's title. What specific outcome must be achieved? Which conditions must remain intact?
One person may emphasize completing a deliverable. Another may emphasize achieving the intended operational result.
If their definitions differ, clarify the expected outcome before discussing task progress.
Who makes the next trade-off?
Identify a realistic decision the teams may face while completing the Rock.
For example, if faster delivery requires additional resources or changes to an established process, who has authority to approve that choice?
The Rock owner may assume a functional leader can decide. The functional leader may believe approval must come from the executive team.
Make that boundary explicit.
What would trigger an IDS discussion?
Ask which conditions should move the issue into the Level 10 Meeting's IDS process.
A routine operational adjustment may be resolved locally. A significant conflict between departments, an unresolved constraint, or a threat to the Rock's intended outcome may warrant broader leadership attention.
The goal is to identify the escalation point before uncertainty creates unnecessary delay.

Compare the Answers Before the Next Level 10
Allow five minutes for independent responses and another five to compare them.
If the answers align, the handoff has a useful indication of shared understanding.
If they differ, identify the most consequential ambiguity.
Agree on one clarification, document the responsible decision-maker, and communicate the rule to the people involved.
If the issue needs leadership resolution, add it to the appropriate Issues List for IDS.
The next Level 10 can then focus on a specific decision instead of reopening a broad discussion about the Rock.
This exercise requires no new software, proprietary score, or additional management framework.
When an ambiguity genuinely belongs in IDS, frame it as a decision to be made. Instead of adding a general issue such as 'onboarding alignment,' the Rock owner can specify the conflicting interpretations, their consequence for the Rock and the approval boundary leadership needs to settle. That preparation helps the Level 10 Meeting resolve the real constraint. When the owner and the downstream leader can agree on the rule themselves, there is no benefit in moving the decision to the entire leadership team.
Keep the Rock Review Focused on What Matters
EOS already provides a disciplined place for reviewing progress and solving issues.
The handoff check is intended to support that process, not add another reporting requirement.
An on-track Rock does not automatically need additional investigation. Nor should every difference in managerial judgment become a leadership issue.
Different functions may legitimately make different decisions when their responsibilities and constraints differ.
The important distinction is whether those differences reflect agreed decision rules or unresolved assumptions.
Where the boundaries are clear, managers should retain the authority to act.
Where they are unclear, a brief clarification can help preserve the Rock's original intent.
Use the check selectively. A green status does not invite suspicion, and teams should not be asked to defend every routine judgment. Prioritize Rocks with material cross-functional dependencies, repeated exceptions or a decision that could change the intended outcome. The purpose is to protect the meaning of the commitment without turning EOS into a parallel audit process.
An Additional View Between Level 10 Meetings
The handoff exercise addresses one Rock. Leadership may also want to understand whether similar questions about priorities, decision ownership, or coordination recur across teams.
Baryons is designed to complement existing operating frameworks, including EOS, through private, company-grounded individual guidance and privacy-protected aggregate organizational signals.
Individuals can use a private Baryon to reflect on work-related decisions and priorities within approved company context.
Separately, anonymized and aggregated Team Resonance Insights provide leadership with broader organizational patterns rather than individual conversation transcripts or attributable employee comments.
These signals can offer additional context for management discussions about clarity and coordination.
Privacy safeguards, aggregation rules, and reporting access should be reviewed as part of any organizational evaluation.
Baryons does not replace Rocks, Level 10 Meetings, IDS, or the accountability structure already established through EOS. Leaders remain responsible for interpreting the information and deciding what action is appropriate.
One Question for Your Next Level 10 Meeting
If the owner of our most important cross-functional Rock and the next team responsible for delivering it explained what success means, who can make the next trade-off, and when to escalate, would their answers agree?
Choose one Rock and compare the answers.
For EOS organizations interested in understanding recurring leadership-clarity and coordination patterns between meetings, Baryons offers a privacy-conscious way to complement established operating practices with individual guidance and aggregated organizational insight.
Sources
Gallup: Leadership & Management Indicators, August 2026 U.S. Employee Data
EOS Worldwide: How Does an EOS Level 10 Meeting Work?
EOS Worldwide: What to Do When Your Rocks Are in Danger
More articles

The Strategy Was Clear. So Why Did Execution Drift?
Quarterly alignment around a 90-day priority does not settle every trade-off needed to deliver it. This article gives Scaling Up teams a three-question check to surface different interpretations between functions while the quarter is still recoverable.

A Leadership Framework Should Reduce Decisions Returning to the Owner
Leadership frameworks build shared language, but owners still field the trade-offs nobody was authorized to make. This article offers a ten-minute, three-person priority check that turns one unclear decision into a rule managers can use.

Between Leadership Sessions, Managers Still Have to Make the Call
Leadership development builds shared principles, but daily decisions test them. This article helps mid-market executives see whether managers apply the same priorities consistently, and whether a gap calls for coaching or clearer organizational rules.