Systems Thinking for Social Good: What a Decade in Banking Taught Me About Poverty

I spent over a decade as an engineer, delivering large technology programmes for global banks in the UK. It is not the background most people expect from someone who now runs an NGO. But it turned out to be the most useful training I could have had — because it taught me to see systems where others see individuals.

When a banking platform fails, no competent engineer blames the user. You don't write a memo asking customers to try harder. You trace the fault through the system — the inputs, the broken handoff, the feedback loop that quietly compounds a small error into a large one. The discipline is simple and unforgiving: behaviour is a property of the system, not a flaw in the person inside it.

Then I came home to India and looked at exclusion through that same lens. And the framing we use everywhere fell apart. We talk about poverty as if it were a personal failing — not enough effort, not enough skill, not enough ambition. But a person who can't get a first customer, a loan, or a fair price isn't a broken user. They're a capable person inside a system that keeps routing opportunity around them.

That is a profoundly more hopeful diagnosis. You cannot fix a person. You can absolutely redesign a system. Find the broken handoff — the missing bank account, the credential no one will recognise, the market that won't quote a fair price — and repair that, and the same person produces a completely different outcome. Nothing about them changed. The architecture did.

This is what an engineering background really gives you for social good: not the technology, but the refusal to blame the user.

So when something isn't working, the engineer's question is the one I keep asking:

Is this person failing the system — or is the system failing the person?