The Powerful Strategic Subtraction Test for Smarter Decisions

AI can accelerate work, but it can also multiply clutter when obsolete processes stay in place. This episode examines strategic subtraction as a leadership discipline for improving AI value, capacity, and operating focus.

It explores how leaders decide what to remove, redesign, protect, or simplify. 

TLDR / At a Glance

• Strategic subtraction discipline
 • Automation before redesign risk
 • Workflow clutter and decision friction
 • The VITALS subtraction test
 • Capacity release and governance focus
 • Protecting trust, compliance, and learning

AI can make your organisation faster while quietly making it worse. If we use copilots and agents to accelerate reports nobody reads, approvals nobody trusts, and meetings that never end in a decision, we are not transforming anything, we are scaling clutter.

We take on the most common starting point for AI transformation and argue it is strategically dangerous: asking what can be automated. The better first question is tougher and far more useful: should this work still exist in its current form? From there, we explore why AI shifts the economics of production but does not fix the real constraint in many businesses, which is attention, coordination, and the ability to absorb information without drowning in it.

To make subtraction practical, we walk through a simple leadership tool: the Strategic Subtraction Test, built around six prompts on value, interference, duplication, assurance risk, liberation of capacity, and strategic fit. You will hear how to apply it to real work objects such as meeting series, dashboards, approval steps, governance forums, workflows, and tools, plus concrete examples of actions like simplifying low-risk approvals, consolidating overlapping governance, substituting decks with live views, and hiding specialist reports from default circulation.

We also get specific about what not to cut. Some work that looks slow is actually trust infrastructure: legal controls, cyber checks, privacy safeguards, incident reviews, escalation routes, and learning loops. If we remove those without redesign, we can damage compliance, resilience, and judgement. If you want AI strategy that delivers capacity release rather than work intensification, subscribe, share this with a leader who owns “AI rollout”, and leave a review telling us what work you would stop carrying forward.

The key takeaway is that effective AI transformation depends on removing low value work before accelerating the system around it.

Transcript

The Strategic Subtraction Challenge

SPEAKER_00 0:00

The powerful strategic subtraction test for smarter decisions. Most AI conversations begin with the wrong question. Leaders ask what can be automated, accelerated, delegated to agents, or supported by AI, but the better first question is more uncomfortable. Should this work still exist in its current form? This article explores why strategic subtraction is becoming a critical leadership discipline in the AI era. If organizations use AI to accelerate obsolete reports, duplicated approvals, overloaded meetings, fragmented tools, or legacy governance rituals, they do not create transformation, they create faster clutter.

The Trap Of Automating Work

SPEAKER_00 0:42

The wrong first question. Most organizations start AI transformation by asking what can be automated. That sounds sensible, but it can be strategically dangerous. If the starting point is automation, the organization often assumes the existing workflow deserves to survive. The only question becomes how to make it faster. That is how companies end up automating clutter. A report that nobody uses becomes easier to produce. A duplicated approval becomes faster to complete. A meeting generates a better summary but still does not lead to a decision. The organization creates more output, but not necessarily more value. The better first question is not can AI do this? It is should this still be done? That question changes the conversation from automation to redesign and from productivity theater to real operating value.

When AI Makes Clutter Worse

SPEAKER_00 1:37

Why AI can make clutter worse? AI changes the economics of production. Drafting, summarizing, searching, coding, reporting, and analysis can all become faster. But faster production does not automatically create better performance. In many organizations, the constraint is no longer the ability to produce more information. The constraint is the ability to absorb it. Leaders are already dealing with too many reports, meetings, dashboards, tools, updates, approvals, notifications, and competing priorities. AI can add even more volume into a system that is already overloaded. Research shows that organizational conditions explain more than twice the reported AI impact of individual behavior. Other studies report that a relatively small group of firms capture the majority of AI's economic value, while only a minority of organizations are fundamentally redesigning how work is performed. The message is clear. AI value does not come from accelerating everything. It comes from redesigning the system around what matters, removing what no longer belongs, and protecting the work that genuinely creates trust, value, resilience, and judgment.

What Strategic Subtraction Really Means

SPEAKER_00 2:52

Strategic subtraction is not cost cutting. Strategic subtraction is the deliberate removal or redesign of organizational activity that no longer creates enough strategic value relative to the friction, duplication, risk, and capacity it consumes. It focuses on work, not just cost. That distinction matters. Cost cutting asks where organizations can spend less. Strategic subtraction asks what should no longer occupy attention, coordination, governance, and decision capacity. It can apply to meetings, status reports, approvals, dashboards, handoffs, governance steps, tools, workarounds, initiatives, cues, and legacy routines. Some work should be removed entirely, some should be simplified, some should be consolidated, some should be paused, some should be hidden from default workflows but retained for specialist use. Some should be protected because it still carries trust, risk, learning, or resilience value. This is why strategic subtraction is not crude reduction. It is disciplined judgment.

The Vitals Test In Six Questions

SPEAKER_00 4:02

