Traditional Authorities as Development Partners: Respect, Structure, and Shared Outcomes

Millions of South Africans live under traditional leadership, yet development programmes routinely arrive as if nobody governs the places they enter. Partnership with traditional authorities is not protocol — it is how work in these communities succeeds.

A significant share of South Africa's people — and a larger share of its deepest poverty — lives in communal areas under traditional leadership. Any organisation serious about upliftment will, sooner or later, work in these communities. Yet development practice has a strange habit: programmes arrive in traditionally governed places designed as though nobody governs them, treat the courtesy call to the traditional council as a box on a checklist, and then express surprise when the community's participation is thin and the programme's welcome thinner. The lesson our work keeps teaching is simpler and older: places have orders, and work succeeds by entering through them. ## What Traditional Authorities Actually Hold Set aside the constitutional debates that occupy conferences, and look at what a traditional council practically holds in its community. Convening power: the ability to gather households, legitimate an initiative, and make participation socially safe. Knowledge: who is genuinely vulnerable, which families carry which burdens, what was promised by previous visitors and what became of those promises — an institutional memory no baseline survey reconstructs. Land and facilities: access to the sites where programmes physically happen. And dispute resolution: when a programme generates conflict, as programmes among humans do, the paths to resolution run through structures that were there long before the programme and will remain long after. An organisation can work around all of this. It will simply work worse, slower, and more alone. > The question is not whether a community's traditional structures will shape your programme. They will. The question is whether they shape it as partners at the table or as weather you failed to forecast. ## Respect, Operationalised Respect in this partnership is not ceremony — it is a set of working practices. Arriving before the plan is fixed, so that leadership shapes design rather than receives it. Putting agreements in writing — purpose, roles, selection principles, sites — not because trust is absent, but because clarity is a form of honour, and successors on both sides deserve a record. Reporting back on a rhythm: the community that hosts a programme is owed its results, including the disappointing ones. And holding the line honestly where lines exist — selection criteria published and applied, programme governance retained by those accountable for it — because genuine partners can carry hard boundaries; it is vague ones that corrode relationships. We have found, consistently, that clear agreements deepen rather than diminish the relationship. Ambiguity is what breeds the misunderstandings that end programmes. ## Shared Outcomes, Shared Credit A partnership matures when its outcomes are owned jointly. The youth placed, the women's enterprises grown, the water point maintained — these are the community's achievements, convened by its leadership, supported by its partners, and they should be told that way. Organisations that harvest sole credit from communal soil rarely get a second season. The compact logic we have written about elsewhere applies here in miniature: development that lasts is development a community recognises as its own, and traditional leadership is very often the custodian of that recognition. ## Continuity Across Successions One practical matter deserves its own attention: leadership changes, on both sides. Traditional leadership passes through succession; NGO programme managers move on; corporate sponsors restructure. Partnerships that live only in personal relationships die with each transition — and communal-area programmes have been orphaned by exactly this, repeatedly. The protections are unremarkable and essential: agreements in writing and physically held by both parties; relationships built with the council as an institution, not solely with an individual; programme records that a successor on either side can read into; and the habit of periodic reaffirmation, where the partnership is restated with whoever now holds each seat. We have watched programmes survive successions on both sides because the paper and the habit were there — and watched others, built on warmer but undocumented relationships, evaporate in a season. Institutional memory is a form of respect too: it says the partnership was made with the community, and is meant to outlast everyone presently at the table. ## For Funders Reading This Corporate and government funders shape this partnership more than they know. Timelines that allow proper engagement, budgets that treat community liaison as real work rather than overhead, and patience with the pace at which trust is actually built — these are funding decisions, made far from the community, that determine whether respectful partnership is possible at all. A funder who demands communal-area delivery on urban timelines has ordered the corner-cutting they will later deplore. ## Walking With Ulift Ulift works in traditionally gov...