← Back to the method overview
The Premise — Deep Dive

The physics under Maxeneur, MAX10, and the MAXED drill.

Success = Integration ÷ Entropy

The job the formula actually does

Most business frameworks tell you what to look at. This one tells you what a business fundamentally is: an energy system trying to capture more value from its environment than it burns internally getting anything done.

  1. Integration (numerator) — the value the system captures by fitting itself to its environment. Capability aligned to opportunity. Strategy realised, not strategy written. Maximise.
  2. Entropy (denominator) — the internal friction of the system. Rework, misalignment, politics, waiting, ambiguity, disorder. The tax every unit of effort pays before it reaches the outside world. Minimise.

The formula's power is that it holds both halves in one expression. Most leaders carry only one:

Neither is wrong about their half. They're wrong about the ratio. The formula forces you to hold both numbers in your head at once — which is precisely the job of the operator.

Attribution, stated once and honestly: the formula and the PSIU forces come from Lex Sisney's Organizational Physics, building on Adizes. The refinements marked Maxeneur refinement below — most importantly "operations is the lever on the denominator, not the denominator" — are Maxeneur's own constructions. Defensible, but not the textbook.

Why a ratio — the part everyone skips

The formula could have been written Success = Integration − Entropy. It wasn't, and the difference is the whole insight.

Subtraction says friction is a fee. Division says friction is a discount rate.

If entropy merely subtracted, you could outgrow it — pile on enough integration and the friction becomes a rounding error. Every scaling startup believes this, and every scaling startup discovers it's false. Entropy doesn't sit beside your output; it divides it. Every unit of strategic value passes through the internal machine, and the machine takes its cut on the way through.

The arithmetic of the operator

Run the numbers and the operator's case makes itself:

MoveBeforeAfterSuccess
Baseline100 ÷ 425
Heroic strategy win: numerator +30%100 ÷ 4130 ÷ 432.5 (+30%)
Quiet operations win: denominator −25%100 ÷ 4100 ÷ 333.3 (+33%)
Both100 ÷ 4130 ÷ 343.3 (+73%)

A 25% entropy reduction beat a 30% integration gain — and entropy reductions are usually cheaper, because you're not fighting a market for them. Nobody outside the building contests your right to remove rework. The market contests everything on the numerator.

And the two moves multiply. That's the real argument for owning the denominator: every point of friction you remove multiplies whatever the strategy can deliver — this quarter's strategy and every future one. Same strategy, less entropy, more success. Maxeneur refinement

The asymmetry of decay

One more property of division: as entropy grows, success doesn't decline linearly — it collapses. 100÷2 = 50. 100÷4 = 25. 100÷8 = 12.5. Each doubling of internal friction halves the business at constant strategy. This is why organisations feel fine, feel fine, feel fine, then suddenly feel broken: the denominator compounds quietly, and division hides its work until it doesn't.

🧪 Test — do you actually believe the ratio?

In your last planning cycle, did denominator initiatives (friction removal) get first-class status alongside numerator initiatives (growth), with owners and dates? Or were they "when we get time"?

If entropy work is scheduled for "when we get time," you believe in subtraction, whatever you say in the room.

The numerator — Integration

What it is

Integration is fit, converted into captured value. It has two faces, and both must be true at once:

FaceQuestionLooks likeOwned by (PSIU)
External integrationDoes the system fit its environment?Product-market fit; services people actually want; sensing what's changing outside; adapting before being forced toP (produce now) + I (adapt for later)
Internal integrationDo the parts fit each other?Teams pulling one direction; decisions that stick; strategy legible at every level; handoffs that don't leakU (cohesion)

Miss the first and you're a beautifully aligned team building the wrong thing. Miss the second and you're ten brilliant people producing the output of three. The two faces multiply within the numerator — external opportunity × internal alignment. A 10/10 market insight executed by a 3/10-aligned organisation captures 3, not 10.

Draw the lines hardWhat integration is NOT

How to raise itThe levers

  1. Legibility. Can a person three levels down predict what leadership would want in an ambiguous situation — and be right? That prediction accuracy is internal integration, in one number. Everything else (OKRs, BSC, comms cadence) is machinery for raising it.
  2. Sensing. External integration decays because the environment moves and the org doesn't notice. Build deliberate outside-in feeds: customer contact for executives, win/loss reviews, competitor watch, regulatory horizon-scanning. The MAX10 domains that face outward (Customers, Revenue, Risk) are your sensing organs — if their Metrics are all internal numbers, you've blinded them.
  3. Decision rights. Integration lives or dies at decision points. Ambiguous authority (see the Delegate levels in the MAXED deep dive) fragments direction faster than bad strategy does — because every unowned decision gets made three different ways in three different rooms.
  4. Kill lists. Integration is as much about what you stop as what you align on. Every zombie initiative pulls people slightly off-axis. The Stop decision type in Execute is a numerator tool.

