Everyone has a version of it. The relationship pattern you swore you’d never repeat. The leadership habit that keeps derailing projects. The financial decision you’ve made — and regretted — three times running. You recognize the mistake after the fact, promise yourself “never again,” and then watch helplessly as the cycle restarts.
The frustrating part isn’t the mistake itself. It’s the repetition. If you were capable of learning — and you are — why does the same error keep showing up in different costumes?
The answer isn’t willpower, discipline, or intelligence. It’s that most people diagnose repeating mistakes at the wrong level. They treat a systems failure as a character flaw — and then wonder why self-criticism doesn’t fix anything.
The Real Reason Mistakes Repeat
Think of any outcome in your life as a formula. In Drago Dimitrov’s Instant Competence framework, every result can be expressed as Y = w1a + w2b + w3c + w4d — an outcome (Y) is the weighted sum of the variables (a, b, c, d) that produce it, each with its own weight (w) reflecting how much it matters.
When you make the same mistake repeatedly, what’s actually happening is that the same variables are set to the same values, producing the same result. Beating yourself up is like staring at the output on a calculator screen and wishing it were different — without changing any of the inputs.
The question isn’t “Why do I keep doing this?” The real question is: “Which inputs am I leaving unchanged?”
The Three Layers of Repeating Patterns
Most repeating mistakes operate on three layers, and people typically only address the surface one:
Layer 1: The Behavior (What You Did)
This is where most self-help advice lives. You procrastinated again. You lost your temper in a meeting. You said yes to a project you should have declined. The behavior is visible, obvious, and easy to label. But behaviors are outputs, not root causes.
Layer 2: The Trigger (What Set It Off)
Going one level deeper, you can often identify the circumstances that preceded the mistake. You were tired. You felt cornered. The deadline pressure was mounting. Trigger awareness is useful — it’s why therapists teach people to recognize emotional cues. But knowing your triggers and actually responding differently to them are two very different things.
Layer 3: The System (Why the Trigger Keeps Appearing)
This is where the real leverage is. The trigger keeps appearing because your environment, habits, and decision architecture are designed — often unintentionally — to produce it. You keep overcommitting because your system for evaluating new opportunities doesn’t account for existing obligations. You keep hiring the wrong people because your interview process rewards confidence over competence. You keep losing your temper in meetings because you schedule them when your energy is lowest.
The Instant Competence framework calls this HD Vision — the ability to see the system behind the symptom. Most people try to fix Layer 1 (the behavior) without ever examining Layer 3 (the system). It’s like mopping a floor while the roof leaks.
The Input-Output Chain You’re Not Seeing
One of the most powerful tools for diagnosing repeating mistakes is what Dimitrov calls the Input-Output Value Chain. Here’s how it works for personal patterns:
Every action you take has inputs (what went into the decision) and outputs (the results it produced). Those outputs then become inputs for the next decision. When this chain is invisible to you, feedback loops form — and not always helpful ones.
Example: A manager repeatedly loses their best team members. The visible mistake is “I didn’t give them enough recognition.” But tracing the input-output chain reveals something deeper:
- Input: The manager feels pressure to deliver results quickly
- Output: They focus exclusively on tasks, not people
- That output becomes input: Team members feel unseen and undervalued
- Output: Top performers disengage and eventually leave
- That output becomes input: The manager now has fewer capable people and even more pressure
- The cycle accelerates
The manager’s instinct is to “try harder to recognize people next time.” But the systemic fix is to redesign how they allocate their time and attention before the pressure builds — changing the input, not just resolving to produce a different output through sheer will.
Why Self-Awareness Alone Isn’t Enough
There’s a popular belief that awareness is the first step to change. It is — but it’s also where most people stop. You can be perfectly aware that you overeat when stressed, overcommit when flattered, or avoid conflict when uncomfortable. Awareness without a system change is just narrating your own downfall in real time.
The Instant Competence framework includes a tool called the No-Judgment Observation Layer that addresses this directly. The idea is to observe your patterns with the clinical detachment of a scientist studying a phenomenon — not to judge them, but to understand the mechanics.
Instead of “I’m so frustrated with myself for doing this again,” the no-judgment observation sounds like: “Interesting — the same sequence played out. The trigger was X, I responded with Y, and the result was Z. What variable could I change to get a different Z?”
This isn’t about suppressing emotion. It’s about separating the emotional reaction (which is natural) from the analytical work (which needs to happen without shame distorting the data). Self-criticism produces defensiveness. Observation produces clarity.
The Monitoring Failure: Why Good Intentions Die
Here’s something most personal development advice misses entirely: even when you identify the right change and implement it, the new behavior often decays within weeks. The Instant Competence 7-step decision process dedicates its entire final step — Step 7: Monitoring and Managing Implications — to this problem.
Most people treat a decision as a moment. Decide, act, move on. But a decision is actually the beginning of a process that requires ongoing monitoring. When you decide to stop checking email first thing in the morning, that decision needs a monitoring system: What will you do instead? How will you handle the discomfort of not checking? What happens when an urgent email arrives at 7 AM and you only see it at 9? How will you prevent gradual drift back to the old habit?
Without monitoring, every behavioral change follows the same arc: enthusiasm → friction → drift → relapse → self-blame. And self-blame is the least useful response, because it treats a monitoring failure as a moral failure.
Building a Personal Monitoring System
Effective monitoring doesn’t require complex tracking apps or journals (though those can help). It requires three things:
- A clear signal that drift is happening. Define it in advance. “If I’ve said yes to three unplanned commitments in a week, something is off.” “If I haven’t exercised by Wednesday, the week’s plan has failed.” The signal needs to be specific and early enough to correct course.
- A scheduled reflection point. A weekly 15-minute review where you ask one question: “Did the pattern show up this week, and if so, at which layer?” Not daily — that creates fatigue. Not monthly — that’s too late. Weekly is the sweet spot for most behavioral patterns.
- A pre-planned response. When the signal fires, what’s the next action? Not “try harder” — a concrete structural change. Move the meeting. Block the calendar. Change the default. Adjust an input variable.
The What-Does-It-Mean Test
One of the most clarifying questions you can ask about a repeating pattern is Dimitrov’s What-Does-It-Mean Laser: take the pattern and relentlessly ask “What does this actually mean?” until you hit bedrock.
“I keep procrastinating on important projects.”
What does that mean?
“It means I start too late and then rush.”
What does that mean?
“It means I consistently undervalue future consequences relative to present comfort.”
What does that mean?
“It means my decision-making system is calibrated to avoid short-term discomfort, even when I know the long-term cost is higher.”
Now you have something actionable. The fix isn’t “stop procrastinating” — it’s recalibrating how you weight short-term discomfort versus long-term cost. That might mean making the long-term cost more vivid (Dimitrov’s Movie/Concrete Visualization tool), or reducing the activation energy for starting (a systems change), or creating accountability structures that make short-term avoidance more uncomfortable than starting.
Five Questions to Break Any Repeating Pattern
Apply these to any mistake you’ve made more than twice:
- What are the actual input variables? Map every factor that contributed — not just the obvious trigger, but the environmental conditions, your state of mind, the timing, the preceding decisions. Use the Y = w1a + w2b formula to identify which inputs carry the most weight.
- Where is the feedback loop? Trace the input-output chain. Does the output of this mistake create conditions that make the next occurrence more likely? If so, you’ve found an amplifying loop that will only get worse.
- What would I see if I watched someone else do this? Apply the No-Judgment Observation Layer. Remove yourself from the emotional center and observe the mechanics. What would you advise a friend who showed you this pattern?
- Which input is easiest to change? You don’t need to overhaul everything. Identify the single variable with the highest weight-to-effort ratio — the one change that would most disrupt the pattern with the least resistance.
- What’s my monitoring signal? Define the early warning sign that the old pattern is reasserting itself. Make it specific, observable, and early enough to intervene before the full cycle completes.
From Self-Blame to System Design
The deepest shift in breaking repeating mistakes is moving from a moral framework to a systems framework. In the moral framework, repeating a mistake means you’re weak, undisciplined, or fundamentally flawed. In the systems framework, it means a variable is misconfigured — and variables can be adjusted.
This isn’t about letting yourself off the hook. It’s about putting yourself on a hook that actually works. Self-blame is a dead-end loop of its own. System design is engineering. And engineering gets results.
The Instant Competence framework’s core metaphor captures it well: stop trying to force the same broken key into the lock. Step back, examine the lock’s mechanism, and craft a new key that actually fits. You don’t need to be a different person. You need a different system.
Ready to Think Differently?
If you want to bring systems thinking and AI strategy into your organization, book a call with Drago. Or start with the free Clarity Worksheet from Instant Competence — the thinking framework behind every concept in this post.