Designing for durability: a systems-based project methodology derived from the sustainability failures of INGO projects in Ethiopia
This article proposes the Sustainable Systems Project Design and Implementation Methodology, a new framework derived from a mixed-methods analysis of sustainability failures in Ethiopian INGO projects, which addresses six identified systemic gaps by integrating strategic design, adaptive delivery, and community-owned learning to ensure long-term project durability.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Development projects are the engines of modern aid, bringing clean water, schools, and healthcare to communities that need them most. These initiatives are usually run by international organizations working in partnership with local groups. For decades, a persistent problem has shadowed this work: once the external money runs out and the foreign experts leave, the projects often stop working. The pumps break, the schools close, and the services vanish. This is not a mystery of human nature or a lack of goodwill; it is a failure of design. The way these projects are planned and managed often treats long-term survival as an afterthought, something to be figured out only when the funding is about to expire. The question researchers have long asked is how to build something that lasts without needing a permanent external hand to hold it up.
A researcher named Beniam Tilahun Jenber set out to solve this management puzzle by looking at what actually went wrong. He studied ten development projects in Ethiopia that had recently finished their funding cycles between 2015 and 2025. Instead of just asking the project managers if they thought they had succeeded, he dug into the hard records, surveyed hundreds of staff members, and interviewed the people who had lived through the projects. He found a startling gap between what people said they were doing and what the documents showed had actually happened. In many cases, the teams reported using sophisticated, "systemic" methods to ensure sustainability, yet the final evaluations showed that the projects had collapsed the moment the money stopped. The evidence pointed to six specific failures: the teams were not designing for financial survival, the transition from foreign control to local ownership was too sudden, and the depth of local commitment was far shallower than claimed.
From this evidence, Jenber constructed a new way of working called the Sustainable Systems Project Design and Implementation Methodology. Think of it as a complete overhaul of the project blueprint, shifting the focus from delivering a set of tasks to building a system that can survive on its own. The core idea is that sustainability must be engineered from the very first day, not added as a final step. The new method organizes the entire project life cycle into three interconnected parts. First, there is a design phase that acts as a strict filter, asking three simple but tough questions before any work begins: Can the community physically reach the service after the project ends? Can they afford to keep it running without outside money? And do they truly understand and want to keep using it? If the answer to any of these is no, the design must change before moving forward.
The second part of the method deals with the actual work while the project is running. Instead of just ticking off a list of activities, the team constantly checks if they are building local capacity and sharing power. A key innovation here is a map that tracks exactly who holds the power to make decisions. In traditional projects, the international organization often keeps the keys until the very end. This new method requires that the map of authority be drawn at the start and that the transfer of decision-making power to local partners be tracked as a measurable goal, just like a budget or a timeline. This ensures that local groups are not just helping out but are gradually taking full control of the system.
The third part is a learning system owned by the community itself. In the past, reports were written by outsiders to satisfy donors, often missing the real story on the ground. This new approach requires the community to generate their own evidence and review their progress together with the project team. This creates a feedback loop where the people using the service can say, "This is not working," and the project can adapt immediately. The method also includes a specific, funded phase for the transition period, recognizing that the moment a project ends is not a cliff edge but a bridge that needs to be built and paid for in advance.
The study found that while the new methodology has not yet been tested in the field to prove it works better than the old ways, it is built directly on the specific failures of the past. It addresses the exact gaps found in the ten Ethiopian projects, such as the lack of financial planning and the abrupt cutoff of support. The researcher is careful to state that this is a proposed solution, not a proven cure. The evidence suggests that the old way of relying on self-reports from project managers is unreliable because it often hides the truth about how shallow the local ownership really is. By shifting the focus to community-generated evidence and making the transfer of power a visible, tracked part of the design, the method offers a plausible path forward. It treats the project not as a temporary delivery of goods, but as a temporary intervention designed to leave behind a system that the community can own, manage, and sustain long after the international partners have gone.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.