The Core Formula
The Adoptability Equation
This is the core test applied at the level of the individual stakeholder, not the system as a whole. Adoption is local: the equation must close separately for every critical participant in a decision network — the economic buyer, the end user, the procurement officer, the compliance reviewer, anyone whose action or inaction can block the product's path into use. A single stakeholder whose equation does not close is sufficient to stop adoption for the entire system, even if every other stakeholder's equation holds comfortably.
Value Captured
Value Captured is the benefit a specific stakeholder receives and can attribute to themselves — not the benefit the product creates in the abstract, and not the benefit some other stakeholder receives. A common failure mode is a value proposition that lands in the wrong account: a clinical tool may improve patient outcomes while the savings are captured by an insurer, not the hospital implementing it; a workflow change may reduce nursing hours while the saving lands in a budget the purchasing officer doesn't control. The product creates real value. It simply isn't captured by the person whose decision matters.
Design principle: design the value proposition for the budget that decides, not for the system that benefits.
Cost of Change
Cost of Change is the total reorganization burden a stakeholder must absorb to use the product — training time, workflow disruption, compliance documentation, budget reclassification, new supplier relationships, or the political cost of navigating an approval process. This cost is routinely excluded from standard unit-economics models (CAC/LTV, payback period, gross margin), which is why a product with strong margins on paper can still fail to scale: the model never accounted for what adoption actually costs the people absorbing it.
Minimum Adoptable Product (MAP)
A Minimum Adoptable Product is the smallest version of a product that a system can absorb without reorganizing its coordination structure. It is not the same concept as a Minimum Viable Product.
MVP
Optimizes Desirability × Feasibility × Viability. Can be technically excellent and still fail to be adopted.
MAP
Optimizes Adoptability directly. Cannot exist with zero Adoptability — designed from the outset for the system's second use, not just its first demonstration.
Illustrative case — Windows 2000 vs. Windows XP: Windows 2000 was a more advanced engineering achievement built on a more stable kernel, but consumers would not adopt it because existing software and games would break. Windows XP used the same underlying kernel but wrapped it in compatibility layers designed for one purpose: lowering the Cost of Change. The product was not made more desirable — the change required to use it was made smaller. That is what closed the equation.
What a MAP minimizes
A MAP does not minimize change generally — every adoption changes something, a line item, a stocked shelf, a habit. A MAP minimizes structural change specifically: it enters through a system's existing interfaces (a purchase pathway, a workflow step, a physical fitting, a budget category) and delivers improved performance at a slot the system already has, rather than requiring the system to build a new slot to receive it.
Illustrative case — the LED bulb: a category-defining energy impact delivered through an unchanged interface — it screws into the same socket the incandescent bulb left behind. Compare this to early electrification, which delivered comparable benefit but required rewiring the building itself.