Minimum Viable Friction: A practical framework for better decisions

Executive summary

Most organisations have spent years removing friction to move faster. In many cases, this has improved efficiency. In others, it has quietly removed the moments where thinking and judgment used to occur.

Minimum Viable Friction is a simple framework for reintroducing just enough pause into high-impact decisions to reduce avoidable mistakes without slowing delivery. It applies only to decisions that are hard to reverse, involve genuine uncertainty, or carry material risk.

The framework introduces three lightweight checkpoints: clarifying assumptions, scanning for broader impacts, and recording a brief judgment statement. These steps take minutes, not weeks, and are designed to fit inside existing ways of working.

Organisations that apply Minimum Viable Friction are not slower. They are more deliberate. They make fewer irreversible mistakes, recover faster when conditions change, and retain clear human accountability even as automation and AI accelerate decision-making.

The outcome is not more process, but better decisions where it matters most.

Minimum Viable Friction

A practical framework for better decisions

Over the last decade, organisations have worked hard to remove friction from how they operate. Approval chains were shortened, processes streamlined, and decisions pushed closer to delivery teams. Automation promised speed, consistency, and scale.

Much of this work was overdue. Excessive friction does slow organisations down and obscures accountability. But in many cases, friction was removed without asking what role it was playing.

Along the way, many organisations also removed the moments where thinking, judgment, and reflection used to occur.

When efficiency undermines decision quality

Most organisational failures are not caused by poor intent or lack of capability. They occur when decisions are made quickly on the basis of incomplete understanding.

Assumptions remain implicit. Risks feel obvious until they materialise. Second-order impacts surface only after commitments have been made.

Highly optimised systems are excellent at executing known patterns. They are far less effective at questioning whether those patterns still apply. When everything is designed to move forward smoothly, there are fewer natural checkpoints where direction itself is examined.

Speed becomes a proxy for certainty.

What Minimum Viable Friction means in practice

Minimum Viable Friction refers to the smallest amount of intentional resistance needed to improve decision quality without creating drag. It is not about adding layers of process or slowing teams down unnecessarily. The intent is to introduce carefully placed pauses at the points in a decision flow where mistakes are hardest to reverse.

Those pauses do not exist to seek permission or enforce compliance. They exist to make thinking explicit. When someone has to explain why a decision makes sense, what assumptions it relies on, or how risk has been weighed, weak reasoning tends to surface quickly. Strong reasoning becomes clearer too.

This approach works because it is proportional. Friction appears where uncertainty, impact, or irreversibility are high, and stays out of the way everywhere else.

Why this matters now

Several changes have made the absence of friction more risky than it appears.

Teams operate under sustained cognitive load, surrounded by dashboards, alerts, and competing priorities. Reflection is often the first casualty. At the same time, AI systems now generate recommendations, summaries, and forecasts at speed. The risk is not that these outputs are always wrong, but that they feel authoritative enough to bypass judgment.

Organisations are also more interconnected than ever. Decisions made in one area can ripple across systems, teams, and incentives in ways that are not immediately visible. Faster decisions reduce the opportunity to notice those effects in advance.

Removing all friction in this environment does not create clarity. It creates blind spots.

Where friction belongs

Not all work benefits from friction. Routine, repeatable execution should be smooth and predictable. Payroll, infrastructure scaling, and standard operational processes work best when resistance is low.

Friction belongs at inflection points. These are moments where decisions are ambiguous, irreversible, or have material consequences for people, trust, or risk exposure.

The failure mode is applying friction everywhere, or nowhere. Minimum Viable Friction is about being selective and deliberate.

What it looks like on the ground

In practice, Minimum Viable Friction is usually light-touch. It might take the form of a brief written articulation of what would need to be true for a decision to fail. It might require a short justification when accepting an AI-generated recommendation. It might introduce a deliberate delay before committing to a non-urgent but high-impact change.

These interventions are not designed to block progress. They exist to surface thinking that would otherwise remain implicit. The value lies less in the artefact produced and more in the act of explanation itself.

