The Plan You Can't Actually Run

I've handed over a lot of strategy documents. The good ones get read once, nodded at in a meeting, and then filed somewhere nobody opens again.

That's not a failure of the strategy. It's a failure of the thing that was supposed to come after it.

Research on strategic planning is blunt about this: more than 60% of strategic plans fail during implementation, not during the planning itself.

The thinking was sound. The follow-through wasn't. And in a sector where every hour is already spoken for, that gap isn't surprising. It's the default outcome unless someone plans specifically to close it.

A strategy tells you what to build and why. It doesn't tell you who sends which email on which day, what the CRM automation actually needs to trigger on, or what gets QA'd before it goes live.

Those are two different documents, written for two different moments, and most organizations only ever get the first one.

That's not because nobody cares about the second one. It's because the first one feels like the finish line. Board approves the plan, everyone exhales, and the org moves back into whatever was on fire that week.

The build — the actual sequence of tasks that turns the strategy into something donors experience — quietly becomes next quarter's problem. Then next year's. And the year after that.

I've said before that finding a leak isn't the same as fixing it, and designing the fix isn't the same as building it either.

Architecture tells you what the structure needs to be.

Build is where someone actually sets the automation triggers, writes the sequence, configures the workflow, and tests it against a real donor record before it touches your file.

Skip that step and you get the story every consultant has heard a version of: "we tried that, it didn't work." Usually what happened is the plan got approved and then handed to whoever had the least on their plate that month — not because they were wrong for it, but because nobody had actually scoped what building it would take.

The plan is the easy part to get excited about. The build is where donors actually notice something changed — because it's the part they experience. A segmentation strategy doesn't retain anyone until it's actually running in the CRM. A recovery sequence doesn't save a lapsing donor until the emails are written, scheduled, and tested.

If you've got a plan sitting in a drive somewhere that made total sense in the room and hasn't moved since — that's usually not a strategy problem. It's a Build problem. And it's the most fixable kind.

Ellena Fortner Newsom is a fractional digital fundraising consultant and founder of Nonprofit Bestie. Reply or book a time if you've got a plan that needs someone to actually build it.