n.V2-3.09| BUILT TO STAY

BUILT TO STAY

01| Fighting urban poverty is a multi-generational problem, and multi-generational problems are not solved by temporary interventions. Yet temporary interventions are overwhelmingly what the sector delivers. Three-year programmes. Five-year grants. Project cycles that end while the problem they addressed continues into the next generation.

02| IkoCiti is built to be permanent, and permanence here is a structural commitment rather than an aspiration. A city does not install a water grid for five years. It installs it because clean water is needed indefinitely, and it stays until something better replaces it. The platform is a utility in the barrio on the same logic. It remains until disruptive innovation makes it obsolete or until people stop using it. Nothing else justifies its removal.

03| Permanence is not a maintenance promise. It is an outcome in itself. A child growing up in a barrio with permanent infrastructure sees something different from a child who watches programmes arrive and disappear. She sees a future that is not waiting to be cancelled, capable adults using tools that will still be there next year, and a horizon long enough to plan against. That shift — from intervention to presence — changes what a neighbourhood collectively believes is possible, and it costs nothing beyond staying.

04| It is also what makes every other claim in this book part credible. A self-perpetuating peer system cannot run inside a five-year grant cycle. A two-generation play cannot be delivered by an organization that may not exist in three years. A barrio asset portfolio cannot compound if the platform building it leaves before compounding starts. Without permanence, every claim here collapses back into the pattern the sector has already perfected.

05| Permanence has a hard edge we should state plainly. Local permanence is not guaranteed. A CITI can die when local funding dries up or when residents lose their urgency, even while IkoCiti continues. The commitment is that we do not withdraw. It is not a promise that every barrio succeeds.

06| The second structural commitment is that management does not have the last word.

07| Most platforms run top-down. Leadership decides, users adapt, and the only real form of dissent is leaving. The Escalation Right rejects that. The Global Management Team runs the platform and makes major strategic decisions. The Board provides oversight against founding principles and long-term interests. Between them sits a third source of accountability: the Ikosi — active users in good standing across Maveriqs, Impact Buyers, ecosystem partners and the rest — with the standing to force a decision back to the Board for review.

08| This is not a veto. Users cannot block a GMT decision directly. What they can do is compel a second look. Major decisions are pre-announced with a minimum window before implementation, which is what makes the right meaningful rather than retrospective — without the window it would be a complaints procedure. During that window, users review and discuss. If concerns are serious, a petition circulates. If it reaches a majority of active users, the Board reviews the decision and either upholds it or sends it back.

09| The threshold is high on purpose. A majority means the mechanism only fires when concern is genuinely widespread, which protects leadership from being held hostage by whoever is loudest while preserving the ability to stop something that is actually wrong.

10| How often it fires is itself diagnostic. Frequent escalation suggests leadership is disconnected from users, or the threshold is set too low. Never firing suggests either consistently excellent decisions — possible, but unlikely to hold forever — or that users have concluded the mechanism does not really work, which is the larger problem. Occasional use on genuinely significant matters is the healthy pattern.

11| It can break in two ways, both involving the Board. If the Board reflexively upholds management, the right becomes theatre and users learn to stop using it. If the Board overrides too readily, leadership cannot lead and strategy becomes hostage to whichever objection organizes fastest. There is no procedural fix for either. The Board's judgment, over time, is what determines whether this is accountability or ceremony.

12| The third commitment concerns who runs the organization, and it is the one most likely to be resisted internally. A peoples' business needs different leadership at different stages, and pretending otherwise out of loyalty is a reliable way for organizations like this to fail.

13| The concept stage needs a founder with conviction and the patience to think long. The build stage needs a builder — architecture, first hires, the thousand small decisions that determine whether the eventual platform is coherent or a patchwork. The reconnaissance stage, which runs for years and is where the model meets reality, needs a people person: a mentor and coach, not a strategist or an operator. The wrong fit here can quietly kill the whole project while the technology and the funding both look fine. The scaling stage needs executives who understand replication — how to reproduce what worked in one place twenty times without losing what made it work. The institutional stage needs leaders who can work inside government: long procurement cycles, political turnover, regulatory complexity, and the patience to operate inside bureaucracies without being absorbed by them.

14| Five stages, five different kinds of leader, one continuous principle underneath: leadership is matched to the stage, not to the organization's history. Technology supports this work and funding enables it, but at every stage the substance of it is human.