The Compound Interest of Failure

You know the feeling. A project ends badly and there’s this brief window — a week, maybe two — where you can feel exactly what went wrong. The assumption that was load-bearing. The relationship that held. The thing you built that worked even though everything around it didn’t. Then the window closes. The next thing starts. The residue evaporates.

Thorfinn Karlsefni lived that window for a decade.

He spends the first arc of Vinland Saga doing one thing: trying to kill Askeladd. Years of his life, burning in a single direction. Every fight, every mission, every sleepless night on a Viking warship pointed at one man. He fails. Askeladd dies by someone else’s hand. Thorfinn’s entire purpose collapses.

From the outside, those years were pure waste. A teenager consumed by rage, accumulating nothing but scars.

Except that’s not what happened.

During those “wasted” years, Thorfinn learned how warriors think. How armies move. How power works at every scale, from the personal to the political. He learned dozens of languages from raiding across Europe. He learned the full anatomy of the thing he would later dedicate his life to dismantling. The revenge years didn’t succeed. But their residue compounded into the foundation of everything that came after. When Thorfinn becomes a pacifist leader in the Baltic Sea arc, he can negotiate with warlords because he was one. That capability wasn’t planned. It accumulated. And it compounded.

The Math of Compound Residue

Compound interest is the most celebrated passive force in finance. Leave a dollar alone, and time does the heavy lifting. Your money makes money that makes money. Everyone understands this when it’s money.

Almost nobody realizes that failure compounds the same way — with one critical difference: a capture rate.

Most people have a capture rate near zero. A project fails. They feel bad for a week. They “move on.” The lessons evaporate. The relationships built during the project dissolve. The patterns observed but never recorded disappear into the noise of the next thing. Their R₀ might be high — the failure might have been rich with insight — but a capture rate of 0.05 means that richness decays to nothing within a few cycles.

Compare that to someone with a capture rate of 0.6. Same failure. Same initial residue. But after five cycles, their accumulated insight is roughly 8× larger — and the gap widens every cycle. Not because they failed better. Because they captured better.

Over ten years, that gap looks like luck. It isn’t.

The Post-Mortem That Actually Works

You know what the blank post-mortem doc looks like. You open it three days after the project ends, stare at it, close it. You run the “good learnings” retro where nobody really meant it. You archive the Slack thread. Box checked. Capture rate: roughly zero.

The operators who actually compound from failure extract three specific things before the window closes. The post-mortem isn’t about the failure. It’s about what you left in it.

The pattern that worked even though the project didn’t. Every failed project has components that functioned — a marketing angle that resonated, a technical approach that solved a real problem, a team configuration that produced unusual output. These patterns get buried under the narrative of failure. Extracting them is the highest-value capture activity.

The boundary condition that broke. Not “what went wrong” in the vague sense. The specific assumption that turned out to be load-bearing and incorrect. “We assumed enterprise buyers would self-serve at this price point.” “We assumed the co-founder wanted the same thing we wanted.” These boundary conditions, once identified, become permanent additions to your decision-making architecture. They transfer across domains.

Every failed project is a sorting function for your network. The people who stayed, who handled the collapse with grace, who didn’t disappear when things got hard — those are the people you build the next thing with.

When you extract all three systematically, your capture rate jumps. And the compounding begins.

Why Success Is a Worse Teacher

Success teaches you what worked. Failure teaches you where the edges are.

Knowing what worked is useful in the exact conditions where it worked. Change the conditions, and that knowledge becomes dangerous — it makes you confident in a playbook that only applies to a game you’re no longer playing.

Knowing where the edges are is useful everywhere. Boundary conditions transfer across domains. The insight “people say yes to pilots but no to contracts” doesn’t just apply to the industry where you learned it. That’s a human behavior pattern. It works in sales, partnerships, hiring, fundraising. Anywhere someone needs to commit.

Failure residue is more portable than success residue. Nassim Taleb’s Antifragile makes this case at length: the knowledge earned by being wrong is categorically different from the knowledge earned by being right. The people who have failed across multiple domains develop an almost uncanny ability to read new situations. They have a larger library of boundary conditions, and those conditions compound across contexts.

The Compounding Flywheel

Each failure’s captured residue feeds your preparation density (Densitas Praeparatio — Kairos II). Higher preparation density reduces your luck dependency. Lower luck dependency means more confident action at the 60% threshold (Audacia Bayesiana — Kairos III). More action means more outcomes. More outcomes means more residue to capture. The flywheel turns faster with each cycle.

The person operating it looks, from the outside, like someone who keeps getting luckier. They’re not. They’re compounding. And Cyclus Cognitus (Kairos VI) describes the timing layer — when in the cycle to deploy what you’ve accumulated. You’re building toward that now.

In a fragile system, waste is loss. In this one, waste is compost. Every failure feeds the next cycle. Every lesson compounds into the next decision. The only question is whether you’re capturing it or letting it evaporate.

Thorfinn didn’t plan for his revenge years to become useful. The transformation wasn’t intentional — it was context-forced, accumulated without design. What made those years compound wasn’t Thorfinn’s foresight. It was what the framework of his life extracted from him against his will. The post-mortem is the deliberate version of that. The active capture that Thorfinn never got to do, done on purpose.

Build your capture rate. The failures are going to happen regardless. The only variable is how much residue you keep.