Kamyar Shah’s Subtraction Framework is the operating decision framework he uses as a fractional COO and founder of World Consulting Group. It reverses the burden of proof: the owner of every process, tool, report, and meeting must name the specific need that breaks without it, or it goes. Five rules turn that test into daily operating discipline.
The Bottleneck: Addition Is the Default
Growing companies tend to solve problems by adding. A missed handoff produces a new report, a failed launch produces a new approval step, and a difficult quarter produces a new tool. Each addition looks reasonable when someone proposes it. The sum of those additions is the friction that slows every later decision.
Addition also feels like progress. A new dashboard is visible, and a deleted one leaves no trace of the work behind it. Leaders tend to be thanked for what they launch and seldom for what they remove. Name that bias before it shapes the next decision.
Gabrielle Adams, Leidy Klotz, and their colleagues reported in Nature in 2021 that people tend to overlook subtractive changes when asked to improve something. Klotz’s book Subtract, published the same year, explores that habit and how to counter it. The Subtraction Framework is not that research. It is a narrower operating rule set for deciding what a company keeps.
The Anti-Pattern: Asking Whether Something Is Useful
The anti-pattern is the periodic cleanup that asks whether each item is useful. Almost everything in a company is useful to someone, so the question protects waste instead of removing it. The report stays because one manager reads it, and the tool stays because one team still logs in. Stop asking whether a thing is useful, because usefulness is a test that almost nothing fails.
A second version of the same mistake treats past cost as a reason to keep something. The money and the effort are already spent, and keeping the item adds a maintenance cost on top. Judge every item by what it costs the operation from today forward. Leave the purchase price out of the decision.
The Calm Rule: Reverse the Burden of Proof
The calm response is a diagnosis, not a purge, and it changes only who must make the case. Under the usual rule, the person who wants to remove something must prove that removal is safe. Under the Subtraction Framework, the owner of the thing must show that its absence would break a specific need. An item with a real need answers in one sentence, and an item that cannot answer is scheduled for removal.
The Framework: Five Rules
The five rules follow from that one reversal. Each rule closes a route by which an unnecessary thing normally survives. Kamyar Shah first published them on August 14, 2026, in a note to his Substack newsletter.
Default is delete. Nothing stays because it is good. It stays only because removing it breaks a named need, so the burden of proof is on existence, not deletion. A thing that cannot make that case leaves, however long it has been in place.
The need must be named, not implied. “Best practice,” “might be useful,” “it is free,” “everyone does it,” and “it is already paid for” are not needs. A need that nobody can state as a specific thing that breaks is not a need. Ask for the sentence, and treat a long explanation as a sign that the need is implied.
One place per thing. Keep one source of truth per fact, one channel per function, and one owner per decision. A second copy is a future contradiction, which is why a RACI chart names one accountable person per task. When a fact must appear in two places, one holds it and the other points to it.
Free 20-Minute Operations Review
Dealing with a specific operational bottleneck? Kamyar Shah works with founders and CEOs to identify the root cause and build a fix.
No speculative generality. Add no tool, process, role, or capacity for something the company does not have today. A future need cannot be named today, so it fails the second rule automatically. A signed commitment or a specific, named risk is a present need, not a speculative one.
Success = the next change is fast. The measure of any system, document, or process is how cheaply the team can change it tomorrow. An impressive system that nobody dares to touch has failed the test. The framework treats that speed as a better sign of scalability than the sophistication of any single process.
Why the Framework Holds Together
The framework holds together because it makes one move and lets the rest follow. Named needs become the only admissible evidence, which moves the debate away from taste and seniority and toward a shared standard. One place per thing removes the question of which copy is true. Speculative additions fail quickly, because a guess about the future cannot name what breaks today.
The same logic sits underneath familiar operating frameworks. Lean treats a step that adds no value for the customer as waste to remove or reduce. The Theory of Constraints directs improvement effort to the one constraint that limits the whole system. The Subtraction Framework borrows that discipline for a company with no formal improvement program.
Subtraction also offers one explanation for why some companies feel coherent. Their SOPs tend to be short because each step protects something specific. Their dashboards are small because each measure serves a decision, a discipline close to the way a Balanced Scorecard ties each measure to strategy. Coherence, in that sense, is what remains after a company stops maintaining what it cannot justify.
Where the Framework Applies
Consider a weekly report that five managers receive. Ask each recipient what decision would break without it, and remove the report if nobody can name one. If one manager names a real decision, keep only the lines that decision needs. The design goal is a report that exists for a decision instead of a habit.
Suppose a company runs two tools that both hold customer records. The third rule would assign each fact one home and reduce the second tool to a reference or remove it. The question of which record to trust would then have one answer. Saving the license fee matters less than ending the contradiction.
Imagine a leadership team that wants a new approval step after an expensive mistake. The second rule would ask what specific failure the step prevents, and the third would ask whether an existing control already covers it. The fourth rule would reject any part of the step aimed at failures nobody can name. A step that survives all three questions has earned its place.
Consider a recurring meeting that began as a response to one difficult project. Ask what decision the meeting makes and who would miss that decision if the meeting stopped. A meeting with no named decision would end, and its one useful update would move into an existing session. The information would stay available, and the standing meeting would not.
What Subtraction Is Not
Subtraction is not cost cutting, and headcount reduction is not its purpose. A cost program asks what the company can afford to lose. The Subtraction Framework asks what each thing protects, and what a company pays to protect a named need is a separate decision. Treat any proposal that cites the framework to justify a cut as unproven until the owners confirm that no named need exists.
Subtraction is also not minimalism for its own sake. Some needs come from outside the company, and an outside obligation is a named need. Ask legal counsel before removing any control that such an obligation may require. Removal follows the test, never a preference for less.
Subtraction Protects People
Every unnecessary process is a demand on someone’s attention. People spend effort maintaining reports nobody reads, reconciling copies that disagree, and waiting on approvals that protect nothing. Removing those demands is a form of service, because it returns time and clarity to the people doing the work. The same idea drives the principle that structure is empathy at scale.
Subtraction can also build trust in the systems that remain. When every surviving process can state its need, people have reason to treat process as protection. One source of truth supports consistency, because it leaves less room for private interpretation. Protect that trust by holding every surviving process to the same standard at each review.
Running the Test
Start with one function, not the whole company. List what that function maintains: its reports, meetings, tools, approvals, and documents. Ask the owner of each item to state the specific thing that breaks without it. Record the answer in one sentence.
Announce each item that has no named need, and remove it when nobody names one. Confirm with legal counsel that no outside obligation depends on an item before it goes. Give every surviving fact, channel, and decision a single home. Borrow the discipline of the five whys when an owner answers with a habit instead of a need.
Then measure the function by how quickly it absorbs its next change. This review is part of the working core of a Kamyar Shah fractional COO engagement.
Repeat the test on a fixed cadence, because additions tend to return when attention moves elsewhere. A quarterly pass through one function at a time keeps the review small enough to finish. Apply the same test at the door: every new proposal states its named need before anyone builds it. Refine the system by removing parts, and let each removal compound into the next.
What the Framework Asks of a Leader
Operational excellence is usually described as something a company builds. The Subtraction Framework treats it as something a company reveals, by removing what stands between the team and the work. The discipline is harder than it sounds, because every addition has an advocate and deletion rarely does. A leader who takes the side of deletion protects the capacity of the organization to change.
