On February 10, 1906, the British Royal Navy christened HMS Dreadnought, a battleship that didn't just raise the bar—it moved it to a completely different field. With its revolutionary all-big-gun armament and steam turbine propulsion, the Dreadnought was so advanced that it instantly rendered every existing battleship obsolete. Navies around the world scrambled to catch up, and the ship's name became synonymous with the entire new class of vessels it spawned. In one bold stroke, Britain had reset the global naval arms race.
Here's what strikes me about the Dreadnought moment: the engineers and admirals behind it didn't try to build a slightly better battleship. They reimagined what a battleship could be. In tech, we face this choice constantly. Do we iterate on existing solutions, making them 10% better each quarter? Or do we occasionally step back and ask the bigger question: what if we rebuilt this from the ground up? The iPhone moment. The cloud computing shift. The move from monoliths to microservices. These weren't improvements—they were Dreadnoughts.
The risk, of course, is real. Britain's own existing fleet became obsolete along with everyone else's. But that's the price of leading rather than following. When you're building something truly new—whether it's a product, a platform, or even a consulting approach—you might be making your own previous work outdated. And that's exactly how you know you're onto something. Sometimes the boldest business decision isn't optimizing what exists, but having the courage to make it irrelevant.