TBM 431: The Denominator That Matters

John Cutler · email · 2026-07-19 Reader 🖥️

AI as Amplifier Enterprise AI Adoption & Readiness Measuring AI Impact Trust

AI success in an organization is the multiplicative product of Machine Understanding, Problem Understanding, and Practice Evolution, all divided by the Social Contract -- and because the Social Contract sits in the denominator of a multiplicative formula rather than as a fourth additive factor, no amount of strength in the numerator can compensate for a broken Social Contract, which is why resistance to AI mandates absent a credible social contract is rational self-preservation rather than ignorance or fear.

practical · expository model-explainer (short newsletter essay built around a single equation) — A compact installment in Cutler's recurring 'physics vs. variables' move (also TBM 430, TBM 432) -- AI doesn't change the underlying causal structure of organizational success, only the terms feeding it -- but here the abstraction is literalized into an actual multiplicative ratio with a named, load-bearing denominator, making the essay read as diagnostic/prescriptive rather than purely descriptive.

Structure

Part	Role
Opening formula	thesis
The Variables (Machine Understanding / Problem Understanding / Practice Evolution / Social Contract)	definition
Failure Modes	demonstration
Closing (denominator collapse / mandate critique / 'not optional')	conclusion

Key terms

Success = (Machine Understanding × Problem Understanding × Practice Evolution) / Social Contract
Cutler's own coinage for this piece: a ratio model in which three factors multiply in the numerator and one gating factor sits in the denominator, so the whole expression collapses toward zero if any numerator term is absent, and collapses regardless of the numerator if the denominator is broken.
Machine (Technology) Understanding
A viable mental model of what AI actually does -- inputs, outputs, failure modes, and (incompletely known) costs -- sufficient to get past treating AI as 'magic,' explicitly not requiring expert-level math.
Problem Understanding
Context, domain experience, skill, customer knowledge, constraints, history, and politics -- everything that makes a problem a specific real-world problem rather than a generic one; without it AI just accelerates the Build Trap.
Practice Evolution
How the work actually gets done -- experimentation, feedback loops, workflow adaptation, team learning -- treated as necessarily unstable ('no best practices yet... things change every week').
Social Contract (the denominator)
The organizational commitment that gains from improvement will be used in line with a shared agreement rather than against the people who generated them, and that the work stays compatible with people's identity; placed structurally as a divisor, not a fourth additive input.
Rational resistance
Cutler's reframing of resistance to AI mandates: not ignorance, not mere fear for one's job, but an accurate reading of both the absent evidence for AI's value and the absent guarantee that gains won't be captured against the people who produced them.

Propositions

explicitAI success in an organization equals Machine Understanding times Problem Understanding times Practice Evolution, divided by Social Contract.conf: high
extendsTBM 432: Bundling & Unbundling Capabilities (and AI) · p6 — TBM 432 states AI changes the magnitude, cost, and feasibility of capability motions but not their underlying causal 'physics'; TBM 431 operationalizes that same physics-vs-accelerant thesis into a literal ratio with named variables, applied to organizational AI success generally rather than to capability motions specifically.
explicitBecause the numerator is multiplicative, any single term at zero (no Machine Understanding, no Problem Understanding, or no Practice Evolution) reduces the whole product to zero regardless of how strong the other two terms are.conf: high
explicitMachine Understanding requires a viable mental model of AI's inputs, outputs, and failure modes -- not expert-level math -- sufficient to get past treating AI as 'magic.'conf: high
explicitProblem Understanding is what makes a problem a specific real-world problem rather than a generic one; without it, AI just executes the Build Trap faster.conf: high
explicitPractice Evolution is the connective tissue between knowing and doing -- experimentation, feedback loops, workflow adaptation -- and requires accepting that no AI 'best practices' exist yet because conditions change weekly.conf: high
explicitThe Social Contract is the organizational commitment that gains from improvement will be used in line with a shared agreement rather than turned against the people who generated them, and that the work stays compatible with who people are and are becoming.conf: high
explicitResistance to AI mandates is rational self-preservation, not ignorance, when there is no credible social contract that gains will not be captured against the improvers -- kaizen specifically depends on that credible contract to function.conf: high
supportsTBM 428: Yes, Robot. Yes, Boss? · p2 — TBM 428 argues AI can relieve capability-and-friction blockers but cannot fix motivational/political blockers (fear, misaligned incentives, illegitimate power). TBM 431's Social Contract names exactly that class of blocker and gives it a structural role (denominator) rather than leaving it as one more listed factor.
explicitThe evidence for AI's organizational value is not yet in -- 'the jury is genuinely still out' -- so resistance grounded in that absence of evidence is an accurate reading of the current state, not merely emotional or self-interested.conf: high
explicitMost AI mandates fail because they try to force Practice Evolution high (compulsory usage) while assuming Machine Understanding and Problem Understanding will develop on their own -- an assumption Cutler asserts is false.conf: high
supportsTBM 428: Yes, Robot. Yes, Boss? · p1 — TBM 428 argues AI amplifies the direction an organization is already moving in. TBM 431's diagnosis of the 'Everyone must use AI' mandate -- forcing Practice Evolution while assuming the rest will follow -- is a concrete instance of that general amplification claim applied to mandate design specifically.
explicitEven when the full numerator is strong -- people understand the machine, know the problem, and are ready to experiment -- honest effort never arrives without a credible Social Contract.conf: high
implicitBecause the Social Contract occupies the denominator rather than a fourth multiplied numerator slot, it functions as a gating precondition rather than a contributing factor: it cannot be traded off against, compensated for, or averaged with the numerator terms -- a broken denominator collapses the formula 'regardless of how strong the numerator is.'conf: medium
extendsTBM 430: Incubate, Compound, Refinance, Liquidate · p11 — TBM 430 argues AI's benefit or harm can't be judged from the technology alone -- it first requires diagnosing which portfolio quadrant/trap an asset occupies. TBM 431 makes the analogous move for org-wide AI success: the Social Contract must be diagnosed first, as a gating precondition, before the numerator terms matter at all.

