Rocks That Never Finish: Telling a Capacity Problem From a Clarity Problem

Two quarters in, a familiar conversation arrives. Rock completion is low, the same names keep missing, and the leadership team wants to know whether the problem is the framework or the people.

It is usually neither. Rocks fail for two causes that look identical from outside and require opposite responses.

Clarity failure. The priority was never defined well enough to be finished. Nobody knows what done looks like, so the work never converges.

Capacity failure. The priority was perfectly clear, and the person who owns it does not have the hours, the authority, or the attention to do it.

Getting this wrong is costly. The default response to a missed priority is more accountability pressure: more check-ins, more visible tracking, a firmer conversation. That is the right treatment for a clarity failure, where attention forces definition. It is the wrong treatment for a capacity failure, where it adds reporting overhead to someone already out of hours, and where the usual outcome is that a good person starts managing your perception of the work instead of doing it.

The forty-five day question

Mid-quarter, ask the owner of a struggling Rock one question, in a one-to-one, with no audience:

"What is the next physical action on this, and when is it on your calendar?"

The answers sort almost perfectly.

Clarity failure sounds like: "I need to sit down and think about the approach." "I've been waiting to hear back from a few people." "I'm not sure whether this includes the west territory." The person cannot name a next action because the outcome is undefined. Adding hours would not help. They would spend them in the same fog.

Capacity failure sounds like: "I need to write the spec, it takes about six hours, and I have not had a six-hour block since the second week of the quarter." Precise action, precise estimate, no time. This person needs the block protected, or something taken off them.

The useful property of the question is that it is diagnostic rather than accusatory, so people answer it honestly. It is not a request for a status update.

What clarity failure actually looks like on paper

Look at the written Rock. The problems are usually visible without talking to anyone.

It is a theme, not an outcome. "Improve customer experience." There is no state of the world at which that is finished. Rewrite it as a finished condition with a number: "Post-service survey running on every completed job, with 30 days of responses collected and a baseline score reported."

It has two owners. A Rock owned by two people is owned by neither. One name, always. The second person can be on the work; they cannot be on the Rock.

Done is not defined. If two people on the leadership team would judge completion differently, it is undefined. Quickest test when setting it: ask two people to describe what they will see on the last day of the quarter. If the descriptions differ, fix it now.

It is really a year-long project. "Implement the new ERP" is not a ninety-day outcome. The Rock is the ninety-day slice, with a completion state real on its own: "Vendor selected, contract signed, implementation plan approved with dates." The slice has to be genuinely finishable, not "phase one, mostly."

It depends on someone outside the room. If completion requires a customer to sign, a vendor to deliver, or a regulator to respond, the owner does not control the outcome. Rewrite it around what they do control.

What capacity failure actually looks like

Too many Rocks. The guidance is three to seven, and for most people carrying a full functional role, three is already ambitious. If the leadership team has thirty Rocks between six people, it has not prioritized, it has catalogued.

All the Rocks land in one function. Count them by seat. If four of seven sit with operations, operations will miss and it will look like an operations performance problem. It is a planning problem, and it was visible the day the Rocks were set.

The owner holds two seats. Common in growing companies. One person is both the sales leader and the de facto marketing leader, carries Rocks for both, and the Rocks for the seat they are less comfortable in are the ones that slip. Every time. Which Rock gets dropped is an excellent map of which seat someone is actually in.

The person is in the wrong seat. Capacity in the right-seat sense is not about hours. It is whether someone has the mental, emotional, and time capacity for the role. Someone excellent but stretched past their capacity in that seat will miss Rocks indefinitely, and prioritization does not fix it. This is the diagnosis teams avoid longest.

The work is not on a calendar. A Rock with no time blocked for it is a hope. If the honest answer to "when is it scheduled" is "whenever I get a gap," it will not finish, because the gap does not arrive.

What to do mid-quarter

Kill Rocks rather than carrying dead ones. If it is week seven and a Rock will not finish, say so in the weekly meeting and remove it. Dead Rocks reported as on track for five more weeks corrupt the system, because after one quarter of that nobody believes any status. Killing a Rock should be unremarkable, and how leadership handles the first one decides whether anyone ever does it again.

Change "on track" to mean something. On track means the owner still expects to complete by the end of the quarter. It does not mean progress was made. That change alone usually surfaces two or three quietly failing Rocks by week four rather than week twelve.

Put one milestone on the weekly scorecard. For a Rock that keeps drifting, add a weekly countable line: drafts completed, sites surveyed, interviews held. A ninety-day horizon is long enough to hide in, and a weekly number removes the hiding place without adding a meeting.

Protect the block. For a genuine capacity failure the intervention is calendar surgery, not encouragement. Find the hours, take something else away, or accept that the Rock moves to next quarter and say so out loud.

The pattern that means something structural

One person missing one Rock is noise. Watch for these instead:

• The same seat misses in three consecutive quarters. That is a seat problem, not a person having a bad quarter.
• Rock completion drops sharply the quarter after a growth spurt. Capacity was consumed by volume and the plan did not account for it.
• Everyone's Rocks finish in the last two weeks. The team is treating the quarter as a deadline rather than a plan, which usually survives until the quarter you are also dealing with something unexpected.
• Rocks finish but nothing changes. The Rocks were not connected to the annual plan, and you are executing efficiently in a direction nobody chose.

Two honest caveats

Completing every Rock every quarter is not the goal, and is arguably a sign the priorities are too easy. The framework's own guidance treats roughly eighty percent completion as a healthy team. A team at one hundred percent for three quarters running is probably under-reaching.

And sometimes the Rocks are fine and the business is not. In a cash crisis, or the quarter a major customer leaves, priorities should be rewritten rather than defended. A team grimly executing a plan the quarter has already invalidated is following process rather than thinking.

Industry shapes which failure dominates. In seasonal work, pronounced for trades businesses and construction companies, a Rock set for the busiest quarter of the year is a capacity failure scheduled in advance. In professional services, where we work with a number of financial firms, clarity failure is more common, because the leadership team is made of producers whose client work has an unambiguous definition of done and whose internal projects do not.

If your Rocks keep missing and you are not sure which is happening, tell us what the last two quarters looked like, including who owned what. The pattern is usually obvious from outside.