actors ⇄ incentives ⇄ constraints ⇄ feedback
A story explains. A mechanism predicts. Only one of them can be tested.
The situation stops being about who is at fault and starts being about what the arrangement rewards.
The same outcome recurs with different people in the same arrangement.
The arrangement, not the personalities, is producing the outcome.
Changing one constraint changes the outcome more reliably than changing the actors.
"I keep messing things up." Complete, emotional, immovable.
Too many inputs open → attention splits → error → frustration → more inputs.
Names a person.
Names a variable you can move.
What could produce this?
Describe it so plainly it sounds boring. If it sounds insightful, it is probably still a story.
What relationships produce the outcome?
Follow the feedback: what does this result make more likely next time?
Does the pattern change when zooming out?
If the same failure appears across unrelated contexts, the cause is structural.
A team keeps missing deadlines. Everyone agrees they need to "communicate better."
Name the actors, their incentives, the constraints, and the feedback loop.
Actors: whoever commits to dates, and whoever absorbs the overrun.
Incentive: committing optimistically is rewarded now; the cost lands later, on someone else.
Feedback: the overrun is absorbed quietly, so the next estimate is just as optimistic.
Nobody communicated badly. The arrangement paid for optimism.
Most people explain their lives through stories ("I'm anxious," "This always happens"). Stories feel true, but they hide the mechanics of what's actually happening. This model is about seeing the system underneath the story. A story is a simple, emotional explanation. It feels complete, but it offers no room to move. A system is a step-by-step process: A leads to B, which causes C. Once you see the system, you can find a place to intervene.
Moving from a personal label to an observable process.
The Story:
"I keep messing things up."
The System:
You can't debug a story. You can debug a system. Stories often lead to feelings of helplessness ("This is just how I am"). They are identity-level declarations that offer no path forward. Systems thinking reveals leverage points. By seeing the pattern as a machine, not a personality trait, you can identify which part of the process to change—the trigger, the state, the response. This creates space for action.
The goal is to see the mechanical reality, not to find a more sophisticated-sounding story. If your "system analysis" sounds like a psychological diagnosis or a complex narrative, it's probably still a story. A true system description is boring, observable, and almost machine-like. "When X happens, Y follows."