Fixing systems while they remain in use

Maintaining systems during transition. Benjamin S. Church repaired a leaking New York City aqueduct in the 1860s by introducing bran into the water flow to seal the breach without stopping the city’s supply (Growth Mindset). Paul Downey similarly managed the transition from the UK’s Directgov to GOV.UK by mapping old URLs to new destinations so users could navigate the change without losing access to necessary information (Growth Mindset). Both cases demonstrate that effective improvement requires keeping existing operations functional while implementing more permanent solutions.

Reframing purpose over product. Steve Jobs redirected Apple’s development of the iPhone by declaring the team was not building a phone, but rather a platform and a remote control for life, which allowed the product to evolve beyond the constraints of industry expertise (Brian Solis from A Quantum of Solis, Brian Solis from A Quantum of Solis). Michelin transitioned from a tire manufacturer to a global restaurant authority by defining its purpose as helping people travel farther and better, rather than focusing solely on rubber production. These organizations maintained relevance by prioritizing the human need served over the specific product portfolio currently in place.

Experimenting to resolve ambiguity. Richard Banfield advises high-agency individuals to treat problems as hackable opportunities by running 24-hour experiments to push stalled projects forward (Richard Banfield). Kent Beck suggests that when a situation defies logic, identifying the specific fact that would make the scenario sensible serves as a reliable diagnostic tool (Kent Beck from Software Design). These methods shift focus from abstract worry to concrete action, allowing for better decision-making in uncertain environments.