Watch forFailure modes

🧪 Max-out test for Integration

External: if your three biggest customers described what your business is for, would their answer match your strategy page?

Internal: pick a mid-level decision made last week without you. Did it land where you'd have landed it?

The denominator — Entropy

What it is

Entropy is the organisational expression of the second law: left alone, every system drifts toward disorder. Not because people are lazy or stupid — because disorder is the default state and order is the thing that costs energy. An organisation is a low-entropy structure maintained against constant decay, the way a body is. Stop spending maintenance energy and you don't stay where you are; you slide.

Three properties follow, and each one is operationally load-bearing:

  1. Entropy is nobody's fault. It accumulates from normal, well-intentioned activity. Every hire adds coordination surface. Every product adds interfaces. Every win adds process to protect the win. This matters because leaders who treat entropy as culpable go hunting for villains and find scapegoats — which adds political entropy to whatever entropy they started with.
  2. Entropy is invisible line-by-line. No single meeting is the problem. No single approval step is the problem. The denominator is made entirely of things that were each, individually, reasonable. That's why it needs instrumentation rather than intuition — intuition approves every increment.
  3. Growth manufactures entropy. This is the cruellest one: the numerator's victories feed the denominator. Scaling from 10 to 50 people can triple integration and quintuple entropy, and the org feels more successful while the ratio quietly falls. Every growth plan should carry an entropy budget line. Maxeneur refinement

A working taxonomyThe five entropy channels Maxeneur refinement

You can't reduce what you can't name. In practice, organisational entropy runs through five channels:

ChannelWhat it isSymptomsPrimary reducer
StructuralWork shaped wrong: unclear roles, duplicated functions, handoffs that leak, approval chains grown like coral"Who owns this?"; things done twice; things done neverOrg design, RACI, decision rights
InformationalTruth is expensive to obtain: data scattered, stale, contradictory; the same question answered three waysMeetings that exist to establish facts; report-building as a jobSingle sources of truth; the M in MAXED
DecisionalDecisions delayed, revisited, or made ambiguouslyThe same debate quarterly; "I thought we agreed…"; escalation as defaultDecision types + authority levels (the E and D in MAXED)
TechnicalSystems friction: legacy debt, manual re-keying, workarounds, shadow ITSwivel-chair processes; heroic spreadsheets; "don't touch that server"Platform investment, automation, retirement of the old
Political / emotionalTrust deficits priced into every interaction: hedging, CYA email, pre-meetings, information hoardingThe meeting after the meeting; decisions relitigated in corridorsPsychological safety + visible consequence for gaming — soft and hard together

Two notes on the taxonomy:

The floorMinimum viable entropy Maxeneur refinement

Here is the nuance that saves the formula from becoming a tyranny: entropy cannot and should not go to zero.

Some disorder is the price of adaptation. Slack in the schedule, experiments that fail, duplicated exploration, the messy edge where new capability is being learned — mathematically these are all entropy, and strategically they're the seed corn. An organisation optimised to zero internal friction is an organisation that has purchased efficiency with fragility: perfectly adapted to today, incapable of becoming anything else. This is the PSIU tension in formula terms — S (stabilise) reduces entropy, but S taken to its maximum strangles I (innovate), and you've minimised the denominator by amputating the future numerator.

So the operator's question is never "how do we eliminate entropy?" It's:

"Is this friction purchased or accumulated?"

Purchased friction bought something — resilience, learning, optionality, control that a regulator genuinely requires. Accumulated friction bought nothing; it's sediment. The kill list is for sediment. The budget is for purchases. Most organisations can't tell you which is which, and that inability is itself informational entropy.

Watch forFailure modes

🧪 Max-out test for Entropy

Name your organisation's three largest entropy sources, by channel, with a number attached to each.

If you can't, you're managing the denominator by feel — and feel approves every increment.

The critical refinement: operations is the lever, not the denominator Maxeneur refinement

The tempting gloss is Success = Strategy ÷ Operations. It's half right, and the wrong half cuts against everything above.

Integration ≈ strategy: fair. Strategy is exactly the work of aligning capability to external opportunity — a good one-word gloss on the numerator.

Entropy = operations: no — and the error matters. Entropy is the friction inside the system. Operations, done well, is precisely what removes it. A well-run operation is a low-entropy engine. Map operations onto the denominator and you've cast the operational function — service management, delivery, governance, the whole discipline — as the bad number to be minimised. Which leads directly to the most common act of organisational self-harm: cutting operations to "reduce cost," watching entropy bloom in every channel at once, and booking the collapse of the ratio as a market problem.

