Watch a single decision move through a response and you can see the seam. A field team identifies a need and writes it up. It travels to a country office, which reframes it for a regional layer, which packages it for headquarters, which translates it for the funder. Then the answer comes back down the same staircase, reshaped at every landing. By the time it reaches the people who raised it, the question and the answer have each passed through several hands and several priorities. We tend to treat that loss as the cost of being a large organization. It is closer to the cost of running two of them.
Most responses operate, in practice, as two systems wearing one logo. There is the world of the field, organized around the situation in front of it, and the world of headquarters, organized around the funder, the board, and the global picture. Each is internally coherent. The problem is the translation layer between them, where the field converts reality into the language headquarters needs, and headquarters converts strategy into instructions the field can follow. The handover between these two worlds is where context goes to disappear, quietly, in the space between formats.
This is not a complaint about headquarters, and it is not a claim that the field is always right. Both layers do necessary work. A center can hold the funding relationship, keep standards coherent across countries, and see patterns no single response can. A field team holds the situated knowledge no center can manufacture. The waste is not in either layer. It is in the seam between them, and the seam is something we designed and can redesign.
The handover tax
Every handover carries a tax. Part of it is time: each translation adds a wait, and the waits stack into the weeks that separate a need from a response. Part of it is fidelity: each retelling smooths the rough edges, and the rough edges are often the most important information, the friction a distant decision-maker most needs to feel. And part of it is ownership. When a decision passes through enough hands, no single hand owns it, so the field team ends up accountable for a plan it did not fully shape, using money it cannot fully move, on a timeline it did not set. Responsibility spread that thin across the staircase stops being responsibility at all.
The cost compounds because the two worlds optimize for different things. The field optimizes for the situation. Headquarters optimizes for the system that funds and governs it. Both are rational. But when they are wired as separate machines joined by a translation layer, every exchange becomes a negotiation between two logics rather than one organization solving one problem. The people we serve experience the result as slowness and inconsistency, and they are right to.
A response should feel like one organization to the person it reaches, because to them it is. The seam between the field and the center is invisible to them and expensive to us.
Designing one operating model
The fix is not to flatten everything into the field, nor to centralize everything at the top. It is to design a single operating model where the two layers share one logic instead of translating between two. A few moves make that real.
Define where each decision actually lives, once. Much of the handover tax comes from decisions that have no clear home, so they travel up and down looking for one. Name, in advance, which choices belong with the field, which belong with the center, and which are shared. A decision with a settled home does not need to climb the staircase to find out who owns it.
Reduce the number of translations, not just their speed. Every layer that reframes a decision adds a tax. Where a layer exists only to convert one format into another, that is a layer worth questioning. The goal is fewer handovers carrying richer information, not the same handovers happening faster.
Let information move in its original form. A field report rewritten four times on the way up arrives clean and hollow. Building ways for decision-makers to hear the unfiltered version, closer to the source, keeps the friction that matters from being sanded off before it lands.
Measure the seam, not only the ends. We track what the field delivers and what headquarters reports. We rarely track the time and meaning lost in the handover between them. Naming that loss, and treating it as a cost to reduce, turns an invisible tax into something we can shrink. The people who fund this work gain a cleaner line from intent to delivery when the seam is tighter, not a murkier one.
None of this dissolves the difference between the field and the center. The two layers do different jobs, and they should. It changes the relationship from translation to collaboration, so a response runs as one organization solving one problem rather than two negotiating across a gap.
Closing the seam is not a contest over who holds the power. It is making sure the context a field team gathers is still intact by the time it shapes the decision, and that the center’s wider view reaches the field without flattening what the field can see. One response, owned together, is the version that serves the person at the door.