Begin With the End in Sight

Most planning conversations I have joined began somewhere in the middle. Someone had already decided that the organization needed a strategic plan, or a feasibility study, or a retreat, or a new brand. The question on the table was how to run it: how many sessions, how many interviews, how long it would take, what it would cost. Those are fair questions. They are simply the second set of questions.

The first question is quieter and considerably harder. What needs to be different when this is finished? Not what will be produced, but what will have changed. If the answer arrives quickly and confidently from everyone in the room, the organization is probably ready. If the answers differ — and they often do, even among people who work together every week — that difference is the real starting point.

Activities are easy to count. Outcomes are easy to avoid.

Activities are comforting. They can be scheduled, staffed, and reported. A board can look at a list of completed activities and feel that progress has occurred. And sometimes it has. But activity is only evidence of effort, not of change, and organizations under pressure tend to reach for effort because effort is available immediately while change is not.

I have watched capable organizations complete an impressive amount of work and still find themselves in the same position eighteen months later: the same tension between programs and revenue, the same uncertainty about who decides what, the same story told slightly differently each time someone tells it. The work was real. It simply was not pointed at anything specific.

The correction is not to work less or plan less. It is to name the destination in plain language before choosing the vehicle. When an organization can say, in a sentence a volunteer would understand, what will be true at the end that is not true now, the choices that follow become much simpler. Some proposed activities suddenly look essential. Others look like habit.

Clarity is not the same as rigidity

People sometimes resist this kind of clarity because they have seen it misused. They remember a plan that became a cage: a document that could not absorb a funding shift, a leadership change, or a season that did not cooperate. That experience is legitimate, and it makes a certain caution reasonable.

But clarity and rigidity are different instincts. Rigidity fixes the method. Clarity fixes the intent and leaves the method open. In the nonprofit work I led, we knew what we wanted to be true about access to the outdoors — that a family using a wheelchair could reach the canopy of a forest and a classroom could reach a shoreline. How we got there changed more than once. We adjusted sequence, partners, and scope. We did not adjust the purpose, and because the purpose held steady, each adjustment felt like navigation rather than retreat.

A useful test: if a major assumption changed tomorrow, would the plan tell you what to protect? A rigid plan answers by listing tasks. A clear plan answers by naming the outcome those tasks were serving, which is exactly the information you need in order to change tasks well.

Alignment is a prerequisite, not a byproduct

Boards and staff frequently arrive at the same table with different definitions of success, and neither group is being careless. Board members often see the organization from a distance and over a longer horizon: sustainability, reputation, stewardship, the arc of a decade. Staff see the organization at close range and in real time: the program that runs on Thursday, the family at the front desk, the grant report due at month's end. Both views are accurate. Neither is complete.

The mistake is to assume that alignment will emerge from the process itself. Occasionally it does. More often, unresolved differences travel quietly through the work and surface at the worst possible moment — when a budget must be cut, a position must be defined, or a public commitment must be made. It is far less costly to surface those differences at the beginning, when disagreement is still inexpensive.

I have found it helpful to ask each group, separately and then together, to complete the same sentence: two years from now, we will know this worked because ______. The gaps between the answers are not a problem to be smoothed over. They are the agenda.

Ambition should be matched with resources

The last discipline is the least romantic. An outcome that no one has the time, money, or authority to pursue is not a goal; it is a wish that will quietly become a source of guilt. Every meaningful ambition should be traceable to someone whose job it is to advance it, a realistic estimate of what it will require, and a decision about what will receive less attention as a result.

That last piece is the one most often skipped. Organizations are generous by nature, and saying no feels like a failure of imagination. But a plan that adds without subtracting is a plan that will be delivered by exhausted people, and exhaustion is not a strategy. In my own experience raising support and building programs, the commitments that succeeded were the ones we were willing to protect at the expense of something else.

None of this requires an elaborate methodology. It requires a willingness to sit with the harder question a little longer before the calendar fills. Begin with a clear description of what needs to be different. Then choose the process that is most likely to produce it — and be prepared to change the process, never the purpose.