We have learned to say that relief, development, and peace belong together. We have not yet built an organization that behaves as if that were true.
The phrase is everywhere now. We write it into strategies and speak it at every gathering: the work of saving lives, the work of building durable systems, and the work of easing conflict are not separate missions but one continuous effort. As a sentence, it is right. The family we feed today needs a livelihood tomorrow and a community not at war with itself for either to last. But walk into the work behind the sentence and you find the opposite of integration. Separate teams that rarely meet. Separate budgets that cannot be combined. Separate plans, written on separate cycles, answering to separate reporting lines. We say one word and run three machines, and the seam between them is where people fall.
This is not a failure of belief. Almost everyone in the sector agrees the divisions are artificial. The gap is between the agreement and the architecture, and because the architecture is shared, it is ours to rebuild together. Our money arrives in separate streams, labeled for relief or for development, each with its own rules, timelines, and definitions of success. Our organizations are built to match those streams, with a humanitarian side and a development side that often barely speak. The structure was inherited from a time when the categories felt clean, and it persists because everything around it, the funding, the reporting, the career paths, still rewards keeping them apart.
Why the silos outlive the slogan
The deeper problem is that integration has no owner and no budget, while the silos have both. A relief grant pays for relief and is measured on relief outcomes. A development grant does the same. Neither one pays for the patient work of stitching them together, so that work falls into the gap between them, done informally if at all. We have made the connected approach everyone’s aspiration and no one’s job. And a thing that is everyone’s aspiration and no one’s job does not happen.
There is a measurement problem layered on top. Each stream counts its own results in its own terms, which means no one measures whether the handover between them actually worked. A relief program closes when its targets are met. A development program starts when its funding lands. Whether the family was carried smoothly from one to the other, or dropped in the gap while the two cycles failed to align, is no one’s indicator. So the most important moment, the join, is the one moment nobody owns.
Building the join, not just naming it
The fix is to give the connection a structure, a budget, and an owner, rather than leaving it as a value we all admire and none of us run. A few moves make that concrete.
Plan around the person across time, not the program in its silo. Build a single picture of what a community needs from immediate relief through to durable recovery, and design the streams to serve that picture together, rather than writing three plans that never reference each other. The continuity belongs to the people we serve, so the plan should start from them.
Fund the handover, not only the phases. Where money must arrive in separate streams, make the transition between them an explicit, resourced responsibility rather than a gap each side assumes the other will cover. Funders gain directly here, because relief that collapses for want of a development follow-on is relief paid for twice.
Measure whether the join held. Track the transition itself, whether people were carried from emergency support into lasting recovery without falling through, and treat a clean handover as a result worth counting. What we measure at the seam is what we start to get right at the seam.
Let the teams share a table and a plan. The humanitarian and development sides do not need to merge, but they do need to meet early, plan together, and know what the other is doing in the same place. Integration starts as a conversation that currently is not happening.
We have made the connected approach everyone’s aspiration and no one’s job, and a thing that is no one’s job does not happen.
None of this asks us to collapse genuinely different kinds of work into one undifferentiated whole. Relief, development, and peace are distinct crafts, and pretending otherwise would weaken all three. It asks only that we build the bridges between them with the same seriousness we built the pillars.
The test is honest and uncomfortable. If we say relief, development, and peace belong together in every strategy and still run our relief and our development as two organizations that do not speak, then the words are decoration. The sentence is true. The work left is to make the structure say the same thing, and we can begin at the next plan we write.