The clean model:

Success = value captured externally (strategy) ÷ internal friction (entropy)
Operations is the hand on the denominator.

This reframe changes who the operator is in the success equation. Not the cost centre. Not "keeping the lights on." The multiplier: every unit of friction removed multiplies whatever the strategy — this one and every future one — can deliver. The strategist proposes the numerator; the operator owns the denominator; and because the relationship is division, the operator's work compounds across everything the numerator ever does.

Two kinds of win follow, and every initiative should declare which it is:

  1. Integration wins — raise the numerator. New capability, new market fit, new value captured.
  2. Entropy wins — lower the denominator. Friction removed, decisions unstuck, systems retired, truth made cheap.
🧪 Test

Does your initiative register / project list carry a "Lever" column — every item tagged Integration or Entropy?

If everything tags Integration, the denominator is unmanaged. If nothing does, the formula isn't actually in use.

The dynamics — how the ratio behaves over time

The formula is a snapshot; businesses live in time. Four dynamic laws:

1

The denominator grows by default; the numerator decays by default. Entropy accumulates without anyone acting (second law). Integration erodes without anyone acting (the environment moves; internal alignment drifts as people and priorities change). So the ratio's natural trajectory — under zero management — is down on both ends. "Maintaining" a business is not a passive verb. This is the deep justification for a weekly cadence: Monday MAX is the scheduled energy injection that the second law makes mandatory. Skip it for a quarter and you haven't paused; you've slid.

2

Every numerator win invoices the denominator. New product → new interfaces → structural entropy. New market → new complexity → informational entropy. New hires → new coordination → all five channels. The invoice arrives 1–2 quarters after the win, which is exactly when the org has moved its attention to the next win. Mature operators book the entropy cost at decision time: "this expansion costs $X and roughly this much denominator — here's who owns paying it down."

3

The ratio turns before either term does. Integration can still be rising while entropy rises faster — output up, success down, and every individual dashboard green. This is why the formula needs to be watched as a ratio, and why growth phases are the most dangerous: they're the only time the org is anaesthetised against denominator pain by numerator pleasure.

4

Entropy reduction has a half-life. Friction removed grows back — the approval step you deleted reappears wearing a different name within a year, because the anxiety that created it wasn't addressed, only its artefact. Entropy wins need maintenance owners, not just project owners. (Delegate levels 4–5, with a trip-wire on the metric that the win improved.)

Misreadings — how the formula gets abused

Worth naming, because a formula this quotable will be misquoted:

MisreadingWhy it's wrongThe tell
"Entropy = operations"Covered above — casts the fix as the diseaseOps budget cut in the name of "efficiency," ratio falls
"Entropy = people being difficult"Dissent and friction aren't the same. Dissent surfaces information; suppressing it converts loud cheap entropy into quiet expensive (political) entropyThe org gets quieter and slower simultaneously
"Zero entropy is the goal"Kills slack, learning, and adaptation — minimises the denominator by executing the future numeratorNothing new has shipped in a year; one resignation is a crisis
"Integration = everyone agrees"Agreement without fit is synchronized errorHarmony high, market share falling
"It's a formula, so measure it to two decimals"It's a lens, not an accounting identity. The terms are proxied, not counted. False precision breeds gamingA "Success Score: 3.7" slide, and behaviour optimising the proxy
"Success is only this"The formula describes organisational success — capacity to capture value. It says nothing about whether the value is worth capturing. Purpose sits outside the equationA high-ratio business everyone hates working in / buying from

That last row matters: the formula is the physics, not the ethics. It tells you whether the engine is efficient, not where to drive. Purpose sits upstream of the equation.

Measuring it — proxies, not decimals

Neither term is directly countable. Both are very trackable through proxies — and MAX10 is, structurally, the instrument.

Integration proxies

