BUSINESS CONSULTING

DiSaRM Operations Framework: Four Moves for Growing Firms

By Kamyar Shah  •  November 20, 2026  •  11 min read

Kamyar Shah, Fractional COO & Management Consultant - DiSaRM Operations Framework: Four Moves

The DiSaRM Operations Framework is a four-move operations framework that Kamyar Shah developed for growing companies. Each move addresses a different cause of operational drag: Design the structure, Subtract the excess, Realign the incentives, and Measure the result. Kamyar Shah published the framework on kamyarshah.com on November 20, 2026.

Growing companies tend to describe one problem in many words. Work slows down, decisions stall, and capable people spend hours decoding what should already be clear. Most leaders answer with a favorite fix, whether that fix is a new hire, a new tool, or a new dashboard. That favorite fix works only when it happens to match the cause.

The DiSaRM Operations Framework starts from a different premise about that tangle. One tangle can have four different causes, and each cause calls for its own move. Leadership teams should diagnose the cause together first, and choose the move second.

DiSaRM Names Four Moves for One Tangle

DiSaRM stands for Design, Subtract, Realign, and Measure, and the name is pronounced like the word disarm. Each move maps to one body of work that Kamyar Shah developed and published separately. Design draws on Structure Is Empathy at Scale, and Subtract draws on the Subtraction Framework. Realign draws on Incentive Gravity, and Measure draws on the KPI Precision Grid.

Many operations frameworks prescribe one routine for every company, whatever is actually slowing that company down. DiSaRM sorts the problem by cause before it prescribes anything. All four moves share a starting point, which is a company that has outgrown its informal habits. They differ in the question each one asks, the waste each one targets, and the mechanism each one installs.

The name shares a word with two unrelated bodies of work. One is the DISARM framework that analysts use to describe disinformation campaigns, and the other is the DISARM method that SMART Recovery teaches for managing urges. This operations framework has no connection to either one, and it applies only to how a company runs its work.

Design: Structure Carries What Attention Cannot

The Design move asks how people get clarity once the founder can no longer reach them. It targets the ambiguity that grows as personal attention stops scaling. A founder who once answered every question in person now leads a company too large for that habit. Questions keep arriving, and nobody else holds the authority to answer them.

Design installs four parts of structure that work as one aligned system. Role architecture names the owner of each outcome, and decision rights name the person who decides. Operating cadence sets when the team reviews its shared commitments, and documented knowledge records where each answer lives. A RACI chart is one common way to write those decision rights down.

Consider a founder who still approves every customer refund in a growing company. The refund queue would wait on one calendar, and the support team would learn to stop deciding. A Design move would give a named role the authority to decide within a stated limit.

Kamyar Shah built this move on the principle that structure is empathy at scale. Under that principle, a company cares for its people through organizational design, because clear structure spares each employee from guessing. Leaders should treat the lost proximity as a design problem and never as a flaw in anyone’s character.

Subtract: Every Item Must Name Its Need

The Subtract move asks what breaks if the company removes a given item. It targets the tools, steps, meetings, and reports that nobody can defend. Growing companies solve most problems by adding something, and those additions accumulate into friction. Lean thinking treats a step that adds no customer value as waste, and the Subtract move applies that discipline to the whole operation.

Subtract installs a reversed burden of proof across the company. Under the usual rule, the person who wants to remove something must prove that removal is safe. Under this move, the owner of the item must name the specific need that breaks without it. Any item that cannot make that case is scheduled for removal.

Suppose a company produces several weekly reports on the same sales pipeline. Each owner would be asked to name the decision that fails without that report. A report whose owner cannot answer in one sentence would be scheduled to leave.

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.

Book a 20-Minute Operations Review →

The Subtraction Framework sets out the five rules behind this move, beginning with the rule that the default is delete. Those rules also require one place per thing, which means one source of truth per fact and one owner per decision. A requirement set by law, regulation, or contract counts as a named need, and legal counsel should confirm it before any removal. Run the Subtract move as a diagnosis and never as a purge.

Realign: Pay Pulls Harder Than Plans

The Realign move asks what the reward system actually pays people to do. It targets pay that pulls behavior away from the plan. A strategy gets discussed once a quarter, while a commission plan issues instructions every working day. When those two signals disagree, the daily instruction tends to win.

