Carl Jacobi was a 19th-century German mathematician who built a career solving problems others couldn't by doing one thing consistently: reversing them. When a problem resisted direct attack, he'd flip it. Prove the opposite. Solve for failure. The phrase he repeated to students — man muss immer umkehren — translates roughly as "invert, always invert."

Charlie Munger encountered this principle and made it a cornerstone of his mental model library. His version: when you want to know how to succeed at something, first make a list of how you'd guarantee failure. Then avoid everything on the list. The power isn't insight — it's the asymmetry. Our minds are better at seeing what goes wrong than at generating what goes right. Inversion uses that asymmetry.

For practitioners, the question is: what would guarantee your next session fails? Start there. The answer is usually more specific and actionable than its positive version.

Marcus Aurelius wrote his Meditations as a private practice — never intended for publication — and the practice was essentially structured inversion. Before each day, he rehearsed what might go badly. Premeditatio malorum: the premeditation of evils.

This was not pessimism. The Stoics were explicit: the point was not to dread bad outcomes but to strip them of surprise. When you've already considered that the meeting will run long, the participant will be hostile, the projector will fail — those things lose their power to derail you. You've already been there.

For practitioners, this is a pre-session protocol. Five minutes before you walk in: what could go wrong? Projector fails. Energy in the room is low. A participant challenges the premise in the first ten minutes. Now: what's your actual response? Not a plan — a disposition. Inversion makes you present to the actual room, not the ideal one.

Atul Gawande documented the origins of the surgical checklist in The Checklist Manifesto, tracing it to aviation. The aviation checklist wasn't designed around "how do we ensure a good flight?" It was designed around a single prior question: "what conditions cause planes to crash?" Then the checklist was built to prevent each of those conditions, one item at a time.

This is pure Jacobi. The checklist is an inverted failure analysis institutionalized as daily practice. It doesn't ask crew members to remember excellence. It asks them to confirm the absence of known failure modes.

Gawande's research found that when the same logic was applied to surgery, complications fell 36% and deaths fell 47% across eight hospitals. The inversion was doing the work, not the items on the list.

Robert and Elizabeth Bjork's research on "desirable difficulties" in learning is best understood through inversion: what conditions reliably guarantee that people forget what they've been taught?

The list is specific. Massed practice (studying the same thing repeatedly in one sitting) — forgotten within days. Recognition testing (multiple choice) versus recall testing — dramatically lower retention. Immediate feedback with no delay — reduces long-term recall. Smooth, comfortable, un-interrupted practice — feels effective, produces forgetting.

The inversion is striking: the conditions that feel like learning often guarantee forgetting. The conditions that feel difficult — spaced repetition, interleaving, delayed feedback, effortful retrieval — produce durable retention. Practitioners who design for comfort are, unknowingly, designing for forgetting.

Robert Kegan and Lisa Laskow Lahey's immunity to change framework is, structurally, an inversion exercise. The protocol asks people to name their improvement goal, then — through a series of inversions — surface the competing commitment that's actually winning.

The diagnostic question: what are you doing, or not doing, that is working against your stated goal? Then: if you imagine doing the opposite of those things, what worries or discomforts arise? Then: what does that worry protect? What is the competing commitment? Then: what big assumption would have to be true for that competing commitment to make sense?

The inversion is finding the second competing goal that's opposing the first — usually an identity-level assumption ("if I speak up in meetings, I will be seen as aggressive; if I am seen as aggressive, I will lose the relationships that matter to me"). The assumption lives below awareness until inversion surfaces it.

For practitioners working on in-person presence: the competing commitment is often comfort — their own or the group's. The big assumption beneath it: if I create real discomfort, I'll lose the room. Invert it: what if the discomfort is the thing that creates the presence?

In-person presence is not the same as in-person delivery. A practitioner can be physically in the room and entirely absent — attending to slides, to agenda, to what's coming next. Presence is the quality of contact between practitioner and participant at any given moment.

The inverted question: what conditions reliably destroy presence?

Agenda-checking: when you're tracking time against plan, you're not in the room. Evaluation anxiety: when you're monitoring how the session is being received, your attention is split between the participants and their imagined reaction. Content delivery mode: when your job is to get through material, participants feel processed, not met. Premature problem-solving: when a participant raises a concern and you immediately respond with a framework, you've prioritized your map over their territory.

The inversion of all of these: presence is produced not by doing more, but by subtracting — agenda, evaluation, content mode, premature solution — until the actual room can be seen.

The first operating principle of Meliorism 2.0: Subtract before you add. This is inversion formalized as a design ethic. Before introducing anything new — a framework, a tool, a module — ask first: what are the things we're doing that guarantee the outcome we don't want? Remove those first.

The additive instinct is nearly universal in organizations: the answer to poor training is more training. More content. More assessments. More touchpoints. Each addition increases complexity. Complexity is a last resort — not a default response to failure.

The inverted question for every design decision: if this doesn't work, what am I adding that might be the problem? Addition creates interference. Subtraction creates space. And space is where learning happens.