CEO as Chief System Designer
The one strategy job a CEO cannot delegate: designing the coherence of the management systems, because nobody else spans them.
The logic is structural. Every function designs its own systems well and locally, finance builds a budgeting system, HR a review cycle, IT a security protocol, and each is sensible alone. Together they signal conflicting priorities to the same people, the accumulation described in the Barnacle Problem. Only one person has both the visibility across all systems and the authority to change any of them. If the CEO does not own coherence, no one does, and incoherence is the default state, not the exception.
What the role requires
Four disciplines. Treat budgeting, planning, performance review, incentives and promotion criteria as one signal system, not separate administrative machinery: employees experience them as one voice, so design them as one. Uninstall systems that motivate obsolete behaviour, not just install new ones; installation is the easy half and almost the only half ever done. Prefer honing to transformation: continuous small adjustment rather than periodic dramatic redesign. And model the signal personally, because leader behaviour is the signal that wins whenever the systems conflict.
The failure mode
A CEO who approves the strategy and delegates "implementation", leaving the nervous system wired for the previous strategy while expecting new behaviour. The organisation is not resisting; it is complying, precisely, with the systems it actually has. Strategy documents lose to promotion criteria every time the two disagree, and in most companies they disagree in a dozen quiet places nobody has audited.
How this connects to OKRs
In our methodology, OKRs, the KPI Scorecard, check-ins and retrospectives are exactly this box of the cascade: management systems, translating choices into weekly behaviour. Which is why an OKR rollout is a systems-design act, not a template purchase, and why it fails when installed alongside an unreformed bonus plan or review cycle that keeps paying for the old behaviour. Coherence is the deliverable; the format is just its carrier.
One line to keep: An OKR rollout is a systems-design act, not a template purchase; coherence is the deliverable.
Our synthesis of Roger Martin’s published work, sources credited. Read the originals: they’re excellent.
What does “CEO as chief system designer” mean? +
That budgeting, planning, review, incentives and promotion are one signal system employees experience as a single voice, and only the CEO spans them all. Coherence across systems cannot be delegated, because nobody else can see the whole.
Why do OKR rollouts fail under this lens? +
Because OKRs, the scorecard, check-ins and retrospectives are the management-systems box of the cascade. Install them beside an unreformed bonus plan or review cycle and the old machinery keeps paying for the old behaviour. Coherence is the deliverable, not the format.
Reading about method is not the same as running it. We install this system and build the capability that stays.
Turn strategy into executed strategy →