Thought Leadership · 15 September 2026 · 4 min read
What a Barangay Taught Me About Systems
A hall that runs on borrowed chairs and unspoken obligations is still a system. Policy that ignores this will not survive contact with it.
Before nursing school, I thought systems were things you designed. Then I watched a barangay captain handle a drainage dispute, a funeral, and a vaccination schedule before lunch, mostly from memory and a notebook.
Formal and informal
Every barangay runs two systems at once: the documented one that appears in reports, and the human one that actually moves. Health workers know which household will not open the door. The treasurer knows which families will pay after harvest.
Programs that arrive with only the first system stall immediately. The people they were designed for are living in the second.
Designing with the grain
The lesson I keep returning to is that you do not introduce a system to a community; you join one that already exists and then try not to break it.
That means building on the relationships already doing the work — the nutrition scholar, the volunteer midwife, the teacher everyone already trusts with the truth.
It means accepting that some of the strongest infrastructure in the Philippines is unpaid.
And it means writing policies that assume goodwill is scarce and time more so, because those are the constraints the good ideas have to fit inside.
A note on measurement
The instinct to prove impact is a good one, and it is also where most small initiatives die. If the only thing that counts is a number a form can capture, you will end up optimising the form.
What I want to measure instead is durability: does the thing still happen when I am not in the room? If the answer is no, it was a project, not a system.
Written by Mark Condino
Get in touch ↗