Innovation is usually described as an act of addition.
A new platform. A new AI tool. A new capability. A new process. A new way of working.
That makes sense. New things are visible, easy to point to, and usually easier to celebrate. But some of the hardest innovation decisions have nothing to do with adding something new. Sometimes innovation means deciding that something which still works should no longer exist. That sounds strange because most organizations are wired to replace things only when they fail. If the system still runs, the process still produces an output, or the spreadsheet still gets updated every month, the instinct is to leave it alone. Why create disruption if nothing is technically broken?
Because working is a very low standard.
A system can work while becoming expensive to support. A process can work while requiring three people to touch something that should require one. A workflow can work while depending on tribal knowledge, duplicate entry, manual checks, or a workaround nobody would design that way today. None of those things look like a crisis. That is exactly why they survive.
The cost of keeping what works
The longer something remains in place, the more arguments accumulate for keeping it. People know how to use it. Someone built an integration around it. Another team depends on a report it creates. Training already exists. The cost to replace it is visible, while the cost of keeping it is spread across support time, inefficiency, complexity, and missed opportunity.
So the old thing stays. Then the organization adds the new thing beside it.
Now there are two systems, two processes, or two ways of doing the same work. The modernization effort may technically be complete, but very little has actually been simplified.
This is how innovation quietly becomes accumulation.
New technology gets layered on top of old decisions, old workflows, and old assumptions until the organization is carrying more complexity than it had before the transformation started.
Retirement is a leadership decision
This is why retirement should be treated as part of innovation, not as cleanup after the interesting work is finished.
The question is not simply, "Does this still work?"
A better set of questions is:
- Does this still deserve investment?
- Does it support where the organization is going?
- What complexity are we carrying just to keep it alive?
- What behavior or process does it force us to preserve?
- What capacity would we create if we stopped doing it?
Those questions are harder because the answer may be uncomfortable. Sometimes the system is reliable. Sometimes the process has been around for years. Sometimes nobody is complaining loudly enough to create urgency. And sometimes the right decision is still to retire it.
In the LEAD IT framework, Innovate is not about chasing every new technology. It is about creating room for tomorrow while still delivering today. Creating that room sometimes requires subtraction. You cannot keep every old system, every old process, every old habit, and still expect the organization to move faster simply because you added something new.
Sometimes the most innovative sentence a leader can say is:
"It still works. We're retiring it anyway."