See where the plan is about to collide with capacity, early enough to change it.
A COO owns the gap between what was decided and what actually ships. The strategy arrives as ambition; delivery happens inside fixed headcount, competing roadmaps, and dependencies nobody owns end to end. The hard part is not setting goals, it is knowing which commitments are already impossible at current capacity, and saying so in week two rather than week eleven. Most missed dates were really a capacity decision made months earlier.
What goes wrong from this seat
Commitments nobody capacity-checked
Quarterly goals get agreed in a room where the roadmap, the hiring plan, and the support load are not on the same page. Every function says yes, because saying no in front of the CEO is expensive. Six weeks in, the same engineers are on the platform migration, the enterprise deal, and the new goal. Nothing was mismanaged; the quarter was oversubscribed on the day it was set.
The dependency with no owner
A goal is assigned to one function, but the work it depends on sits in two others. Marketing owns the launch number and engineering owns the feature; the goal is scored against marketing. The handoff is where the quarter is lost, and nobody is accountable for the handoff. Write the dependency down when the goal is set, with a named owner and a date, or the first real conversation about it happens after it has already slipped.
Green, green, green, red
Status collected as a color from the person doing the work is a confidence report, not a measurement. People stay green while they still believe they can recover, which is rational and almost always too long. A goal that flips from green to red in the last two weeks of a quarter was never green; it was unmeasured. Pair every goal with a number that moves weekly and the color stops mattering.
Improvement work loses to the day job
Operations runs on urgency, and urgency always has a name attached: a customer, an outage, a deadline. Goal work has only a quarter-end attached, so it yields every time the two compete. Teams that finish improvement work protect the time structurally, with a fixed slot, a named owner, and a measure reviewed in a meeting somebody else runs. Willpower is not a mechanism; a recurring review is.
What to look at, and how often
Framework-neutral. Whether you run OKRs, Scaling Up or 4DX, the rhythm below is the part that most often gets dropped.
| When | What |
|---|---|
| Weekly | The handful of measures that lead the quarter's goals, plus every blocker that crosses a function boundary. Blockers get an owner and a date in the meeting, not an action item to discuss the blocker later. |
| Monthly | Commitment against capacity. Which teams are carrying more goal work than last month's actual throughput suggests they can finish, and what you are going to take off them rather than ask them to try harder. |
| Quarterly | Score what finished, then re-plan against real capacity rather than the capacity you hoped to have hired by now. Name what will not happen, in writing, so teams stop half-funding it. |
| Annually | Translate the annual targets into the operating constraints they imply: headcount, systems, and the two or three cross-functional programs that will consume most of the year's slack. |