Knowing What to Do Was Never the Problem

The Declaration was the easy part. So is your strategic plan.

The Fourth of July always gets me thinking about what we actually celebrate.

We celebrate a document. One page, signed in 1776, describing what a country believed it should become.

It solved almost nothing that day.

The war lasted another seven years. The Constitution came later. Writing down what should be took an afternoon. Building it took decades.

I keep coming back to that, because it's the same pattern I see inside nonprofit organizations.

Every organization has its declaration

You have your version of that document. The mission on the wall. The strategic plan the board approved. The list of priorities everyone agrees matter. The grant that should be written, the donor who deserves a follow-up, the partnership that's been sitting there for months.

If I asked what should happen next, you probably wouldn't hesitate.

Knowing what to do was never the problem.

Where the work actually begins

So I've started paying attention to a different question. Not what organizations know. Where the work actually begins.

In almost every conversation, people describe work that should already be moving. Before anyone can take the next step, they have to remember why a decision was made, find the latest version of a document, reconnect conversations from months ago, or bring someone else up to speed. Progress doesn't begin with new work. It begins by reconstructing old work.

Over time that changes something. Organizations don't stop having ideas, or making good calls, or learning. They just struggle to carry any of it forward.

Organizations keep moving. The work keeps happening. It just doesn't always build.

We often describe this as a capacity problem. It is, partly. But the deeper issue is memory. Organizations lose what they know faster than they realize. When decisions and reasoning don't persist, you spend more time getting back to where you left off than building from it. The same priorities stay on the list, not because they didn't matter, but because every day starts by recovering context before anyone can move anything forward.

The weekend it clicked

That became especially clear over the holiday weekend.

Lee and I were back at our desks on Sunday. The work just doesn't recognize long weekends. What surprised me more was hearing from people in our beta doing the same thing. Not because they suddenly had new ideas. Because the context was finally there waiting for them, so they could pick the work back up instead of rebuilding it first.

A fundraising campaign that had sat unfinished since spring finally launched. A board packet that had slipped through three meetings got done. Partnership proposals that had lived in draft form were finished.

No one found more hours in the day. The difference wasn't knowing. It was spending less time getting back to where the work had already been.

One person told me the thing she appreciated most was that something was finally keeping track. This isn't really about software. It's about having somewhere for the work to continue instead of starting over.

After the declaration

The Declaration mattered because people kept building on it. Every generation inherited more than an idea. They inherited the work that came before.

I wonder how different nonprofits would feel if their own thinking accumulated the same way. Not because they wrote better plans, or sat through another training, but because what they already learned became the ground the next thing was built on.

Knowing what to do was never the problem.

The real question is whether the work has somewhere to go after it begins.