When a programme grows past a few dozen young people, support can't all flow through staff.
The programmes that stay human at scale build peer structures — and treat them as real infrastructure.
There is a size at which a youth programme changes character. Below it, staff know every participant by name and support flows through relationships. Above it — usually somewhere past fifty young people — the maths breaks: no support team can hold two hundred individual threads, and young people who feel like entries on a spreadsheet start behaving like entries on a spreadsheet. The programmes that stay human past that line share a design feature: they build peer structures, and they treat them as infrastructure rather than decoration. ## What Peer Structures Actually Do A peer structure is simple to describe: participants organised into small groups with a chosen or elected representative, meeting on a light rhythm, connected upward to programme staff. What it does is less simple, and more valuable. **Early warning.** A young person will tell a peer things they will never tell an official — the transport that fell through, the trouble at home, the host who crosses lines. Peer groups surface problems while they are still small, which is the entire economics of support. **Belonging.** Placements are isolating, especially distributed ones where each young person works alone at a small business. A peer group turns two hundred separate placements into a cohort — people who compare notes, encourage each other through the month-two wobble, and stay when they might have drifted. **A voice worth hearing.** Committees give participants a legitimate channel into programme decisions — raising patterns staff cannot see from records, and testing changes before they roll out. Programmes consistently improve faster when the people living them have a structured way to say so. > Records tell a programme what happened. Peer structures tell it what's happening. The difference is measured in drop-offs prevented. ## The Leadership Dividend Something else happens inside peer structures, quietly: the representatives learn to lead. Convening a group, carrying concerns upward honestly, standing between peers and authority with credibility on both sides — this is real leadership practice, of a kind no classroom module simulates. Across our work, committee members disproportionately become the programme's success stories: absorbed first, promoted first, and often the community's next generation of organisers. A peer structure is a leadership development programme hiding inside a support system, at almost no cost. ## Building Them So They Work Peer structures fail in two familiar ways: as tokens (a "committee" that meets once for a photograph) and as burdens (representatives loaded with staff work, unpaid and unsupported). The design that holds is modest and respectful. Groups small enough to be real — eight to fifteen. Representatives chosen by the group, not appointed by staff. A defined, limited role: connect, surface, represent — not administer, not discipline. A fixed channel upward that visibly responds, because nothing kills a structure faster than raising issues into silence. And small recognition — a stipend supplement, a certificate, a reference letter that names the role — because the work is real. In community-based programmes, these structures do one more thing: they persist. A youth committee built during a programme often outlives it, becoming part of the community's own fabric — exactly the kind of quiet asset a well-run project leaves behind. ## The Mechanics, Practically For programme designers wondering what this costs to run: very little, if it's built on tools the cohort already uses. Groups organise naturally in messaging apps; the structure adds is what matters — a named representative per group, a monthly rhythm (thirty minutes, an agenda of three questions: what's working, what's worrying, what needs deciding), and a standing slot where representatives meet the programme team together. Representative roles rotate or renew at fixed intervals, which keeps the position a service rather than a small kingdom. Record-keeping is one page per meeting, and the programme's response to raised issues is reported back at the next one — the loop that makes the whole structure credible. Budget-wise, the real items are a modest recognition for representatives, occasional venue and data support, and staff time for the upward meetings. Set against what the structure returns — early warnings, retention, and a leadership pipeline — it is consistently the cheapest capacity a large programme can buy. ## Where Abamandla Fits People systems are Abamandla's work, and peer structures are people systems — we design them, launch them, and support the young leaders who carry them. If your programme is growing past the size where staff can know everyone, that is not a crisis; it is the moment to build the structure that scales the caring. We are glad to help you build it.