ProxyFaceReads
Revenue per FTE, trendExternalValue captured per unit of system
Net revenue retention / repeat rateExternalThe environment voting on fit
Win rate on qualified opportunitiesExternalStrategy meeting market, at the coalface
Strategy legibility check — 5 people, 3 levels: "what are our top 3 priorities?" — count distinct answersInternalDirection actually propagated
% decisions that stick (not reopened within 90 days)InternalAlignment at decision points
MAX10 Priorities close-out rate (last week's top 5)InternalStated intent converting to action

Entropy proxies

ProxyChannelReads
Cycle time: decision → doneDecisional/StructuralTotal internal friction, end to end
Rework % / change-failure rateTechnical/StructuralWork paying the friction tax twice
Meeting hours per FTE per week, trendInformational/PoliticalCost of establishing truth and trust
Time-to-answer for a standard factual question ("what did we sell last month, by product?")InformationalPrice of truth
Approval steps on the five most common processesStructuralSediment count
CEO Action Share (from the MAXED deep dive)Structural/DecisionalLoad-bearing on one person = concentrated entropy risk
Zombie actions (rolled 3+ weeks)DecisionalDecisions that didn't decide
Unplanned work %AllThe system interrupting itself
The dashboard is the ratio's trend, not its value. Pick 3 integration proxies and 3 entropy proxies, baseline them, and watch direction quarterly. The moment someone asks for the combined score to two decimals, re-read the misreadings table.

How MAX10 / MAXED instruments the equation Maxeneur refinement

This is the through-line that makes Maxeneur one system rather than three ideas:

  1. MAX10 is the sensor array — ten domains reporting weekly. The RAG heat grid over time is a low-resolution image of the ratio: reds clustering and persisting = denominator winning.
  2. MAXED is the entropy pump — each letter converts a specific ambiguity into order (what's true → what matters → why → what we're doing → who owns it). Ambiguity is entropy in its purest organisational form; the drill removes it in five staged extractions, weekly, per domain.
  3. The contamination links (X-Ray) map the entropy cascades between domains — the causal spine.
  4. The Depth Score measures whether the pump is actually pumping or just cycling.
  5. Weekly Alignment (top 5 / top 3 priorities) is the integration mechanism — the numerator's weekly maintenance, matching the denominator's.

One session, both terms serviced.

Worked examples

The telco audit Entropy win, pure

Same telco capability before and after; ~39% of annual cost removed. Numerator untouched, denominator cut — the ratio rises with zero strategy risk, zero market permission required. This is the archetype of the operator's win: invisible to the customer, material to the equation.

The platform migration Integration win, with an entropy dividend

Legacy telephony replaced with a modern platform (Operator Connect): external integration up — capability aligned to where the environment already moved — and technical entropy down, with workarounds and legacy friction retired. Wins that score on both terms are rarer and worth flagship status; they're what "modernisation" means when the word is being used honestly.

The scaling startup Numerator victory, ratio defeat

10 → 40 people in a year; revenue 2.5×. Feels like triumph. But coordination surface grew combinatorially: informational entropy (nobody's numbers agree), structural (three people own nothing and everything), political (factions form in the vacuum). Integration ×2.5, entropy ×4 → the ratio fell ~35% during the most "successful" year in company history — which is why year two feels inexplicably harder than year one. The formula explains what the P&L can't.

The over-stabilised function Denominator victory, numerator defeat

A unit that has spent a decade perfecting control: every process documented, every change gated. Entropy, measured naively, is superb. But I was strangled by S — the environment moved (cloud, cyber, community expectations) and external integration quietly rotted behind the immaculate process. The ratio fell while every internal metric glowed. The fix isn't more control and isn't a bonfire of process — it's re-weighting the PSIU forces and distinguishing purchased friction from sediment.

The PSIU forces as the equation's crew

The clean mapping — each force manages one corner of the formula:

ForceHorizonWorks onIn formula terms
P — ProducingNowExternalConverts today's fit into captured value — numerator, present tense
I — InnovatingLaterExternalMaintains fit with a moving environment — numerator, future tense
S — StabilisingNowInternalOrder, repeatability, control — denominator, present tense
U — UnifyingLaterInternalCohesion, trust, shared direction — denominator (political channel) and internal-integration numerator

The classic tensions read straight off the table: P vs I is this quarter's numerator vs next year's; S vs I is denominator control vs the disorder that innovation requires; and U is the only force working both terms at once — which is why its absence is the most expensive and the least noticed. An unbalanced crew doesn't fail randomly; it fails in the corner of the formula nobody is standing in.

The one-breath versions

The operator's version
"Success is what you capture externally divided by what you burn internally. Strategy proposes the numerator; I own the denominator — and because it's division, every unit of friction I remove multiplies everything the strategy delivers."
The homepage version
"Your business is an engine: value captured, divided by friction burned. Maxeneur instruments both numbers — and gives you the weekly ritual that moves them."
The Academy version
"Entropy is not your fault, but it is your job. It grows while you sleep, it hides inside your wins, and it divides everything you build. The operator's craft is naming it, channel by channel, and pumping it out — weekly, forever."
The Exit Gate

The MAXED-style definition of done

You are actually using the formula — not quoting it — when all five hold:

The physics, applied — weekly.

MAX10 senses both terms. MAXED pumps the entropy out. The coaching journey builds the numerator.

The MAXED deep dive Explore the Maxeneur method