Field-First Strategy

We have all sat in the planning meeting that happened in the wrong room. The strategy was sound on the slide. It named the right outcomes, cited the right frameworks, and cleared every approval gate. Then it reached the field and bent in places no one had designed for, because the people who knew where it would bend were not in the room when it was drawn. This is not a failure of intelligence or intent. It is a failure of distance. Plans built far from the problem inherit the blind spots of that distance, and we pay for those blind spots in delay, in rework, and in the trust of the communities we came to serve.

The instinct to centralize is understandable, and often right. A capital can see across countries, hold the funding relationship steady, and keep a portfolio coherent. The problem is not the center. The problem is when coherence at the top hardens into rigidity at the edge. We write a twelve-month plan in conditions that have already changed by month three. We lock targets before we have met the people who will have to carry them. The field team then spends its energy translating reality back up the chain rather than acting on it, and the strategy quietly turns from a tool to be used into a document to be defended.

The cost here is not only operational. When the people closest to the crisis are treated as the implementers of someone else’s design rather than the authors of their own, we lose the one input no headquarters can manufacture: situated judgment. That is the knowledge of which road floods first, which committee actually speaks for a neighborhood, which promise the last agency broke and is still being remembered. It is the difference between a plan that works and a plan that only looked good.

Field-first is not a softer word for consultation. Consultation asks people to react to a plan that is already mostly written. Field-first means the people closest to the crisis hold real authorship and real authority before the plan is set. Concretely, that asks a few hard things of us.

It means pushing planning authority down to the level that actually holds the context, and funding the local time and analysis to use it well, rather than treating that work as something done for free on top of delivery. It means setting clear intent and firm guardrails at the center while leaving the route deliberately open, so frontline teams can change the how without having to reopen the why. It means building review rhythms that assume the plan will move: short cycles, measured in weeks rather than quarters, where a signal from the field can revise a target without a long approval climb. And it means we measure whether a strategy adapted in time, not only whether it was delivered as written, because in a crisis a plan that never changed is usually a plan that stopped listening.

None of this removes the center. It changes the center’s job. The work at the top shifts from drawing the route to setting the destination clearly, clearing the obstacles, and backing the judgment of the people on the ground. That is harder than it sounds, because it asks us to hold the discomfort of not specifying everything in advance, and to trust that authority placed closer to the problem is authority better used.

We should be honest that this trade has a price. A bendable strategy looks less tidy on paper. It does not offer a funder the clean comfort of a fixed twelve-month map, and it requires us to say plainly that we are planning for conditions we cannot fully predict. So we have a choice. We can keep buying that comfort with plans that break quietly in the field, or we can build for the world as it actually moves. The second is the more honest path, and in our experience it is also the one that works.

Plan the destination from anywhere. Plan the route with the people who can see the ground.

Scroll to Top