You’ve been in that meeting. The one where the same problem surfaces again.

Maybe it’s a team that keeps missing deadlines. A communication breakdown that seems to repeat itself every few months. A key player who can’t seem to follow through. A senior leader who keeps creating confusion without realizing it.

And every time it comes up, someone says some version of: “We need to fix this.”

So you fix it. Or you try to. You address the behavior, adjust the process, have the conversation. And for a while, things improve.

Then it comes back.

Here’s what I’ve noticed after more than 20 years of working inside organizations: the problem isn’t that leaders don’t care enough or don’t work hard enough to fix what’s broken. The problem is that they’re solving symptoms. The root cause is still running.

What you’re looking at isn’t a problem. It’s a pattern.

The Distinction That Changes Everything

Symptoms Repeat. Patterns Connect.

There’s an important distinction most leaders miss, and it costs them more time than almost any other mistake.

A symptom is what you can see. A missed deadline. A team conflict. A disengaged employee. A communication breakdown. These are real, and they need to be addressed. But addressing them alone doesn’t make them stop.

A pattern is what connects the symptoms.

Think about it this way. If your team keeps missing deadlines, that’s a symptom. But what’s the pattern underneath it? Are deadlines being missed because priorities keep shifting without notice? Because workload isn’t being distributed well? Because accountability conversations aren’t happening until it’s too late? Because the team doesn’t have what they need to execute?

The deadline is the symptom. The pattern is somewhere in the leadership, the communication, or the system around it.

When leaders treat symptoms without identifying the pattern, the symptom always comes back. Sometimes in the same form. Sometimes in a different one. But it comes back because the root cause was never named.

When leaders treat symptoms without identifying the pattern, the symptom always comes back. The root cause was never named.

What I See in Organizations

What Patterns Actually Look Like

I want to give you a few real examples. Not with names, but with enough detail that they’ll feel familiar.

The accountability loop.

A leader comes to me frustrated that people on their team aren’t taking ownership. “Nobody follows through,” they tell me. “I have to chase everything.” When we look underneath it, the pattern isn’t a performance problem. It’s a clarity problem. Expectations are being set in conversation and never confirmed in writing. Deadlines are implied, not stated. Ownership is assumed, not assigned. The symptom is low accountability. The pattern is unclear expectations. The root cause is a leadership communication habit.

The conflict that keeps coming back.

Two senior leaders can’t seem to align. Every time they’re in the same room, tension surfaces. The executive team has had the conversation, mediated the conflict, and asked them to work it out. Twice. When we look underneath it, the conflict isn’t about personalities. It’s about decision rights. Nobody has clearly defined who owns what. So they keep stepping into each other’s territory, and every step feels like a threat. The symptom is conflict. The pattern is role overlap. The root cause is structural.

The culture problem nobody can describe.

Leadership is hearing that morale is low. Engagement scores are declining. People are leaving. But when you ask leaders to describe the culture problem, they struggle to put their finger on it. When we look underneath it, the pattern is inconsistency. Leadership standards are communicated but not modeled. What gets tolerated in some areas doesn’t get tolerated in others. What gets celebrated sends a different message than what gets corrected. The symptom is low engagement. The pattern is inconsistent leadership behavior. The root cause is a gap between stated values and actual standards.

A Framework for Root Cause Thinking

Introducing The Pattern Diagnostic™

Patterns in organizations almost always reveal themselves through three lenses. I use these in every diagnostic engagement.

People. How are leaders leading? Where is trust breaking down? Who owns what? Are the right people in the right roles? Where is emotional intelligence creating friction?

Communication. What isn’t being said clearly? Where are expectations being assumed rather than stated? What feedback isn’t happening? What conversations keep getting avoided?

Systems. Where is the structure creating the problem? Are roles clearly defined? Are decision rights assigned? Are the right processes in place, or are people working around them?

Here’s what I’ve learned: when something keeps going wrong in an organization, the answer almost always sits in one of these three areas. Or at the intersection of two of them.

An accountability problem is usually a clarity problem (communication) that hasn’t been reinforced by structure (systems).

A conflict problem is usually a role problem (systems) that’s being expressed through behavior (people).

A culture problem is usually a leadership consistency problem (people) that’s never been named out loud (communication).

The Pattern Diagnostic™ isn’t complicated. It asks one question from each lens:

• What do I see in the people?
• What do I hear in the communication?
• What does the structure reveal?

When you hold all three together and look for what connects, the root cause usually becomes visible.