top of page

n.V2-3.04| FOUR STAGES, ONE CASCADE

Writer: Robert "Pinto" Eikelboom
Robert "Pinto" Eikelboom
Jul 27
4 min read


01| Capability does not grow smoothly. It moves through stages, each with a different psychology, a different level of work a person can absorb, and a different job for the platform. Skipping stages does not accelerate anyone. It removes them.

02| Stage one — the novice. She arrives uncertain, motivated and frightened in roughly equal measure, with no proof that she can do any of this. What she can handle is a very small project with clear instructions, immediate feedback, a short duration, and a visible result: a block cleaned, a survey run from a template, a meeting organized. What the success builds is not the clean block. It is the sentence I said I would do something, I did it, it made a difference, people noticed. The platform's job here is unglamorous — templates, handholding, fast feedback, and making sure the completion is marked rather than passed over.

03| Stage two — the contributor. Six to eighteen months in, confidence has a foundation under it. She can take moderate complexity, some independent decisions, a small budget, a project running over weeks rather than days, and a problem to solve rather than instructions to follow. A community garden that struggles for a season and then produces is worth more here than one that works immediately, because this is the stage where a person discovers she can learn things she does not yet know. That discovery arrives through experience. It cannot be taught.

04| Stage three — the leader. Two to three years in, she can run complex multi-stakeholder work with real budgets and real timelines, pitch to officials, absorb ambiguity, and hold a team together. She has started mentoring newer Maveriqs, which is where her own learning consolidates. The identity shift at this stage is the substantive one: she is no longer someone who responds to what happens in her barrio. She is someone who initiates.

05| Stage four — the innovator. Beyond three years, she creates project types rather than executing existing ones, builds things that outlast her involvement, develops other leaders systematically, and carries enough standing to influence how resources reach her neighbourhood. This is where multiplication starts, because a person at this stage is intrinsically multiplicative. One of her can carry ten to twenty people through the earlier stages.

06| Five mechanisms drive the cascade from one stage to the next.

07| Proof builds confidence. Each completed project is evidence against people like me can't. Cumulative evidence outperforms encouragement by a wide margin, because it is hers and it is checkable.

08| Skills transfer across contexts. Project management learned on a cleanup applies to a garden. Budget discipline learned on a garden applies to a household. Eventually the meta-skill — knowing how to learn an unfamiliar domain — emerges, and that is the one that transfers everywhere.

09| Networks multiply. The first project introduces her to other Maveriqs. Peer support makes the second easier. The third builds trust; the fourth produces an introduction; the fifth opens a door that capability alone would not have opened.

10| Visible success attracts resources. Reputation compounds inside a barrio faster than anywhere else, because everyone can see the work. Resources start following demonstrated capability rather than demonstrated need — which is, incidentally, the inversion the sector claims to want and structurally discourages.

11| Income creates bandwidth. Even modest earnings reduce survival hustle, and reduced hustle returns mental space. More bandwidth allows more complex work, which earns more, which returns more bandwidth. This is the least discussed of the five and probably the most important, because everything else in this chapter assumes a person has attention to spare.

12| Loops break, and they break in recognizable ways. Projects pitched too hard too early, where failure confirms the belief the whole system exists to disprove. Too much support too soon, where the participant succeeds but attributes it to the programme — outcomes achieved, capability not built, collapse on withdrawal. No progression pathway, where people master the entry level and plateau because nothing harder is available. Invisible success, where real capability grows in private and transmits to nobody. Isolation, where a person progresses without peers and has nothing to fall back on when a project goes wrong. Elite capture, where the programme selects the participants most likely to have succeeded anyway, and the rest of the barrio correctly concludes this is for special people. Brain drain, where the strongest Maveriqs succeed and leave, removing the models the next cohort needed. And no resource bridge, where capability accumulates but no external funding ever arrives, so ambition runs into a ceiling and stops.

13| Every one of those failure modes has a design answer, and most of them come down to the same three: size the work to the stage, make the progress visible, and keep the attribution with the person. You did this, with support is a different sentence from we did this for you, and the difference is the entire mechanism.

14| Two things about the numbers in this chapter. The stage durations are working assumptions, not findings — RECON exists to replace them with what actually happens. And the sequence itself is the claim we are most exposed on: if people do not progress through these stages at anything like this rate, the compounding argument in the previous chapter loses its engine.

bottom of page