top of page

n.V3-3.08 | FIVE DEFENSES

Writer: Robert "Pinto" Eikelboom
Robert "Pinto" Eikelboom
Jul 23
3 min read


01| Follow-up projects are the mechanism. They are not the whole defense. IkoCiti runs five, and they are layered deliberately, because evaporation has more than one cause and a single countermeasure would leave the others open.

02| First: MM360, against fragmentation. Impact evaporates when projects are designed in isolation — a well here, a training programme there, a clinic somewhere else, connected by nothing but a funding cycle. MM360 is the long-term barrio strategy that says where each project sits in a sequence: what it depends on, what depends on it, what it makes possible next year. No project is designed without an answer. Fragmentation is not untidiness; it is the reason isolated gains have nothing to hold onto.

03| Second: mandatory follow-up projects. Covered in the previous chapter. Maintenance is a funded, staffed, listed unit of production, not a paragraph in a handover document.

04| Third: the Barrio Assets Team, against invisible decay. Assets are tracked as a portfolio. Deterioration is caught while it is still repairable and generates a project. Nothing degrades unnoticed for three years and then gets written off.

05| Fourth: local ownership, against the exit problem. This is the one the sector structurally cannot copy. A professional who leaves takes their motivation with them — not from cynicism, but because their next contract is elsewhere and their reputation does not depend on what happens here. The Maveriq is not going anywhere. Her reputation on the platform, her income, her children's route to school, and her standing among her neighbours are all attached to whether the thing still works. Staying power is not something we designed into her. It is the natural consequence of ownership by people who live with the outcome.

06| Fifth: activism, against the budget problem. Public maintenance money exists. Getting it redirected toward the barrio is a political capability, and Maveriqs who understand the landscape and know the numbers are the ones to exercise it.

07| Now the objection, and Casey's finding from the evaporation chapter is the sharpest form of it. Community-driven development delivers goods and does not durably shift power. Why would we be different?

08| Our answer has to be structural, not aspirational. The CDD programmes Casey studied gave communities decision rights inside a programme that had an end date, while the funder retained the ability to override. Committees met because the programme funded the meetings. When the programme stopped, the arrangement stopped, because it had never been used for anything else.

09| IkoCiti's difference is that the decision rights are attached to production rather than to consultation. A Kikundi team selects its own projects, sets its own pace and recruits its own members without approval from the centre. The centre sets standards and curates quality; it does not approve decisions. And what the team is deciding about is its own income, which is a considerably more durable reason to keep deciding than a committee mandate.

10| There is a real caution buried in the research on decentralisation that we should hold onto rather than dismiss. Formally removing hierarchy does not remove the habit of deference. People who have spent decades on the receiving end of other people's decisions keep asking permission long after the org chart says they do not have to. The capacity is not missing; it has been conditioned out. That means the first years will look slower and more dependent than the design implies, and we should not read that as the model failing. We should read it as the shadow of hierarchy, and we should have said in advance that we expected it.

11| So: permissionless by architecture, not by policy. A policy of empowerment can be quietly reversed by a nervous manager in month eight. An architecture in which there is no approval step to reintroduce cannot.

12| Five defenses, and one test that decides whether any of it worked. Not whether the projects were completed — whether the change was still there years later. That is the next chapter, and it is where we are most exposed.

bottom of page