If the Same Problem Keeps Returning, You May Not Have Solved It

Something goes wrong: A deadline is missed, a client complaint escalates, documentation falls behind. Perhaps, a department fails to communicate something important, an employee makes a mistake, and a manager intervenes.

The problem is addressed: an email is sent, someone is reminded of the expectation, and a meeting is held. Perhaps a new procedure is introduced, and everyone agrees to do better.

The organization moves on. Then, three months later, something remarkably similar happens again: It is now a different employee, a different client, a different Tuesday, but it is the same problem.

At some point, leadership has to ask a more difficult question:

What if the problem is not that people keep making the same mistake? What if the system keeps producing the same conditions?

This is one of the most important shifts from reactive leadership to systems leadership. Organizations are often very good at responding to events: something happens, and someone acts; the immediate issue is corrected, and operations resume.

Of course, some problems require immediate intervention. However, resolving an event is not necessarily the same as solving the problem that produced it.

Imagine water repeatedly appearing on the floor of a building. Each time, someone arrives with a mop, the floor is cleaned beautifully, and everyone appreciates the responsiveness. However, if the water returns every Tuesday, eventually someone has to stop praising the mopping and ask:

Where is the water coming from?

Organizations need the same discipline. Repeated problems are information. They tell us that something beneath the visible event may remain unchanged. This is where leaders can become trapped by what appears obvious. An employee missed the deadline, so the employee needs better time management. A supervisor failed to communicate, so the supervisor needs communication training. Documentation is late, so staff need another reminder. Turnover is high, so HR needs to recruit faster. People are burned out, so the organization offers wellness activities.

Each response may contain something useful; and each may also address the visible manifestation while leaving the generating conditions intact.

Peter Senge’s work on learning organizations helped popularize a fundamental principle of systems thinking: events are often connected to broader patterns and underlying structures. If leadership responds only at the level of the event, the organization can become extremely efficient at repeatedly solving problems it continues to create.

That is an expensive way to operate. It is expensive financially, cognitively, and especially emotionally. Recurring problems create a particular kind of exhaustion. People begin saying: “We’ve talked about this before.” “Nothing ever changes.” “Here we go again.” “We already tried that.”

Those statements are easy to dismiss as negativity. Yet sometimes they are organizational memory. People remember previous attempts, previous promises, and they remember when the same problem was called urgent six months ago. Eventually, repeated unresolved patterns teach employees something. They teach people what the organization is willing to tolerate.

This is why recurring problems deserve more curiosity than blame. When the same issue appears repeatedly, leaders need to resist the temptation to ask only: “Who did this?” They ought to also ask: “What keeps making this possible?” That second question, in turn, moves us from individual correction toward organizational learning.

At SWEET Institute, the Four Layers of Transformation give us a way to deepen that inquiry.

At the Conscious Layer, we examine the event.

• What happened?

• Who was involved?

• What was expected?

• What actually occurred?

• What immediate action is needed?

• This layer matters. Facts matter. Responsibility matters. Accountability matters.

• But we cannot stop there.

At the Preconscious Layer, we look for patterns.

• Where else has something similar happened?

• How often?

• Under what conditions?

• At what times?

• Within which teams?

• What tends to happen immediately before the problem?

• What tends to happen afterward?

• Patterns turn isolated events into information.

Then we move to the Unconscious Layer.

Here we ask what structures, assumptions, incentives, habits, or unwritten rules may be helping reproduce the pattern. Perhaps employees are told to prioritize quality while being rewarded primarily for speed. Perhaps managers are expected to supervise thoughtfully while carrying caseloads that make meaningful supervision nearly impossible. Perhaps employees are expected to raise concerns, but previous experiences have taught them that speaking up creates interpersonal risk. Perhaps everyone knows a process is inefficient, but no one believes they have the authority to change it. Perhaps a high-performing employee repeatedly compensates for a dysfunctional process, preventing leadership from ever seeing how dysfunctional the process actually is.

Now the problem looks different. The employee may still have responsibility. However, responsibility is no longer confused with explanation.

Someone can be responsible for an action without being the sole explanation for why the action occurred.

Systems thinking does not eliminate accountability. It makes accountability more intelligent. It allows us to hold individuals responsible for choices while simultaneously asking what the organization can learn from the conditions surrounding those choices.

Then we arrive at the Existential Layer.

Here we ask:

• What is this recurring problem trying to teach us about who we are becoming as an organization?

That question changes the meaning of failure. Failure becomes more than something to eliminate. It becomes something to learn from. Healthy organizations do not aspire to eliminate every mistake. That would be unrealistic. They aspire to avoid wasting mistakes. When something goes wrong, they extract learning from it. When it happens again, they become more curious. When it becomes a pattern, they stop treating it as an isolated event.

This is where leadership becomes organizational learning. Instead of asking only, “How do we prevent this employee from doing this again?” leaders begin asking, “How do we make this outcome less likely throughout the system?”

That may lead to a very different intervention. Perhaps the workflow needs redesign, decision rights need clarification, or staffing assumptions need reconsideration. Perhaps technology is creating unnecessary friction, or two departments have incompatible expectations.

Perhaps supervisors need more authority rather than more training, or perhaps a process contains ten steps when five would accomplish the same thing. Perhaps leadership itself is creating competing priorities.

Sometimes, yes, the conclusion will still be that an individual needs coaching, additional training, clearer accountability, or consequences. In other words, systems thinking should never become a sophisticated way of avoiding responsibility. However, neither should accountability become a convenient way of avoiding systems thinking. We need both.

This is why the SWEET four-step rhythm is so useful when problems repeat.

First, Stabilize. Address the immediate situation, and protect people, operations, and the mission.

Then Reframe. Ask whether the visible incident is the entire problem or one expression of something larger.

Next, Decide with Clarity and Transparency. Determine what needs to change, who owns that change, and how the organization will know whether the intervention worked.

Finally, Align Work with Purpose. Make sure the solution improves the organization’s ability to fulfill its mission rather than merely adding another procedure.

Then comes the part organizations frequently forget:

Go back and look.

Did the problem actually decrease?

Did the new process work?

Did people adopt it?

Did something unexpected happen?

Did the intervention solve the problem, or merely move it somewhere else?

Without that final learning loop, organizations can mistake action for improvement.

This work sits at the heart of the Beyond Burnout 12-Month Leadership Cohort.

Because burnout is often sustained by recurring organizational problems that people are expected to compensate for indefinitely.

These include the broken workflow everyone works around, the vacancy everyone absorbs, and the meeting everyone knows accomplishes little. These may include the conflict no one resolves, the unclear role everyone has learned to navigate, and the inefficient process everyone quietly accepts.

Each one consumes small amounts of human energy, day after day, and month after month. Eventually, what looks like individual exhaustion may partly reflect accumulated exposure to organizational problems that were repeatedly managed but never truly solved.

Here is the question for your leadership team this week:

What problem in our organization are we exceptionally good at repeatedly managing?

Find one.

Then resist the urge to reach immediately for another mop.

Follow the water.

The Call to Action

If the same problems keep returning with different names, different employees, or different circumstances, your organization may not need another reminder, another training, or another policy.

It may need to learn.

The Beyond Burnout 12-Month Leadership Cohort helps leaders move beyond reactive problem-solving toward deeper organizational learning, examining the patterns, structures, assumptions, and human dynamics that repeatedly shape performance.

We Stabilize, Reframe, Decide with Clarity and Transparency, and Align Work with Purpose.

Strong organizations solve problems. Learning organizations ask why those problems existed in the first place; nd transformational organizations go one step further:

They change the conditions that keep bringing them back.