Systems map of a life

Every article in this series so far has handed you a piece of the systems thinking toolkit: stocks and flows, feedback loops, bottlenecks, archetypes, leverage points, and the discipline of mapping a system well instead of just decorating a diagram. This article puts all of it to work on the system you know best and think about least clearly—a single human life.

To keep this concrete, we're going to follow one person through it: Dan.

Dan is in his mid-30s, works a full-time job, and has the usual mix of responsibilities—some work stress, some relationships to maintain, a body that needs looking after, and never quite enough hours in the day. He's not in crisis. He's just… busy, a little tired, and vaguely aware that something about how he's living isn't sustainable, without being able to name what.

Notice how little that tells you. No job title, no relationship status, no specific vice. That's on purpose. Dan isn't a character study—he's a stand-in. The less specific he is up front, the more likely it is that his map ends up looking like yours.

Why map a person instead of an organization?

Most systems thinking writing—including the case study earlier in this series—uses organizations, supply chains, or ecosystems as the example. That's useful, but it keeps systems thinking feeling like a professional tool you pick up at work and put down at 5pm. The truth is that the same structures—stocks that deplete and refill, loops that reinforce or balance, delays that hide consequences, archetypes that repeat—are running underneath your own life right now, mostly invisibly, mostly unmanaged.

Dan's life isn't a metaphor for a system. It is one. It has stocks (energy, trust, savings, health). It has flows (hours spent, calories burned, goodwill earned and spent). It has feedback loops that either compound in his favor or quietly work against him. Mapping it isn't a self-help exercise dressed up in diagrams—it's applying the exact same rigor you'd apply to a supply chain, aimed at the one system you actually live inside.

Three loops, three time scales

A life doesn't run on one loop. It runs on several, nested inside each other, operating at very different speeds. Confusing them is one of the most common mapping mistakes—you try to fix a slow-moving identity problem with a fast-moving willpower tactic, and wonder why it doesn't stick. So we'll separate Dan's life into three layers: daily, monthly, and life-arc.

Loop	Time scale	What it governs
Energy/Coping Loop	Daily	Stress, recovery, and how Dan spends his depleted evenings
Competence/Confidence Loop	Weeks–months	Performance, feedback, and how much Dan invests in himself
Identity/Life-Arc Loop	Years	The story Dan tells himself about who he is and what's possible

Loop 1: The Energy/Coping Loop

This is the loop Dan lives inside every single day, and the one he's most aware of—while understanding it least.

Work demands draw down a stock: call it Energy, or Willpower, or Recovery Capacity. It isn't infinite, and it doesn't refill itself just because the day ends. When that stock runs low, Dan reaches for a Coping Choice—something fast and reliable: the couch, the phone, a second drink, a late-night snack. In the moment, this works. Comfort goes up. That's not an illusion; it's real relief.

But the coping choice also crowds out the slower, harder things that would have actually refilled the stock—sleep, exercise, a real conversation, quiet. So Energy stays low, which makes Dan more likely to reach for the same fast relief tomorrow, which crowds out recovery again. The loop closes on itself.

This is a textbook Shifting the Burden archetype. There's a symptomatic solution (quick coping) and a fundamental solution (actually rebuilding capacity), and the symptomatic solution is faster and easier, so it gets chosen—repeatedly—while the muscle for the fundamental solution quietly weakens from disuse. Dan isn't failing to fix his life through some lack of character. He's caught in a structure that rewards the wrong lever every single time he's tired enough to reach for one.

Loop 2: The Competence/Confidence Loop

Zoom out from days to months, and a second loop appears, built on top of the first.

Dan's Energy level affects his Performance—at work, in relationships, in the gym, wherever he shows up. Performance generates Feedback, from others and from himself: a good quarter, a strained friendship, a missed workout streak. Feedback shapes Confidence—his working belief about whether he's someone who's on top of things or someone who's falling behind. And Confidence determines how much he's willing to invest in the fundamental fixes from Loop 1. Believing change is possible is itself a resource, and it's one this loop can build up or drain.

This is where Success to the Successful shows up. Two people can start from nearly the same place. One gets an early win, invests a little more, gets a slightly better result, invests more—a virtuous spiral. The other gets an early setback, disengages a little, gets a worse result, disengages more. Same starting conditions, diverging trajectories, purely from which way the loop tipped first. This is also why timing matters more than most people assume: a small intervention early in this loop is worth far more than a large intervention late in it, once the spiral has had months to compound.

Loop 3: The Identity/Life-Arc Loop

The slowest, quietest loop sits underneath both of the others.

Every time Dan cycles through Loops 1 and 2, the outcome leaves a residue—a small update to the story he tells himself about who he is. Enough cycles of depleted evenings and slipping confidence, and the story hardens: I'm someone who doesn't have time for himself. I'm someone who always burns out eventually. Enough cycles the other direction, and a different story hardens: I'm someone who follows through.

That story isn't just a description—it becomes a constraint. It quietly caps what Dan even attempts in Loops 1 and 2. He doesn't consciously decide not to try the fundamental fix; the identity story has already decided the outcome before the day starts, by determining what feels like "the kind of thing Dan does." This is Donella Meadows' highest-leverage point—the paradigm a system is built on—operating at the scale of a single person, and it's exactly as hard to see here as it is in any organization, for exactly the same reason: it's the water everything else swims in.

Where people intervene, and where the leverage actually is

Here's the payoff of drawing this out as a map rather than just describing it in prose: it shows you where Dan (and probably you) instinctively push, versus where the structure would actually bend.

The default move is to intervene in Loop 1, at the lowest-leverage point available—a parameter tweak. Try harder. Use more willpower. Cut out the coping behavior through sheer resolve. This occasionally works for a few days and almost never holds, because it treats the symptom (the coping choice) without touching the structure that keeps generating the need for it (the depleted stock, the absent fundamental fix, the story that says this is just how Dan is).

Higher-leverage moves sit elsewhere on the map:

• Redesign the loop, not the willpower. Make the fundamental fix as low-friction as the coping behavior—laying out gym clothes the night before, pre-deciding the evening's first move before Energy is already gone. This is a structural change, not a motivational one.
• Intervene early in Loop 2, not late. A small win, deliberately manufactured and noticed, is worth more in week one of a slide than a large effort in month six, because it changes which direction the spiral is already bending.
• Touch the paradigm in Loop 3 directly. This is the hardest and highest-leverage move of all—consciously naming and contesting the identity story itself, rather than waiting for enough small wins to erode it by accident. It's also the move almost nobody makes, because it's the least visible lever in the whole system.

None of this is a claim that Dan's life is simple enough to fully diagram, or that one map settles what he should do next. A map is a model, and a model is always a simplification—that's the point of it, and also its limit, as the earlier article on mapping discipline covered. What the map does is make the structure visible enough to argue with. Before mapping it, Dan's stuckness feels like a personal failing. After mapping it, it looks like what it actually is: a small number of loops, running at different speeds, that reward the wrong lever by default—and can be redesigned once you can see them.

That's true of Dan. It's very likely true of you too.