Why Broken Problems Cannot Be Solved, Only Redesigned

Jun 02, 2026

9 min read

2 views

88%

The Most Expensive Habit We Have Is Trying to Fix the Wrong Thing

What if the reason so many smart people remain stuck is not that they lack better answers, but that they are asking the wrong kind of question?

Most of us are trained to see a problem as a thing with edges. Something breaks, we inspect it, identify the faulty part, and repair it. That instinct works beautifully for machines, where a broken gear can be replaced without changing the rest of the device. But human life, organizations, and knowledge systems are not machines. They are living arrangements of context, interaction, and feedback. When we treat them as isolated parts, we often improve one piece while quietly damaging the whole.

That is why so many solutions feel effective in the short term and corrosive in the long term. We resolve a symptom, but the underlying system keeps generating the same trouble in new forms. The deeper issue is not that we are bad at problem solving. It is that we confuse solving with redesigning reality.

Why Problems Multiply When We Treat Them Like Objects

A common mistake in thinking is to imagine that a problem is a discrete object, like a stone on the road. Remove the stone, and the road is clear. But many problems are not stones. They are patterns. They live in relationships, habits, incentives, language, and expectations. Pull one thread, and the whole fabric shifts.

Consider a team that keeps missing deadlines. The obvious response is to demand better time management, add status meetings, or punish lateness. Those actions may produce a brief improvement. Yet if the real issue is ambiguous priorities, poor handoffs, or a culture that rewards saying yes to everything, the deadline problem will return in a new costume. The visible symptom was not the disease. It was the body’s attempt to adapt to it.

This is why context is not decoration. It is the problem. Once you remove a system from its environment, you lose the very interactions that make it intelligible. A customer complaint may look like a communication issue until you notice that the company’s own process creates confusion. A habit of procrastination may seem personal until you realize the task is ill defined, emotionally costly, or embedded in a workflow that encourages delay.

A problem is often not a thing to be eliminated. It is a signal that the system is producing an outcome it was never consciously designed to produce.

That changes the job entirely. You stop asking only, “How do I fix this?” and start asking, “What kind of world keeps creating this outcome?”

The Hidden Difference Between Solving and Dissolving

There are at least four ways people respond to difficult situations.

Absolution: ignore the issue and hope it fades.
Resolution: choose a decent enough response based on past experience.
Problem solving: search for the best available fix in the current frame.
Dissolving: redesign the system so the problem no longer exists.

The first three treat the problem as something already given. The fourth asks whether the category itself can be changed.

This distinction is more radical than it first appears. If you are trying to solve traffic congestion, you might widen roads, adjust lights, or stagger work hours. If you are trying to dissolve congestion, you ask a different question entirely: why does our city depend on so many people traveling to the same place at the same time? That question opens up remote work, transit design, housing policy, and neighborhood planning. The issue is no longer traffic alone. It is the structure of daily life.

The same applies to personal life. If you have trouble focusing, you can buy a new app, set a timer, or rearrange your desk. That is problem solving. But if you ask why your attention keeps getting fragmented, you may discover a system designed for interruption, not concentration. The answer is not another productivity trick. It is a redesign of your inputs, commitments, and environment.

The deepest insight here is that problems are often properties of systems, not defects in parts. A part can be perfectly healthy and still participate in a bad pattern. That is why the logic of repair is often too small for the scale of the issue.

Outlining a Life, Not Just a Page

This is where outlining becomes more than a writing technique. At its best, outlining is an act of design.

When you outline, you are not merely arranging notes. You are deciding what belongs together, what depends on what, and what must come before something else can make sense. You are building a structure that gives meaning to fragments. Without that structure, even good ideas remain scattered. With it, they become capable of producing insight.

Think of the difference between a pile of bricks and a house plan. A pile of bricks contains possibility, but not purpose. The house exists first as a design, a coherent pattern of relationships. Only then do the pieces take on their roles. If you try to fix a room without understanding the whole house, you may improve one corner while undermining the layout, light, or flow of the rest.

The same principle applies to thinking itself. A notebook full of observations is not yet understanding. A collection of tasks is not yet a strategy. A series of clever solutions is not yet wisdom. Outlining is powerful because it forces you to see the architecture of the problem before acting on its parts.