What it is not

Minimum Viable Friction is often mistaken for distrust or an attempt to control decision making. In practice, it is neither. It does not exist to protect legacy roles or slow down change. It reflects a simple reality: confidence and correctness are not the same thing, and systems that remove every pause make that difference harder to detect.

Poorly designed friction creates compliance theatre. Well-designed friction creates clarity.

A more useful definition of organisational maturity

Maturity is often equated with speed: faster delivery, faster decisions, faster change. In practice, mature organisations are those that understand when speed is appropriate and when it is not.

They treat judgment as a finite resource and design their systems to protect it. Minimum Viable Friction provides a way to do this without reverting to bureaucracy. It recognises that some resistance is not a flaw in the system, but a feature that keeps decisions grounded and accountable.

The Minimum Viable Friction framework

The framework itself is intentionally simple. It is designed to be applied inside existing decision-making processes, not layered on top of them.

Minimum Viable Friction is applied by identifying decisions that meet at least one of three criteria: they are hard to reverse, they involve significant uncertainty, or they have material impact on people, trust, or risk exposure. Routine operational decisions do not enter the framework.

Once a decision qualifies, three lightweight checkpoints are introduced.

The first checkpoint is an assumption check. Before the decision proceeds, the decision owner articulates the key assumptions it relies on. This does not need to be exhaustive. The goal is to surface what must be true for the decision to succeed.

The second checkpoint is an impact scan. The decision owner considers who and what will be affected beyond the immediate scope. This includes downstream teams, customers, systems, incentives, or regulatory obligations. The intent is not to predict every outcome, but to avoid narrow optimisation.

The third checkpoint is a judgment statement. The decision owner briefly records why they believe this is the right decision now, given the available information, and what would cause them to revisit it later.

These checkpoints can be completed in minutes. They can be written, verbal, or embedded into existing tooling. What matters is that the thinking happens and is visible.

How to use the framework

Start by mapping your current decision points. Identify where irreversible or high-impact decisions are being made quickly or implicitly.

Introduce the framework only at those points. Do not apply it universally. Overuse will dilute its value.

Assign a clear decision owner. Minimum Viable Friction increases accountability by making it explicit who is exercising judgment.

Keep the artefacts lightweight. A paragraph is usually sufficient. The purpose is not documentation for its own sake, but clarity in the moment.

Review outcomes periodically. If decisions consistently require rework or reversal, increase friction slightly. If decisions move smoothly with good outcomes, friction may already be sufficient.

The framework should evolve with the organisation. As confidence, capability, and shared understanding grow, the amount of friction required often decreases.

Minimum Viable Friction is not a control mechanism. It is a design tool for protecting judgment at the moments where it matters most.

How Changeable applies Minimum Viable Friction

At Changeable, Minimum Viable Friction is applied as a practical decision design tool, not as a generic governance overlay. We embed it directly into existing delivery, transformation, and AI-enabled workflows so it supports momentum rather than competing with it.

In discovery and strategy work, we use the framework to slow decisions that lock organisations into long-term paths before assumptions have been tested. This typically shows up in operating model changes, technology selections, AI use-case prioritisation, and investment sequencing. The framework ensures that confidence is grounded in shared understanding rather than optimism or precedent.

In delivery and change programmes, we apply Minimum Viable Friction at transition points where decisions become difficult to reverse. Examples include moving from pilot to scale, shifting ownership from project to operations, or automating decisions that were previously human-led. The intent is to make judgment explicit at the moment responsibility changes hands.

In AI and automation work, the framework is used to preserve human accountability. AI-generated recommendations, classifications, or actions are paired with lightweight judgment statements that clarify why an output is being trusted, where its limits are, and what signals would trigger review. This allows organisations to move quickly without surrendering responsibility to opaque systems.

Across all engagements, we calibrate friction to context. High-trust, high-capability teams often require very little. Less mature environments may need slightly more structure at first, which can be reduced over time as decision quality stabilises.

The goal is not control. It is decision confidence that holds up under pressure.