Arguments

The Social Contract is not optional -- it is the precondition for everything above the line, and most AI mandates fail because they never address it. strength: low

Explicit premises:

Success is modeled as (Machine × Problem × Practice) / Social Contract.
When the denominator is broken, the formula collapses regardless of how strong the numerator is.
Most AI mandates only push Practice Evolution (compulsory use) and assume Machine and Problem Understanding will follow, while none of the mandates observed address the Social Contract at all.

Implicit premises:

A term placed in the denominator of a ratio has categorically different leverage over the outcome than a term placed in a multiplied numerator -- it gates rather than merely contributes.
The organizations issuing AI mandates generally have not established a credible Social Contract before or alongside the mandate.

Inferences:

From the mathematical structure of the ratio (division dominates any finite numerator when the denominator approaches zero) to the practical claim that social-contract work must precede or accompany technical and practice work, not follow it.
From 'resistance is rational absent a credible social contract' to 'organizations should read resistance as diagnostic signal about the denominator, not as an obstacle to route around.'

Narratives

The 'Everyone must use AI' mandate, cited as a real-world pattern rather than a specific named case.
→ Serves as the essay's one concrete illustration of the abstract failure-mode claim -- a mandate that forces Practice Evolution alone while assuming Machine and Problem Understanding will resolve themselves, which Cutler says they won't.

Questions addressed

✅ Why do people resist AI mandates?
Rational self-preservation in the absence of a credible social contract that improvement gains won't be captured against the people who generated them -- not ignorance, not mere fear for one's job.
✅ What determines whether AI succeeds or fails in an organization?
The multiplicative product of Machine Understanding, Problem Understanding, and Practice Evolution, gated by a Social Contract in the denominator -- but resolved definitionally via the formula, not operationally (none of the four terms is given a way to be observed or scored).
⭕ How would an organization actually know where it stands on any of the four variables, or measure 'success' as an output in the first place?

Gaps

incompleteNone of the four variables is defined operationally or made measurable -- there is no way to observe, score, or compare 'Machine Understanding,' 'Problem Understanding,' 'Practice Evolution,' or 'Social Contract' for a given organization, so the essay's most emphatic claim (denominator collapse dominates any numerator strength) cannot actually be tested against a specific case.
Read next: TBM 430's own unresolved gap about un-operationalized axes (extract-tbm-430-incubate-compound-refinance-liquidate#g1); DORA/SPACE literature on operationalizing soft organizational constructs into measurable proxies.
illogicalThe formula's multiplicative structure and 'denominator' framing borrow the rhetorical authority of arithmetic (multiplication, division, zero-collapse) to argue a qualitative organizational claim, but none of the four terms are actual quantities -- there is no unit, no scale, and no independently verifiable zero point for any of them. Treating 'the formula is multiplicative' as a premise that licenses 'the denominator is not optional' smuggles more logical necessity into the argument than a metaphor can bear.
Read next: Compare with other multiplicative-formula rhetoric in the corpus (e.g. TBM 430/432's 'physics vs. variables' framing, which stays at the level of causal structure rather than literal arithmetic) to see whether Cutler's other pieces make the same move more cautiously.
uninformedCutler doesn't engage existing organizational-trust or lean/kaizen literature (Edmondson on psychological safety; Toyota-style gainsharing and no-layoff commitments) that has already studied exactly this precondition -- what specific mechanisms actually make a social contract credible, as opposed to merely asserted in a newsletter paragraph.
Read next: Edmondson on psychological safety as receiving infrastructure for surfaced truth; lean/kaizen literature on the specific institutional guarantees (no-layoff pledges, gainsharing) that historically made continuous improvement programs credible to workers.
incompleteThe essay names six failure-mode combinations for the three numerator variables but treats each as strictly present-or-absent; it never explores degrees -- what happens when a term is weak rather than zero (shallow Machine Understanding, superficial Problem Understanding)? The all-or-nothing 'zero kills the product' framing may not describe real organizations, where these variables are usually partial and blended rather than binary.
Read next: Compare with TBM 432's more granular nine-motion taxonomy of capability change (extract-tbm-432-bundling-unbundling-capabilities), which at least allows partial/simultaneous states rather than binary presence/absence.
incompleteThe Social Contract is defined only in the negative (what breaks it: capturing gains against the people who generated them, threatening identity) -- Cutler gives no positive example of an organization that has actually established a credible AI-era social contract, so readers have no model to build toward, only a diagnosis of absence.
Read next: Case studies of organizations with explicit AI-era no-layoff or gainsharing commitments tied to productivity tooling, if any exist publicly, would test whether the Social Contract Cutler describes is achievable or aspirational.

Closes gaps elsewhere

TBM 432: Bundling & Unbundling Capabilities (and AI) · g1 — TBM 432's open gap asks what determines whether a capability motion tips toward useful adaptation or harmful instability, listing 'psychological safety' among unexamined candidate factors. TBM 431 supplies Cutler's own explicit candidate answer at the level of AI adoption generally: the Social Contract (whether gains will be captured against the people who generated them) -- though this is Cutler's asserted hypothesis, not empirically adjudicated, so the gap is narrowed rather than fully closed.