This is why many people feel busy but not effective. They are operating at the level of notes, tasks, and reactions, without ever stepping back to ask what the structure is doing. They are inside the rooms of the house, trying to reason their way to a better home, when the real work is to redraw the blueprint.

Good thinking is not just better answers. It is better framing.

That insight matters in writing, planning, management, and personal change. If you cannot outline the system, you cannot redesign it. You may still improvise a fix, but you will be operating blind to the interaction effects that determine whether the fix holds.

The Real Question: What Reality Is This Problem Helping Create?

Once you see that many problems are emergent patterns, a more interesting question appears: what reality is this problem sustaining?

This sounds strange at first, but most persistent problems have a function. A family conflict may preserve distance that everyone has learned to tolerate. A bloated meeting culture may preserve control by making decisions appear collaborative. A personal pattern of overcommitting may preserve identity by making someone feel needed. The problem is painful, but it also stabilizes the system in some way.

That is why simple fixes often fail. They threaten the hidden balance that the problem was helping maintain. If you remove the visible symptom without addressing the underlying equilibrium, the system will often create a new symptom to restore its previous state.

This is the mental shift from correction to design. Correction asks, “What is wrong here?” Design asks, “What is this arrangement optimized for, even if unintentionally?” Once you answer that, the path forward becomes clearer. You may discover that what looks like inefficiency is actually protection, or that what looks like laziness is actually resistance to a misdesigned workflow.

A useful way to test this is to ask three questions:

What behavior keeps repeating?
What does that behavior make possible or avoid?
What system changes would make the behavior unnecessary?

That third question is the one most people skip. They stop at behavior modification because it is visible and immediate. But lasting change usually requires changing the conditions that make the behavior reasonable.

A Practical Framework: From Symptom Fixing to System Redesign

If you want to move from problem solving to problem dissolving, use this four step frame.

1. Name the symptom precisely

Do not start with vague labels like “communication problem” or “motivation issue.” Specify the repeating pattern. For example: “Decisions are revised three times after meetings,” or “I begin important work late in the day and then rush.” Precision reveals structure.

2. Map the context, not just the event

Ask what precedes the symptom, what reinforces it, and what it protects. In a workplace, look at incentives, approvals, emotional norms, and information flow. In personal life, look at timing, environment, energy, and social pressure. Problems rarely live alone.

3. Identify the system’s current payoff

Every stubborn pattern is getting something. It may be safety, predictability, approval, or avoidance of uncertainty. If you do not identify the payoff, you will attack the behavior while preserving the reason it exists.

4. Redesign the conditions

Change the environment so the old pattern becomes less necessary and the desired pattern becomes easier. This could mean simplifying choices, reducing friction, clarifying ownership, changing meeting structures, altering defaults, or reorganizing the physical space.

This framework is powerful because it moves from judgment to architecture. Instead of asking why people are failing, it asks what design is making failure likely. That is a much more humane and more effective question.

Key Takeaways

Stop treating every problem as a broken part. Many persistent issues are properties of the whole system.
Look for patterns, not just incidents. Repetition is usually a clue that the underlying structure matters more than the surface event.
Ask what the problem is protecting. Symptoms often maintain hidden stability, even while causing pain.
Design the conditions, not just the response. Lasting change comes from changing incentives, environment, sequence, and context.
Use outlining as a thinking tool. Before solving, map the architecture of the problem and how its pieces interact.

The Strange Discipline of Seeing the Whole

The hardest part of redesigning a problem is that it requires patience with ambiguity. A part is easier to grasp than a system. A symptom is easier to attack than a pattern. A fix is easier to celebrate than a redesign. But the world keeps teaching the same lesson: what is easiest to see is rarely what matters most.

This is why design thinking is not just for engineers or architects. It is a moral and intellectual discipline. It asks us to resist the seduction of quick fixes and instead study the relationships that produce outcomes. It asks us to trade the thrill of immediate action for the deeper reward of lasting change.

The most powerful shift is not from confusion to certainty. It is from reaction to architecture. Once you see that, the question changes. You are no longer merely trying to solve a problem inside reality. You are deciding how reality itself should be arranged.

And that is a far more consequential kind of thinking.