When fixing the symptom makes the problem worse


Hello Reader,

You schedule two-hour blocks for deep work. Twenty minutes in, you're answering Slack messages.

You try again tomorrow. Same result. You download a focus app, turn off notifications, and move to a quiet room. Thirty minutes this time, then you're back in reactive mode.

You adjust your tactics—using better tools, stricter rules, and more discipline. But the pattern persists.

Most people would continue to tweak the execution. That's single-loop learning: fixing the symptoms without examining the beliefs that generate them.

The double-loop fix: question the assumption. You're operating under the belief that "I need to be available when people need me," but that belief is destroying your capacity for deep work. The assumption driving your behavior is inherited from an old job, an old manager, an environment that rewarded responsiveness over depth.

Rewrite the assumption: "I create value by protecting focus, not by being responsive." Now redesign your behavior. Block your calendar. Set clear response windows. Redirect urgent requests to specific channels.

Here's what most people miss: they're trapped in single-loop learning—adjusting actions within a framework they never chose.

Think of a thermostat. Temperature drops, heat turns on. Temperature rises, heat turns off. The thermostat corrects constantly but never questions the temperature setting itself.

That's single-loop learning: correction without examination.

Real learning happens when you question the framework itself. It's called double-loop learning, and it's the difference between working harder and thinking differently.

Why Use It

Most learning happens in one loop. We fix errors, refine tactics, optimize execution—all while our underlying assumptions stay invisible.

Single-loop learning asks: "How do I fix this?" Double-loop learning asks: "Why did this happen in the first place?"

The thermostat is the perfect analogy. When the temperature drops, the heat turns on. When it rises, the heat turns off. The thermostat adjusts its actions constantly—but it never questions the temperature setting itself.

That's single-loop learning: correction without examination.

Double-loop learning steps back and asks: "Is this the right temperature? Who set it? Does it still make sense?"

Here's the distinction:

In single-loop learning, you adjust actions. Your marketing campaign underperforms, so you tweak the copy. Your meetings feel unproductive, so you try a new agenda format. Your strategy isn't working, so you execute harder. You're solving the problem as defined—but never questioning the definition.

In double-loop learning, you transform thinking. You don't just tweak the campaign; you question whether you're targeting the right audience. You don't just fix the meetings; you examine whether meetings are the right tool for the job.

The practical insight: when facing persistent problems, don't just try harder. Examine your underlying assumptions.

Groundhog Day illustrates this perfectly. Phil Connors spends most of the film using single-loop learning—memorizing facts about the townspeople to manipulate them, learning card tricks and ice sculpting to impress Rita, adjusting his tactics within the same selfish framework.

None of it works. He's stuck in the loop.

His breakthrough comes when he questions his fundamental assumptions about what he actually wants and who he wants to become. He stops asking "How do I win this day?" and starts asking "What kind of person creates a day worth living?"

That's double-loop learning—transforming the problem-solver, not just solving the problem.

Real solutions often come not from better answers, but from better questions.

Here's what double-loop learning gives you:

Escape from persistent problems. When you keep hitting the same wall despite tactical adjustments, the issue isn't execution. It's the model. Your assumptions about the situation are incomplete or wrong. Double-loop learning surfaces them so you can redesign them.

Protection from inherited frameworks. You absorb beliefs from your environment without noticing—your manager's definition of productivity, your industry's assumptions about success, your culture's norms about how things work. These become your operating logic unless you deliberately examine them.

Clarity about what you're actually optimizing for. Getting better at the wrong thing is worse than doing nothing. Double-loop learning forces you to question whether the problem you're solving is the problem that matters.

This is how organizations and individuals break out of cycles that single-loop adjustments can't fix.

When to Use It

Use double-loop learning when you notice patterns that resist change.

You're improving without progressing. You refine your process, work harder, execute better—but outcomes stay flat. That's not a tactics failure. That's a model failure. Your assumptions about the problem are wrong, and adjusting actions won't fix broken beliefs.

You solve problems that keep regenerating. Address the issue here; it appears there. Fix the bug; it returns in a different form. That's not bad execution. The behavior you're trying to fix is being generated by an assumption that you haven't explicitly stated. Go deeper.

Your goals feel hollow. You're pursuing what you're supposed to pursue—and it doesn't satisfy you. The promotion, the milestone, the metric. You hit it, and it feels empty. That's a signal. The goal was inherited, not chosen. Time to examine the assumption that led you there.

Your industry's "best practices" feel misaligned. Everyone does it this way, so you do too—even though the approach feels wrong and the results are mediocre. You're operating within someone else's framework without questioning whether it fits your context.

Your beliefs feel automatic. Someone challenges a position you hold, and you react defensively before examining whether you actually believe it. That reflex is a warning. The belief may be inherited, rather than chosen.

The signal is consistent: effort without meaningful change. When you see that, stop adjusting and start examining.

How to Use It

