The Problem Is Rarely the Whole Problem

What recurring challenges can reveal about the capacity an organization needs to develop next.

Growing organizations are very good at telling leaders what needs their attention.

A project falls behind. A decision gets stuck. Accountability becomes a recurring conversation. Two leaders leave the same meeting with different understandings of what was decided. The founder discovers that something they thought had been delegated has landed back on their desk.

The natural response is to solve the problem. Often, that is exactly what leadership requires.

I have become more interested in what happens when the problem gets solved and something remarkably similar happens again.

One difficult meeting may simply be a difficult meeting. A missed deadline may simply be a missed deadline. But when the same kind of friction begins appearing in different places, among different people, under different circumstances, I start looking for something else.

Events capture attention. Patterns explain reality.

After nearly three decades inside and alongside organizations, I have learned to pay close attention to recurrence.

What keeps happening?

Organizations have good reasons for focusing on what just happened. Something goes wrong. Leadership responds. A decision is made. The organization moves forward.

Meanwhile, patterns accumulate quietly. Another missed handoff. A familiar conversation about accountability, this time involving another team. An important initiative everyone supports but no one seems able to move forward. A founder pulled back into work they were certain they had delegated.

Each occurrence comes with a reasonable explanation. Expectations weren't clear. Someone misunderstood. The team was overloaded. Circumstances changed.

The explanation may be accurate. It may also be incomplete.

When something keeps returning, I want to know: What keeps happening?

That question widens the field of view. Instead of examining one meeting, one person, or one decision, we begin looking across time, teams, and circumstances that initially appeared unrelated.

That is often where the organization becomes more visible.

What proximity makes difficult to see

Leaders are surrounded by information about their organizations. They know the history behind decisions, why roles were structured a certain way, which experiments failed, which compromises were made, and why something that looks strange from the outside once made perfect sense.

Over time, that knowledge becomes intertwined with assumptions.

Context that was once accurate remains embedded in how people understand the organization long after the organization itself has changed. Interpretations harden. People stop noticing what they have learned to explain. The organization keeps changing while the stories people use to understand it often change more slowly.

A communication problem over here appears unrelated to an accountability problem over there. A decision bottleneck belongs to one leader. An execution challenge belongs to another team.

Viewed separately, each requires its own solution. Viewed together, they may be different expressions of the same pattern.

Perhaps people no longer share enough context to exercise judgment independently. Perhaps authority has been distributed without enough clarity to use it confidently. Perhaps the organization still depends on informal ways of communicating that worked beautifully when everyone could fit around the same table.

These aren't conclusions to jump to. Recurrence is information, not proof. It is a reason to look more closely.

Solving the same problem exceptionally well

Capable leaders solve problems. That strength can create an interesting paradox: an organization can become remarkably good at solving the same problem over and over without recognizing that it is the same problem.

A new process gets added. Expectations are clarified. Another approval is introduced. Another meeting appears on the calendar.

The immediate situation improves. Then the frustration returns somewhere else.

Over time, organizations can accumulate process around a pattern they still haven't understood. This is why I have become cautious about moving too quickly from problem to solution.

A problem asks: What should we do? A pattern asks: What should we understand? Leadership requires both.

What is the organization being asked to develop?

Last month, I wrote that every stage of growth asks an organization to become capable of something it has never had to become before. Recurring challenges are one place those requirements become visible.

When an organization is small, a founder can carry an extraordinary amount of context personally. Decisions happen through conversation. Ambiguity can be resolved quickly. Someone notices something is off and addresses it.

Growth stretches those informal capacities. More people need enough context to exercise judgment. Authority has to travel farther. Relationships multiply. Decisions become connected to consequences the person making them may not see directly.

Eventually, something that once depended almost invisibly on a few people has to become an organizational capacity.

We often experience that transition first as friction. This is why one question has become increasingly useful in my work: If we solved this problem tomorrow, what would our organization still need to become more capable of so it doesn't keep returning?

The deadline still matters. The conflict still needs attention. The decision still has to be made. The question simply refuses to stop there.

Seeing what the problem is showing you

Not every organizational problem requires a deeper diagnosis. Organizations are full of ordinary mistakes, imperfect decisions, personality conflicts, missed details, and circumstances no one could have anticipated. But recurrence deserves curiosity.

When a familiar frustration returns wearing different clothes, I have learned not to dismiss the resemblance. Where else have we seen this? What assumptions are we making about why it keeps happening? What has changed about the organization since those assumptions were formed? And eventually: What is this organization asking us to become more capable of?

Some problems will disappear once someone makes a good decision. Others will keep returning until leadership recognizes that the problem itself was never the whole problem.

Sometimes recurring friction is the organization revealing the edge of a capacity it has not yet developed.

Once you see the pattern, you are no longer solving the same problem.

You are finally seeing what the problem has been trying to show you.

The 13th Field Note is where I think in public about leadership, growth, and the human systems we build together. A new Field Note is published on the 13th of each month.

Amanda Pascale is the founder of Lionhearted Enterprises and a Strategic Growth Partner to founders, CEOs, and leadership teams navigating consequential growth.