The Problem Behind the Problem

Organizations rarely open a conversation with their actual problem. They open with the symptom that has become impossible to ignore. Revenue is down. The board is restless. The staff seems disengaged. The website is dated. Each of these is a real observation, and each is worth taking seriously. But the presenting concern is a starting point, not a diagnosis.

I say this with some humility, because the temptation to answer quickly is strongest when you have seen a situation before. Experience is useful precisely because it produces pattern recognition — and pattern recognition is exactly what causes an advisor to hear three sentences and reach for a familiar answer. The discipline is to slow down long enough to find out whether this organization is actually the pattern you think it is.

Fundraising is often about something else

When an organization says it has a fundraising problem, sometimes it does. Often, though, the money is a downstream reading of something upstream.

It can be a mission problem: the organization can describe what it does but not why it matters now, and donors respond to relevance more than to activity. It can be a board problem: nobody has ever been asked directly to participate in raising support, or has been asked in a way that made the ask feel like an obligation rather than an invitation. It can be a trust problem: something happened — a departure, a controversy, a promise that slipped — and giving quietly cooled while everyone politely avoided naming it. It can be a discipline problem: gifts arrive, but there is no consistent practice of thanking, reporting, and asking again, so relationships restart from zero each year. And it can be a story problem: the organization's work has changed and its language has not.

Each of those calls for a different response. A campaign built on top of an unaddressed trust problem will exhaust the people who care most, and it will do so slowly enough that no one identifies the cause until the campaign is nearly over.

Communication problems are frequently strategy problems

A similar substitution happens with communications. An organization concludes that its message is not landing and decides it needs new materials, a new site, a new identity. Sometimes the materials genuinely are the constraint. Often the difficulty is upstream of design: the organization has not decided what it is, and no amount of typography resolves an unmade decision.

There is a simple check. Ask five people from across the organization — a board member, a program lead, a front-desk staff member, a long-time volunteer, a newer employee — to describe in two sentences what the organization is for. If the answers rhyme, the problem is likely presentation. If they diverge, no rebrand will fix it, and doing one first will only make the divergence more expensive to repair later. Branding is worth doing well; it is best done after a decision, not instead of one.

Board concerns are usually about expectations and information

When boards become uneasy, the discomfort tends to be attributed to personality. In my experience it is more often structural. Members are unclear about what is expected of them, or they are receiving information that does not let them govern well.

A board that receives thirty pages of operational detail and no interpretation will drift toward the details, because details are the only thing it has been given to hold. A board that receives only reassurance will eventually stop believing it. Neither behavior is a character flaw; both are predictable responses to the material in front of them. Change what a board is asked to consider and, more often than not, the behavior changes with it.

Expectations work the same way. Many boards have never had a direct conversation about what membership actually requires — attendance, giving, advocacy, committee work, the willingness to make an introduction. In the absence of that conversation, each member invents a private standard and then quietly judges the others against it. Naming the expectation is not a loyalty test. It is a kindness, and it is usually welcomed by the people who have been guessing.

None of this means the presenting concern should be dismissed. It should be treated as evidence — accurate about something, but not necessarily about itself. When an organization tells me its board is disengaged, I believe that something real is being observed. I simply do not assume the cause is located in the people being described.

A sequence worth trusting

Over time I have come to rely on a simple sequence. It is not a proprietary method. It is a way of keeping the work honest.

• Listen. Talk with enough people, in enough settings, to hear what is said easily and what is said carefully.
• Understand. Name the actual condition — including the parts that are uncomfortable — and confirm it with the people who live inside it.
• Strengthen. Repair the underlying capacity: clarity, governance, discipline, trust, or story, whichever the condition requires.
• Advance. Only then pursue the ambitious thing, with a foundation that can carry it.

The sequence is often resisted because it seems slower. In practice it is usually faster, because it avoids the most expensive kind of work: the effort that is competent, well-executed, and aimed at the wrong condition.

It also asks something of the advisor. To listen well, you have to be willing to hear that your first instinct was wrong, and to say so. The organizations I have been most useful to were the ones where I resisted the urge to be impressive early and settled instead for being accurate a little later.