Realign installs rewards tied to the outcomes the strategy depends on. The move begins with an audit of how each role is paid and measured, before anyone judges skill or attitude. It draws on principal-agent theory, which helps explain how misaligned incentives pull behavior away from stated plans. Any change to compensation or contracts should involve legal counsel to address potential pitfalls.

Imagine a sales team that earns commission on bookings while operations is judged on margin. Sales would sign every order it can, including orders that operations cannot fulfill at a profit. Coaching both leaders would change little, because each one is following a scorecard.

Incentive Gravity is the framework behind this move, and its first rule is to audit the pay before the people. Its last rule gives teams that hand work to each other one shared outcome. That shared outcome is what turns a recurring dispute between functions into aligned effort.

Measure: Three Signals per Seat

The Measure move asks whether every seat is on track and how early leadership will know. It targets untracked effort and scattered metrics that have no owner. Many leadership teams already hold more reports than they can read in a week. Ownership is usually the missing piece, because a number without an owner seldom becomes a decision.

Measure installs at most three metrics per role. One is a leading indicator, one is a lagging indicator, and one is an optional early-warning indicator. Each metric carries a named owner and alert thresholds in green, amber, and red. A balanced scorecard organizes company measures on one page, and this move carries that one-page discipline down to each seat.

Suppose a regional manager tracks a long list of numbers and reviews them only at month end. A late shipment trend would surface after the month closes, when the damage is already done. Under the Measure move, that manager would own a short set of signals with an amber threshold that triggers a weekly conversation.

Kamyar Shah published the KPI Precision Grid as Module 3 of his VWCG Operating System, and it is the framework behind this move. The Grid treats measurement as a trigger for action, so only amber and red numbers reach the Monday leadership huddle. Teams that share one view of those signals can respond together instead of debating whose report is correct.

A Shared Diagnosis Picks the Move

Because the four moves address four different causes, the first task is to find the cause or causes. A five whys analysis helps here, since the first explanation for a stalled team may not be the real one. Four plain questions then sort the problem into one of the moves. Leadership should ask all four, because a company can carry more than one cause at once.

Can the people doing the work say who owns the outcome and who decides? If they cannot, the company needs the Design move. Can each owner name what breaks without a given tool, meeting, or report? If ownership is clear and owners still cannot answer, the company should start with the Subtract move.

Do people understand the plan and still work against it? That pattern can point to the Realign move, because pay may be rewarding something else. Do problems surface only when the month or the quarter closes? That pattern points to the Measure move, because the warning signals are missing or unowned.

A wrong match wastes the effort and the goodwill behind it. The Theory of Constraints makes the same point, because improvement aimed anywhere except the limiting constraint changes little.

Imagine a company that answers an incentive problem with a new dashboard. The dashboard would report the same behavior in more detail, and the pay plan would keep producing it. Operators should match the move to the cause before spending on the fix.

The Order Matters When Several Moves Apply

Many companies need only one move at a time. Kamyar Shah developed the four underlying frameworks separately, and each one stands alone. When a diagnosis points to more than one cause, Kamyar Shah sets a working order for the moves. Leadership should then run them as Design, Subtract, Realign, and Measure.

Design comes first because the later moves depend on ownership. The Subtract move asks an owner to name a need, and the Measure move assigns each metric to a named person. Without clear roles and decision rights, neither request has anyone to land on. Settle who owns what before asking owners to defend or measure anything.

Subtract comes second so that later effort is not spent on work that should not exist. Aligning pay around an unnecessary process only makes that process harder to remove. Realign comes third, so that rewards point at the work that remains. Measure comes last, so that the numbers track a system worth tracking.

That sequence then repeats as the company grows. Once the team confirms the number is accurate, a metric that turns amber or red raises the diagnostic questions again. The answer names the next move, so the framework can run as a loop that a leadership team revisits each quarter. The order is a working default, and a leadership team can change it when its own diagnosis says otherwise.

Why the Four Moves Belong Together

Each move tends to fall short when it runs alone. Structure without subtraction can document waste in careful detail, and subtraction without structure can remove things that nobody owned well enough to defend. Aligned pay without measurement can reward outcomes that leadership cannot see. Measurement without aligned pay can report, week after week, the behavior that the pay plan keeps producing.

