The most reliable indicator of whether an operating system is working is not the quality of the plans — it's the follow-through rate.

Commitments made in planning sessions, staff meetings, and one-on-ones that don't get followed through aren't signs of individual failure. They're signs of a broken system.

This is a hard thing to absorb if you're a manager, because the reflex when commitments aren't met is to look at the person who didn't deliver. Usually that's the wrong question. The right question is: what is it about the system that made it easy for this commitment to not be kept?

What a Broken Follow-Through System Looks Like

The symptoms are easy to recognize once you know to look for them:

Every planning cycle produces a plan that looks nothing like the next quarter's work. This is the clearest signal. Teams plan aggressively, commit broadly, and then spend the quarter re-prioritizing instead of executing what they committed to. The plan becomes aspirational almost immediately.

Blockers don't get surfaced until the review. In a functioning system, blocked work gets flagged immediately — at the daily standup, in the weekly review, in Slack. When blockers only surface at the review, it means the escalation path isn't working in real time. The system is producing theater, not signal.

The same conversations happen repeatedly without resolution. A decision gets made, action is assigned, the next meeting notes the action, nothing happens, the decision gets remade. This is the most exhausting pattern in organizational life and it is always a system failure, not a motivation failure.

People stop making commitments because they've learned they won't keep them. When follow-through rate is consistently low, the rational response is to stop committing. This is how operating systems degrade: not with a dramatic failure, but with a gradual withdrawal of genuine commitment.

Distinguishing System Failure from Overcommitment

Not every follow-through problem is a system failure. Sometimes teams are consistently overcommitted — they agree to more than they can do, not because the system doesn't surface blockers, but because they don't accurately estimate their capacity.

You can tell the difference by looking at what doesn't get done:

System failure: the commitments that don't get met are the ones that were made in the planning forum, but work continues on other priorities. The plan degrades, but new work still happens. The team is busy but not executing the plan.

Overcommitment: the commitments that don't get met are mixed in with work that also doesn't get met — everything slips proportionally. The team is trying to do everything and finishing nothing well.

Overcommitment requires a planning discipline conversation: can we agree that we will do fewer things and do them well? System failure requires a different diagnosis: which part of the system — the planning, the review, the decision rights, the information flow — is breaking down?

Both are fixable. Neither is fixed by hoping for better execution from the same system.