One of our department heads consistently hits their ongoing weekly Scorecard measurables but drops their cross-functional quarterly Rocks, claiming client emergencies took priority. How do we address an executive who treats strategic Rocks as optional side projects?

Question

Tyler Smith · Accepted Answer

An executive who hits their weekly Scorecard measurables but routinely drops their quarterly Rocks is confusing activity with leadership. Scorecard metrics track the baseline pulse of daily operations. They show that the engine is running. Rocks represent strategic priorities designed to move the business forward, build systems, and prepare the company for long-term scale and an eventual clean exit.

When a leader treats Rocks as optional side projects, they are operating as a functional supervisor rather than an enterprise leader. Claiming that client emergencies or operational brushfires prevented them from completing a ninety-day priority is an admission of poor time management and lack of delegation.

Address this during your weekly Level 10 Meeting. When a Rock goes off-track, it must immediately be placed on the Issues List for IDS. Dig into the root cause. Did the leader set an unrealistic scope? Did they fail to delegate day-to-day tasks to their team? Or did they simply prioritize urgent tactical fires over important strategic milestones?

If the leader repeatedly drops Rocks quarter after quarter, evaluate them using GWC. An executive who lacks the capacity to balance daily operational rhythms with strategic projects cannot remain in a top-tier seat. Explain clearly that hitting eighty percent of company Rocks each quarter is the baseline expectation for leadership. If their functional seat is genuinely so overwhelmed by operational emergencies that they cannot execute strategic initiatives, the solution is not dropping the Rocks. The solution is using the Accountability Chart to hire or delegate operational tasks so they have the capacity to lead.