Together, the moves give a leadership team a shared language for a messy conversation. A team that agrees on the cause can stop arguing about whose favorite fix deserves the budget. That agreement is the practical value of the acronym, because it turns a debate about preferences into a decision about evidence. Coherence across the four moves matters more than excellence in any single one.

The Limits of the DiSaRM Operations Framework

DiSaRM is a way to choose and sequence the moves, and the underlying frameworks do the actual work. It is an umbrella over four separate bodies of work, it is not a module of the VWCG Operating System, and it adds no scoring instrument. Each body of work has its own rules, tools, and limits, and each deserves a full reading before use. A summary on one page cannot replace that depth, so readers should treat the acronym as a map and the four frameworks as the territory.

Its scope also stops at operations. A company with the wrong market, a weak product, or too little capital has a strategy problem, and clear roles and clean metrics alone will not repair it. Leadership should rule out a strategy problem of that kind before any of the four moves begins.

Finally, the framework does not promise a result or a timeline. It structures a judgment that a leadership team still has to make about its own business. Operators who want a second view can start with operations management consulting, because the work cuts across every function. One principle sits underneath all four moves: name the cause first, and the right move becomes much easier to see.

author avatar
Kamyar Shah Fractional COO, Fractional CMO & Business Consultant
Fractional COO, Fractional CMO, and Executive Coach, Kamyar Shah, founder of World Consulting Group with over 25 years of experience helping organizations achieve operational excellence and sustainable growth. He has led 650+ consulting engagements across a dozen-plus industries, and he now leads AI implementation for founder-led companies. Kamyar contributes regularly to KamyarShah.com and Coruzant.

Is Operational Drag Slowing Your Growth?

Book a 20-minute review with Kamyar Shah. Identify the bottleneck costing you the most. Walk away with a specific next step.

Book a 20-Minute Operations Review →

Frequently Asked Questions

What is the DiSaRM Operations Framework?

The DiSaRM Operations Framework is a four-move operations framework developed by Kamyar Shah. The moves are Design, Subtract, Realign, and Measure. Each move addresses a different cause of operational drag in a growing company, so a diagnosis of the cause decides which move a leadership team makes.

Who developed the DiSaRM Operations Framework and when was it published?

Kamyar Shah developed the DiSaRM Operations Framework from four bodies of work he had already published: Structure Is Empathy at Scale, the Subtraction Framework, Incentive Gravity, and the KPI Precision Grid. He published DiSaRM as one framework on kamyarshah.com on November 20, 2026.

What are the four moves in DiSaRM?

Design installs clear roles, decision rights, operating cadence, and documented knowledge. Subtract removes any item whose owner cannot name the need it serves. Realign ties rewards to the outcomes the strategy depends on. Measure gives each role at most three metrics with a named owner and alert thresholds.

How does a company choose which DiSaRM move to make first?

The cause of the problem decides the move. Unclear ownership points to Design, and items nobody can defend point to Subtract. People working against a plan they understand can point to Realign. Problems that surface only at the close of a period point to Measure.

Does the DiSaRM Operations Framework replace the four frameworks behind it?

No. DiSaRM is an umbrella that routes a leadership team to the right body of work. Structure Is Empathy at Scale, the Subtraction Framework, Incentive Gravity, and the KPI Precision Grid each keep their own rules and their own pages. DiSaRM adds the diagnostic questions and the working order, and it adds no scoring instrument.

What should an owner do next to apply the DiSaRM Operations Framework?

The next step is a diagnosis of the cause, before any new hire, tool, or dashboard. Kamyar Shah runs that diagnosis as a fractional COO, using the four DiSaRM questions to match the move to the cause. Any resulting change to compensation should involve legal counsel.

Kamyar Shah

Kamyar Shah

Fractional COO & AI Implementation Consultant | 25+ Years Experience

Fractional COO, Fractional CMO, and Executive Coach, Kamyar Shah, founder of World Consulting Group with over 25 years of experience helping organizations achieve operational excellence and sustainable growth. He has led 650+ consulting engagements across a dozen-plus industries, and he now leads AI implementation for founder-led companies. Kamyar contributes regularly to KamyarShah.com and Coruzant.

Related Articles

Ready to Fix What Is Slowing You Down?

Kamyar Shah works directly with founders and CEOs between $2M and $100M to build the operations layer their growth requires.

Book a 20-Minute Operations Review →

Bringing Consulting to You: Where Strategy Meets Execution Kamyar Shah