Honing vs Transformation
Martin’s maintenance philosophy: transformation is not boldness. It is the accumulated cost of not honing.
Honing is continuous, small adjustment as the environment shifts: a standing discipline of noticing drift early and correcting cheaply. Transformation is the dramatic, expensive, multi-year overhaul, and Martin's reading of it is the reverse of the business press's: organisations that require transformation every five to seven years are revealing that nobody was steering between crises. The dramatic rescue is the bill for years of deferred correction, arriving with interest.
Why honing loses politically
Transformations are visible, fundable and career-making; honing is invisible when done well, which means the incentive gradient runs the wrong way, itself a management-systems design failure. Nobody gets promoted for the crisis that never happened, so organisations systematically underinvest in the discipline that prevents crises and celebrate the leaders who resolve them. Fixing the gradient, making early correction visible and valued, is part of the systems coherence job of the CEO as chief system designer.
The barnacle connection
Barnacles accrete precisely when no honing discipline exists: each obsolete system, each small drift, individually too minor to act on, collectively the reason the eventual reckoning is expensive. The hull is either cleaned continuously or dry-docked catastrophically; there is no third option in which neglect stays free. The practical honing form for strategy itself: quarterly re-application of the Opposite Test and the Can't-Won't Test to the current How to Win. Cheap tests, run often, versus one expensive reckoning run late.
How this connects to OKRs
Our methodology institutionalises honing at two speeds: weekly check-ins correct at the goal level, quarterly retrospectives correct at the system level, and both exist so the organisation never needs the expensive reckoning. We apply the same philosophy to the methodology itself, maintained by changelog rather than reissue, which is why the concept map on this site records what changed and when instead of pretending the method arrived complete.
One line to keep: A hull is cleaned continuously or dry-docked catastrophically; there is no third option where neglect stays free.
Our synthesis of Roger Martin’s published work, sources credited. Read the originals: they’re excellent.
Why do organisations prefer transformation to honing? +
Because transformation is visible, fundable and career-making, while honing is invisible when done well. Nobody is promoted for the crisis that never happened, so companies underinvest in the discipline that prevents crises and celebrate the leaders who resolve them.
How does honing show up in OKRs? +
At two speeds: weekly check-ins correct at the goal level, quarterly retrospectives correct at the system level, so the organisation never needs the expensive reckoning. We hone the methodology itself the same way, by changelog rather than reissue.
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 →