Picture the org chart the way we usually draw it. Headquarters sits at the top. The regional offices sit below. The field sits at the bottom, closest to the work and lowest on the page. The geometry is so familiar we stop seeing it, but the geometry teaches a lesson every day. It says the center commands and the edge complies. It says importance rises as you move away from the people the work is for. We did not choose that message on purpose. We inherited a shape, and the shape quietly governs how we behave inside it.
This is not an argument for abolishing the center. A headquarters does real and necessary work. It holds funding relationships steady, keeps standards coherent across many contexts, carries institutional risk, and connects parts of an organization that would otherwise never speak. The question is not whether the center should exist. It is what the center is for, and which way the service runs.
The inversion worth making
In most of our structures, the field exists to feed the center. It generates the reports the center needs, answers the questions the center asks, and translates its reality into the formats the center can process. A large share of frontline energy goes upward, into being legible to headquarters, rather than outward, into the response. We have built a system where the people closest to the crisis spend a meaningful part of their week serving the structure above them instead of the population in front of them.
Flip the question and the design changes. If headquarters exists to serve the field, then its core job is to remove obstacles the field cannot remove alone. Negotiating with funders for flexibility. Carrying the compliance weight so frontline teams do not have to. Building the shared systems, the surge capacity, the standards that no single office could maintain by itself. Under this reading, the center is measured not by how well it directs the edge, but by how much friction it takes off the edge’s shoulders. That is a different organization, even if not a single box on the chart moves.
What a serving center does differently
Three shifts make the inversion concrete, and none of them require dismantling anything.
Decide what genuinely needs scale, and keep only that at the center. Some functions truly belong where they can see across the whole. Common standards, the funding relationship, cross-context learning, surge that no single office can hold. Other functions drifted upward by habit and would work better closer to the ground. Naming which is which, honestly, is the first act of a serving center.
Measure the center by the burden it removes, not the activity it produces. A headquarters that generates more requests, more templates, and more clearances is easy to mistake for a busy one. The better question is how many hours it gave back to the field this quarter. A center earning its place makes the edge lighter, not heavier.
Let the field commission the center, not only the other way around. Build a real channel for frontline teams to name what they need from headquarters and to say when a central requirement costs more than it returns. When the service can be asked for, and declined, the relationship stops being command and starts being support.
A center earning its place makes the edge lighter, not heavier.
We should be straight that this is uncomfortable for everyone, including the people at the center who carry real expertise and real care. Being a service rather than a summit means measuring your worth by someone else’s lightened load rather than by your own visible output. That is a harder thing to feel proud of in the moment, and it is the more honest measure of whether the role is working.
The shape of an organization is an argument about what matters most. If what matters most is the person waiting at the door, then the structure should be built to serve the people closest to that door, not to be served by them. We drew the chart with the center on top. We can redraw what the center is for, and that redrawing is available to us now.