Most enterprises keep detailed backlogs of things that need to be built. New features. New integrations. New AI pilots. New dashboards. New automation layers. There are prioritization frameworks, roadmaps, sprint cycles, and investment committees, all of which are meant to keep the delivery pipeline moving.
Very few organizations have a backlog for stopping.
From an IT leadership point of view, this is the structural flaw that leads to digital accumulation. We have made advanced systems and processes that can add features, but we haven’t made any that can take them away. Transformation without subtraction is not transformation. It is simply expansion.
The Missing Operating Discipline
Organizations carefully manage what they build. But removal happens informally, if at all. Apps stick around for years after they stop being useful. There are so many reports that no one knows which dashboard has the right information. Integrations stay in place even when platforms change. Governance layers build up until the process of getting approval becomes a maze.
Every quarter, things get more complicated because there isn’t a structured “stop-doing” discipline. The technology portfolio turns into a museum of old choices instead of a set of tools for doing work now.
Why Subtraction Fails in Enterprises
Stopping feels like a political move. Taking a tool out of service affects stakeholders who built workflows around it. Taking away a dashboard hurts teams that depend on it for information. Getting rid of a regular meeting affects people who feel in control or derive status from attending.
So, accumulation is the safer way to go. No one minds keeping something. Taking something away makes everyone mad.
But safe accumulation creates weak systems. Every new tool, report, or integration adds more area that needs to be managed, secured, and explained. The organization gets bigger but not stronger.
For technology leaders, subtraction must be a part of the system, not just a feeling. It can’t rely on one-time cleanup campaigns or heroic efforts from team members who are fed up. It needs to be part of how the business works.
Introducing the Anti-Backlog
A mature digital organization maintains two parallel pipelines: one for what it is building and one for what it is retiring.
The anti-backlog is not symbolic. It is measurable and accountable. It includes:
-
- Applications to decommission
- Reports to eliminate
- Dashboards to consolidate
- Meetings to remove
- Governance layers to simplify
- Legacy integrations to terminate
When subtraction becomes visible and tracked, it gains legitimacy. Teams stop treating removal as failure and start treating it as essential maintenance.
To build a stop-doing operating model, you need to use certain methods that make subtraction a normal part of your day instead of something special. And here are some of those methods that I could think of:
1. Quarterly Rationalization Targets.
Commit to retiring a defined percentage of overlapping tools, reports, or processes every quarter. Make the target specific and track progress publicly. What gets measured gets managed.
2. One-In, One-Out Discipline.
Every new tool approval requires identifying at least one existing tool to sunset. This forces honest conversations about whether new capabilities or even specific functionalities truly add value or merely duplicate what already exists in another corner in another system.
3. Application Portfolio Reviews.
Conduct regular reviews of the entire application/technology portfolio with a simple question: Does this still create measurable value? If the answer is unclear or negative, move it to the Anti-Backlog.
4. Single Source Enforcement.
Get rid of duplicate reporting structures on purpose. The old dashboard must be turned off when the new one goes live. If you see conflicting numbers, you should treat them as a system failure that needs to be fixed right away.
Governance now includes subtraction, not just as an afterthought. It shows up on roadmaps, is talked about at investment committee meetings, and gets the same level of discipline as building.
What Changes When You Do This
Organizations that institutionalize subtraction experience predictable improvements. Teams no longer have to wonder which dashboard or tool to use, which improves clarity. As obsolete integrations and apps are eliminated, the security surface shrinks. Reconciliation meetings are reduced when there are fewer systems, which speeds up decision-making. As cloud instances and data centers spin down unused workloads, energy consumption drops. As the portfolio is reduced to strategic relationships, vendor management becomes easier.
Above all, architecture becomes coherent again. The technological landscape becomes comprehensible when accumulation ceases to outpace subtraction. Since new capabilities replace rather than stack, they integrate cleanly.
Without losing strength, the organization gets lighter. Because there is less to navigate, it moves more quickly.
The Final Leadership Question
Those responsible for technology should regularly ask two questions:
- If we froze new tool adoption for six months, what would actually break? The answer reveals how much of our portfolio is truly essential versus merely accumulated.
- If we froze subtraction for six months, what would eventually explode? The answer reveals where complexity is silently compounding toward failure.
Most companies fear stagnation. Very few fear uncontrolled accumulation. But accumulation is the slower, quieter threat. It does not announce itself with dramatic failures. It simply erodes capability year by year until the organization is too weighed down to move.
The Conclusion
The future is built on backlogs. They transform visions into reality and ideas into functional systems.
Anti-backlogs safeguard the future. They guarantee that our creations are still usable, that complexity is kept under control, and that potential is not obscured by accumulation.
Both are governed by mature technology leadership. It honors addition and subtraction with equal rigor. It acknowledges that an organization’s actions are just as strategic as its inactions.
After all, transformation isn’t about how much you can handle. It all depends on how much unnecessary burden you are willing to bear.
If this topic resonates with you, then I am delighted to hear your ideas too. In my book Life in the Digital Bubble, I explore how AI and digital systems are reshaping not just IT but also work, families, and society over the next three decades. And if you’re ready to turn AI from a noisy collection of projects into a clear operating model, my digital transformation and AI consulting services are focused on helping leaders design that next phase with structure, realism, and confidence.