Shifting paradigms in development: embracing the PDIA approach

How development is done right now, and the problem with it

Most development interventions follow an almost fixed pattern: specialists conduct studies to decide on a “solution,” pre-design it for the context it will enter, and then move to implementation. It’s a linear sequence, and we think it leaves limited room for either real learning or adaptation along the way. The large majority of development projects begin life as a solution already presented at the proposal stage, following that same set pattern. Some of these approaches have produced real successes, but they usually come with gaps: in what gets learned along the way, in how far stakeholders are genuinely involved, and in the other processes that would otherwise strengthen a project’s outcomes and its odds of lasting.

The PDIA philosophy and approach

Building organisations’ ability to implement increasingly complex interventions is one of the development sector’s current hard problems, and it isn’t one that quick-fix project processes are built to solve. Effective, lasting solutions to complex issues have to account for the interplay of local context, politics, history and culture, which is exactly why Problem-Driven Iterative Adaptation (PDIA) argues that the right solution is rarely a generic institutional blueprint or a universal “best practice” technique waiting to be dropped in.

Finding a solution that actually fits a complex problem starts with identifying multiple candidate ideas, then testing them experimentally, in a way that allows genuinely new hybrids to emerge. PDIA tries several approaches at once rather than committing early to one. Take teenage pregnancy as an example: policymakers and would-be reformers can try new ideas, learn what works and why, adapt those ideas, and repeat the cycle until something that actually fits emerges. Building the capability to work this way takes time. Iteration begins with identifying initial action steps, building on problem analysis and idea-generation work already done, and those first steps need to be specified precisely enough that what happens next, and what gets repeated, is clear. The questions that should recur throughout are simple: what was achieved? What was learned? What comes next?

Underneath all of this sits one more test that’s easy to skip: whether an idea is politically and administratively possible to implement in this specific context: whether the people who would carry it out actually know how to, and whether the solution has been shown to work in a setting like theirs, not just somewhere else.

To sum up

PDIA rests on continuous learning and on constantly checking an idea against the political and administrative reality of the context it’s meant to serve. The repeated cycles of action, and the sustained involvement of the people the project affects, are what make it a stronger way to implement development work than a fixed blueprint applied on faith. PDIA doesn’t offer a shortcut; it offers a set of tools for building development solutions that are actually built to last.