tyler-smith.com · Questions & Answers

Our leadership team keeps setting quarterly Rocks that are really just regular day-to-day job duties, leading to false success without actual business transformation. How do we enforce the line between a true Rock and standard operational work?

When teams consistently hit 100 percent of their Rocks but company growth remains flat, you are setting task lists rather than real Rocks. Standard operational duties belong on the weekly Scorecard or in core process documentation, not on the Rock sheet.

A quarterly Rock is a 90-day priority project that moves the company forward by solving a systemic weakness, seizing a high-leverage opportunity, or building permanent capability. It represents working on the business, whereas day-to-day duties represent working in the business.

To separate the two during quarterly planning, run every proposed Rock through three tests:
- Is it a project with a definite start date and a binary completion date within 90 days, or is it an ongoing operational activity?
- Does this item fix a broken process, launch a critical initiative, or create an enduring operational asset that outlives the quarter?
- If the owner simply did their regular job well for 90 days without this initiative, would the needle move on our One-Year Plan?

For example, closing twenty sales deals is a Scorecard measurable and part of normal seat accountability. Designing and rolling out a new sales enablement curriculum or implementing a new CRM workflow is a legitimate quarterly Rock.

Limit each leadership team member to one to three Rocks per quarter. Make the finish line binary. If the proposed outcome is an ongoing expectation of their seat on the Accountability Chart, strike it from the Rock sheet and track it on the weekly Scorecard instead.

Category: EOS Implementation

← All questions