In December 2015, Chennai had an unprecedented flood. At the time, I was a Teach for India fellow teaching third graders in Pulianthope, one of the city’s worst-hit areas.
Government relief had yet to arrive. So I did what I could: I used Facebook to raise relief supplies like food, medicine, and clothing from donors in Bengaluru, coordinated volunteers, and arranged for vehicles.
What I couldn’t do right away was make any of it reach where it mattered. The streets were flooded with sewage-infused water, access was uneven, and what looked navigable on a map was often impassable on the ground. Our car couldn’t move.
The community men with their ‘fish carts’, locally known as மீன்பாடிவண்டி, solved it. Movement wasn’t a constraint for them, nor did they need a map to navigate the flooded streets. They hauled their cart through the water, hollering in Tamil and distributing supplies. The community opened up to them in a way it never quite did for us.
We delivered all the supplies quickly. But I left that day with a discomfort I didn’t yet understand.
The work had been done, but not through me in the way I had, perhaps unconsciously, imagined. Decisions were made without me or my team’s involvement. The community responded to others, not to us. What I had brought mattered, but how it moved, where it went, and what it became was not in my control. When I tried to help directly, I encountered the limits of my outsider-ness that no amount of good intention could dissolve.
At the time, I told myself it was the chaos of a disaster. It took me longer to see what it actually was, and the naive assumption I hadn’t admitted to myself: that showing up and contributing would be enough to be received. That showing up with the right resources would translate into being trusted.
A decade of working in large public systems and the social sector has made me realise that this wasn’t a one-off misread. I kept seeing versions of the same response: communities engaging with outsiders on their own terms, regardless of the intent or effort brought in. Over time, reflecting on that pattern made a few things clearer to me.

Seeing is not understanding
The first thing I had to reckon with was the unexamined assumption most outside interventions carry: that seeing a problem clearly is the same as understanding it.
The outsider arrives with a diagnosis. Children aren’t learning. The community is flood-prone. The system is broken. And this diagnosis is often accurate. Because, distance frees them from two things that shape what insiders see and say: a tendency to normalise the dysfunction, and the social costs of naming the failure.
But that clarity has limits. Accurately identifying the problem doesn’t automatically translate into knowing what will work in a particular context. Our needs assessments tend to confirm what we already suspect. Our theories of change reflect our own mental models and unexamined blind spots, not the community’s lived history, relationships, and invisible constraints. A literacy programme would assume that appropriate training would enable teacher adoption of a new method, without accounting for the fact that teachers are evaluated on syllabus completion rather than learning outcomes. The result is an intervention built on a correct observation, but an untested assumption. And the gap between these two things is where most programmes fail.
The need for validation shapes what gets built
The outsider’s limitations don’t stop at what they know. Underneath runs something less visible and more personal. It’s a need we don’t fully name: to be received, to be seen as useful, to have the effort validated by the community and funders.
I felt it that day in Pulianthope—the emotional pull to stay central to what was happening, to be the one the community turned to, even after my role was actually done.
When unexamined, that need could move from the personal to the structural. The solution that gets prioritised is the one that’s visible, fundable, and demonstrable on a site visit. The milestones tracked are often the ones that satisfy a funder’s reporting cycle, not those that reflect the community’s actual progress. The need to matter can itself become what the programme is built around, which could be entirely different from what the community wants it to be built around.
When named honestly, that need loses some of its grip on the design. And a programme designed with that awareness tends to ask harder questions of itself: about who it’s actually serving, and what it’s actually building towards.
Reception is earned, never automatic
The outsider can raise resources, map failures, and design the ‘perfect’ intervention. None of it reliably lands until the community decides whether, and how, to receive it. And they decide on terms the outsider can seldom fully see or control in advance.
Those terms often live in unwritten rules: whose voice carries legitimacy, which local leaders must be consulted, and whether the intervention strengthens or undermines existing relationships and authority. Of course, in extreme emergencies, raw necessity can sometimes override these rules. But even then, acceptance often flows through existing networks of trust.
What an outsider experiences as hesitation, silence, or resistance is frequently the community protecting its own dignity and social fabric. The outsider’s solution can easily feel like an intrusion or a judgement on how the community has managed so far.
Over the years, I’ve watched programmes with flawless logic meet limited uptake because they were offered, not invited. During the floods, our supplies mattered, but a lesson I learned later was that being useful meant earning the right to participate, rather than assuming our presence equals permission.
The outsider’s presence itself does things they can’t fully control
Even when all of the above are acknowledged and accounted for—entering with humility about what one knows, naming the ego, and earning the community’s reception—something remains that self-awareness alone cannot fully resolve.
The outsider’s presence reorganises the social field just by existing in it. The outsider comes with resources, which signals opportunity (more books, food, clothes) for some, and for others—particularly those who hold existing authority—a threat. And alongside this, there is usually the novelty or charisma factor that commands attention in ways that have nothing to do with the programme’s design, and everything to do with someone from the outside entering a system in equilibrium.
Some of this disruption creates possibilities. Some of it causes damage that becomes visible only later. And these don’t cancel each other out. They coexist, often inseparably, the way employment and environmental harm coexist around a factory.
That day in Pulianthope planted the seed of the question that I have carried with me through a decade of work across repeated cycles of diagnosis, design, validation-seeking, and negotiating acceptance: What does it mean to be useful when you don’t belong?
I’ve learned that being useful as an outsider is a discipline. It’s less about what you bring and more about what you’re willing to reckon with: the limits of your seeing, the needs you’re carrying, the disruption your presence causes, and the community’s right to decide whether any of it is welcome.
The discipline is uncomfortable because it asks the outsider to remain uncertain in contexts that reward confidence. The system pushes you toward answers before you’ve earned the right to have them. The harder thing, and the more courageous thing, is to move forward while holding the question open. To act without letting the pressure for confidence close off the honesty that makes the work worth doing.
This isn’t an argument against outside intervention. Communities need resources they can’t always generate internally, and systems—institutions, governments, communities—have blind spots that those working inside them can’t always see clearly.
The motivation to show up need not be entirely selfless either. Genuine care mixed with the need to feel useful is human, and it gets people to look at issues they wouldn’t otherwise touch.
What matters is what happens after. Whether you bring what the situation actually needs from you rather than what you want to be known for bringing. Whether you’re willing to measure your work by what continues after you’ve left than what you built while you were there. That’s a harder standard. And the one worth holding yourself to.
—





