Edition No. 52 - The Difference Between a Problem and a Pattern

Why the same strain may be showing up in several different places

A problem usually announces itself clearly.

The board is not following through. Fundraising feels stuck. Staff are confused. The leader is tired. Communication breaks down. A decision keeps circling back.

Each issue looks separate at first.

So the organization tries to solve each one separately. Board training for the board issue. A campaign plan for fundraising. A meeting rhythm for communication. A clearer job description for staff.

Any of those may help.

But sometimes what looks like five problems is really one pattern wearing five different outfits.

Problems look isolated. Patterns show how the system is actually functioning.

When the Same Strain Keeps Returning

Patterns are easy to miss because they rarely show up in only one place.

A board member wants to help but does not know how to begin. A fundraiser says the donor story depends too much on one person. A staff member says decisions are unclear. The leader says everything comes back to them.

Those can sound like different concerns.

But listen underneath them.

Each one may be pointing to the same capacity issue: the work has not been made clear enough, shared enough, or carryable enough for more people to participate with confidence.

The board issue may not be only a board issue. The fundraising issue may not be only a fundraising issue. The staffing issue may not be only a staffing issue.

They may all be evidence of the same deeper pattern.

The system depends on a few people to interpret too much, remember too much, translate too much, and hold too much.The Problem Is the Doorway

This is why the first named problem matters, but it should not be treated as the whole diagnosis.

A problem is a doorway.

It gives the organization something to notice. It offers language for the discomfort. It creates enough urgency for leaders to ask, "What is going on here?"

But if the organization stops at the doorway, it may build the wrong solution.

A board training may inspire people briefly but never answer where ownership lives. A fundraising plan may create activity but never build shared confidence around the donor story. A new hire may add capacity but inherit the same fog.

The visible problem is not unimportant. It is trying to reveal something.

The work is to listen long enough to see whether the issue is isolated or connected.

Patterns Tell the Truth Kindly

Seeing a pattern can feel sobering at first.

It may reveal that the organization has been solving symptoms for a long time. It may show that people have been working hard inside a structure never designed to carry the weight placed on it.

But pattern recognition can also be merciful.

It moves the conversation away from blame. The question becomes less, "Who is not doing their part?" and more, "What has the system learned to do, and what has it not yet learned to carry?"

That shift matters.

It protects the board from being labeled disengaged too quickly. It protects staff from being treated as resistant when they may be unclear. It protects the leader from believing their exhaustion is personal failure.

This keeps showing up in different forms. Maybe it is not five problems. Maybe it is one pattern.

Seeing Before Solving

This is why a focused Scan can be so helpful.

A few careful interviews, document review, and a practical debrief can help the leader and system see what the recurring problems have in common.

Where does the same strain repeat? What keeps returning to one person? Where does agreement fail to become ownership? Where does mission depend more on memory than shared practice?

The goal is not to make the work more complicated.

The goal is to make the real work more visible.

Once the pattern is named, the next step can become clearer. Maybe the organization needs board formation, fundraising alignment, role clarity, decision rhythms, or a better way to distribute ownership.

But those choices become wiser when they are made in response to the pattern, not just the pressure of the most recent problem.

Before you solve the problem in front of you, listen for the pattern underneath it.

That is often where the real work begins.

Go get 'em this week and keep inviting people into the wonderful story of your work! I believe in you and hope you do too!

Kevin