We get a version of this question in every funder pitch, every conference Q&A, every cold email from a sceptical academic: Is "Applied Intersectionality" just intersectionality with a marketing varnish on top?
The honest answer is no, but we understand why the question keeps coming. The development sector has a long history of taking precise scholarly frameworks and dilating them into branded slogans that do most of their work as identity signals. It happened to "systems thinking", to "human-centred design", to "trauma-informed", and to half a dozen other concepts that arrived in the field with sharp edges and lost them within a funding cycle.
We’re trying not to do that. Here’s the test we apply: if a methodology can’t be operationalised — can’t change what shows up in a project plan, a budget line, a hiring decision — then it’s a vocabulary, not a method.
Where intersectionality came from
Kimberlé Crenshaw introduced intersectionality in 1989 as a framework for legal and social analysis. The original insight is structural: a Black woman’s experience cannot be partitioned into the sum of being Black and being a woman. The compound of those positions creates conditions invisible to either lens alone — and the legal and policy systems built around single-axis analysis kept missing them.
It is, at its root, an epistemic observation about what frameworks let you see and what they hide.
Where we extend it
Our argument is that the same epistemic observation applies to the systems people live inside. Water is not a hydrology problem. It is a hydrology problem compounded with governance, gender, climate, livelihoods, and health. Each of those facets shapes what counts as a "good" water solution, and any plan that ignores one will under-perform on the others — usually slowly enough that the donor cycle ends before anyone notices.
The move from people to systems is not a metaphor stretched thin. It’s an extension of the same observation about partitioning: when we draw an artificial boundary around a "water project", we make decisions invisible at the boundary that determine the project’s success.
What it changes operationally
This is where Applied Intersectionality earns its name. Concretely:
- Team composition. We don’t scope a water project with hydrologists. We scope it with hydrologists, governance experts, gender specialists, public health people, and community representatives — before the budget exists. We have walked away from contracts that did not allow this.
- Mapping before designing. Every project starts with a systems-mapping sprint. The map is on the wall before any solution is sketched. Half the time the leverage point is not what anyone arrived expecting.
- Multi-outcome targets. We don’t commit to "deliver clean water". We commit to deliver clean water and hold the gender ratio on the board and hold the operating cost trajectory and survive a drought year. Single-outcome contracts are how you produce single-outcome results.
- Hand-off architecture. Community ownership is a milestone with a date on it, not a slogan. The constitution is a deliverable.
The harder thing
Applied Intersectionality also fails differently from buzzwords. When a buzzword fails, you can use it again next year on a different project. When the method fails, the failure is concrete: a board lost its women’s seats, an outcome metric reverted, a pump stayed off through a drought. We document those failures. We publish the ones we’ve survived.
That’s how you tell the difference between a frame that’s real and a frame that’s a varnish. The real one accumulates a list of mistakes. We’re happy to share ours.