The vitals test The Strategic Subtraction Test is built around six questions. Leaders can use it before approving new automation, agents, AI workflows, transformation activity, or operating model change. Value. Does this activity directly improve revenue, customer outcomes, decision quality, risk reduction, strategic learning or operational performance? Interference. How much delay, rework, queuing, review burden, search, switching, meeting load or coordination does it create? Twins. Is the same information, approval, control, report, dashboard, meeting, or initiative duplicated somewhere else? Assurance risk. If changed or removed, would trust, resilience, compliance, safety, customer promise, or learning capacity weaken? Liberation of capacity. What time, budget, leadership attention, or decision bandwidth would be released, and is that capacity actually reclaimable? Strategic fit. Does this activity support the current strategy and future operating model, or is it a legacy artifact from a previous constraint? The test works best when applied to real work objects. A meeting series, dashboard, approval step, report, review queue, governance forum, workflow, tool, or initiative. A strong subtraction candidate usually has low value, low strategic fit, high interference, high duplication, low assurance risk, and meaningful capacity release. If assurance risk is high, the answer is rarely simple removal. It is more likely protection, redesign, or risk tiering.

How To Apply Vitals

SPEAKER_00 5:52

How to use the test. The easiest way to use vitals is to start with one workflow where AI adoption is already happening or where leaders are under pressure to improve speed, cost, quality, or value. Do not begin with the official process map. Begin with how the work actually moves through the organization. Map the meetings, reports, dashboards, approvals, tools, handoffs, review cues, escalation steps, and manual workarounds. Then score each one against vitals. The aim is not to prove that everything should disappear. The aim is to separate what should be eliminated, simplified, consolidated, paused, hidden, substituted, or protected. For example, a weekly deck might be substituted with a live workflow view. A low-risk sequential approval chain might be simplified into risk-tiered review. Two overlapping governance forms might be consolidated. A report might be hidden from default circulation, but retained for audit or specialist use. A customer complaints review might be protected because it creates learning and trust, even if it feels slow. The discipline is to make the action explicit. Most subtraction fails because new work is added, but old work is never formally retired.

What To Remove And Protect

SPEAKER_00 7:11

What leaders should remove first. The best starting point is usually not headcount, it is work. Leaders should look first at standing meetings with no decision, reports that do not change action, duplicated dashboards, overlapping governance forms, low-risk approvals that move through too many hands, tools that create search and reconciliation work, and legacy initiatives that continue because nobody formally stopped them. These are attractive subtraction candidates because they often consume attention without creating proportional value. They also create drag around AI adoption. If the old meeting, report, approval, or dashboard remains in place, AI simply becomes another layer on top of the old system. Research and software delivery offers a useful warning. AI may save coding time, but developers still lose significant hours to fragmented tools, unclear requirements, meetings, and information search. The lesson applies far beyond engineering. If leaders automate the fastest part of the workflow but leave the surrounding friction untouched, the value leaks elsewhere. What leaders should protect. Strategic subtraction only works when leaders know what must not be removed. Some work looks inefficient because its value is protective rather than obvious. Legal controls, cyber checks, privacy safeguards, safety processes, customer complaint signals, incident reviews, escalation routes, override rights, and junior learning loops may all appear slow in a narrow productivity review. Removing them without redesign can damage trust, resilience, compliance, capability, and judgment. That is why assurance risk is central to the test. Leaders should not ask only whether something is slow. They should ask what it protects. A duplicated approval may be waste. A human review in a high consequence decision may be trust infrastructure. A routine report may be stale. An incident review may be a learning loop that protects the organization from repeating mistakes. Good subtraction removes clutter while protecting capability.

Avoiding AI Work Intensification

SPEAKER_00 9:28

The common failure pattern. The most common failure pattern is adding AI without retiring old work. A team introduces an AI assistant, but the old meeting continues. A workflow becomes faster, but the same approvals remain. Reports become easier to generate, so more reports appear. A new agent handles first pass analysis, but review cues grow because nobody redesigned the escalation model. That is how AI creates work intensification rather than capacity release. Research increasingly shows that AI can widen job scope, increase work density, and dissolve stopping points in the working day. Other studies warn that excessive AI use or monitoring can increase decision overload, errors, and intent to quit. If AI increases output, but leaders do not subtract work around it, the system absorbs the gain as more activity. The organization becomes busier, not better.

What Leaders Do Next

SPEAKER_00 10:31

What this means for leaders. Leaders should make strategic subtraction a formal part of AI governance, transformation planning, and operating model design. Before approving new automation, agents, co-pilots, or transformation work streams, they should ask which existing work will be removed, simplified, consolidated, paused, hidden, substituted, or protected. This is not a side exercise. It is central to value realization. AI will not deliver its full impact if it is layered onto overloaded workflows, duplicated controls, fragmented tools, and legacy routines. The organization has to create capacity before it can absorb new capability. The strongest leaders will not ask only what AI can do. They will ask what the organization should stop carrying forward. In the AI era, removing the wrong work may become just as important as accelerating the right work.

Closing And LinkedIn Reading

SPEAKER_00 11:31

Conclusion. Strategic subtraction is not cost-cutting. It is the leadership discipline of deciding what work should no longer exist before AI accelerates it. The strongest AI leaders will not simply automate more work, they will remove the work that should no longer exist. This concludes the article. You can also read this article on my LinkedIn page where I share regular insights on AI, strategy, and emerging technologies.