Double-loop learning is a method for questioning your underlying assumptions and operating logic.

When persistent problems resist tactical fixes, the issue is rarely a lack of effort. It's assumptions.

Step 1: Identify the recurring pattern.

Write down a problem where you keep adjusting tactics without getting different results. Be specific. Not "I can't grow the business," but "We keep launching features that customers don't use." You're isolating a concrete behavior loop, not describing a vague frustration.

Step 2: Surface the governing assumption.

Ask: What belief is generating this pattern?

Most people answer with tactics: "We need better market research," or "We need to communicate features better." That's single-loop thinking. Go deeper.

What do you believe about how this works? What rule are you following without questioning it?

Examples:

  • "Features don't get adopted" → Underlying assumption: "More features create more value."
  • "Meetings feel unproductive" → Underlying assumption: "Alignment requires everyone in the room."
  • "I can't focus" → Underlying assumption: "Being available is part of my job."

Write it down. See it as separate from you. It's not truth—it's a belief that might be outdated or wrong.

Step 3: Question the assumption.

Where did this belief come from? Is it based on evidence or inheritance? Does it still apply? Who benefits from you believing it?

Most assumptions enter invisibly. Your previous company built features fast and won, so you absorbed "shipping features equals growth." Your training taught you "collaboration requires meetings," and you never questioned whether that's still true in a remote environment. Your first manager valued responsiveness, and you internalized "availability equals value."

Trace the origin. Often, your operating beliefs came from contexts that no longer apply.

Step 4: Redesign or discard.

Once you've surfaced and questioned the assumption, you can choose to keep it, modify it, or replace it.

If "more features create more value" is generating unused features, rewrite it: "Depth on core problems creates more value than breadth." Then, redesign your product strategy to align with the new belief.

If "alignment requires everyone in the room" is creating meeting overload, rewrite it: "Alignment requires clear documentation and opt-in participation." Then redesign your collaboration approach.

If "availability equals value" is preventing focus, rewrite it: "Deep work creates more value than responsiveness." Then redesign your calendar.

This isn't a one-time exercise. It's a continuous practice. Every time effort isn't translating to progress, run the protocol.

Single-loop learning adjusts actions. Double-loop learning transforms thinking.

Next Steps

Pick one recurring problem where you've adjusted tactics multiple times without meaningful progress.

Write down the governing assumption driving your approach. Ask: What am I taking for granted about how this works? What belief is generating this pattern?

Then question it: Where did this assumption come from? Is it still valid? Does it fit my current context?

You're not yet solving the problem. You're examining whether you're framing it correctly.

Where It Came From

Chris Argyris, a Harvard organizational theorist, spent decades studying why intelligent people and high-performing organizations kept repeating the same mistakes.

In 1977, he and philosopher Donald Schön published their findings, which suggested that most learning occurs at the surface level. Argyris documented a case that made the concept tangible: a major corporation lost over $100 million on a failing product over the course of six years. Multiple managers knew the product was doomed, but organizational norms about communication made it impossible to surface the truth.

The product failed. The money was lost. And the system that caused the failure remained intact because no one questioned the underlying beliefs about how communication should work.

A double loop is how you turn dead ends into doorways.

Until next time, keep questioning. Your mind is the last territory you truly control.

Think Independently, JC

Share or Join 👉

Re:Mind with Juan Carlos

Re:Mind is a weekly newsletter exploring mental models and frameworks that help you think clearly and make better decisions. Each week, I share practical insights and tools that transform complex ideas into wisdom you can apply immediately. Join me in making better decisions, together.

Read more from Re:Mind with Juan Carlos

Hello Reader, Here's the pattern: you set a target. You hit it for a week, maybe two. Then a bad day arrives (low energy, fractured schedule, unexpected chaos) and you miss. Not by much. But by the goal's own logic, a miss is a miss. So you log the failure. Then you miss again. Then the goal quietly dies, buried under a pile of "not todays." The goal didn't fail because you lacked discipline. It failed because it only had two states: perfect or pointless. And that binary is a trap. The ABC...

Hello Reader, My wife Taylor hosts a podcast called Doomed to Fail with her co-host Farz. The premise: take history’s most notorious disasters and epic failures, analyze the red flags, and ask the uncomfortable questions: How did things go so wrong? Could this have been avoided? They invited me to talk about a mental model that answers both questions. It’s called second-order thinking. And I wanted to share the core ideas with you here, because this pattern is everywhere. The Scene That...

Hello Reader, Austria and Germany share a border, similar cultures, and comparable healthcare systems. Ask citizens of both countries whether they support organ donation, and roughly 85% say yes. Yet Austria has a 99% organ donor registration rate, and Germany sits at 12%. Same values. Same medical infrastructure. Opposite outcomes. The difference? Austria uses opt-out registration. Germany uses opt-in. In Austria, you are considered a donor unless you actively decline. In Germany, you're not...