On April 20, 1653, Oliver Cromwell walked into England's House of Commons and did something that would make any modern CEO's heart skip a beat—he completely shut down a failing system that everyone knew wasn't working. The Rump Parliament had been limping along for years, plagued by corruption, inefficiency, and an inability to make meaningful progress. So Cromwell simply said "enough" and sent everyone home.
As tech leaders, we've all been there. That legacy system everyone's afraid to touch. The process that made sense three years ago but now creates more problems than it solves. The meeting structure that generates endless discussion but zero decisions. Cromwell's dramatic parliamentary reset reminds us that sometimes the bravest leadership decision isn't trying to fix what's broken—it's having the courage to start over entirely. Sure, it's disruptive. Sure, it creates uncertainty. But sometimes you need to clear the deck to build something that actually works.
The beauty of Cromwell's move wasn't just the boldness—it was the clarity of vision that followed. He didn't dissolve Parliament just to create chaos; he had a plan for what came next. In our world of rapid iteration and agile development, we often forget that sometimes the most agile thing you can do is stop, assess honestly, and rebuild from the ground up. Whether it's sunsetting a product that's outlived its usefulness or restructuring a team that's stuck in dysfunction, Cromwell's 1653 reset reminds us that great leaders aren't afraid to press the ultimate reset button when the situation demands it.