Inclusion is often spoken about as a principle, something an organization believes in, commits to, and occasionally reports on. It appears in values statements and strategy documents, framed as an aspiration that signals intent. But in practice, inclusion does not behave like a principle. It behaves like a system. And when it is treated only as a principle, it remains dependent on goodwill, leadership attention, and isolated initiatives that may or may not survive changes in budget, personnel, or priorities.
Many institutions can articulate why inclusion matters, yet struggle to show how it is embedded in the way decisions are made, resources are allocated, and accountability is enforced. This gap is where most inclusion efforts stall. The organization may have strong language around equity and participation, but still operate through processes that reproduce exclusion in subtle and consistent ways. Hiring pipelines that look open on paper but privilege certain networks. Consultation processes that invite voices but do not shift decisions. Budgets that acknowledge marginalised groups but rarely follow through with meaningful allocation. The contradiction is not usually in intent; it is in design.
The challenge with treating inclusion as a value is that values do not enforce behaviour when trade-offs emerge. When pressure increases, budgets tighten, or timelines shorten, values alone are not what determine outcomes. Systems are. A system determines who gets heard, whose input counts, and what gets prioritised when competing demands arise. Without systems that actively structure inclusion, even well-meaning organizations revert to default patterns, which tend to reflect existing power structures.
This is why inclusion that depends on individual champions is inherently fragile. It rises when leadership is attentive and declines when attention shifts elsewhere. It appears in pilot programmes, workshops, and campaigns, but rarely stabilises into institutional practice. Over time, it risks becoming performative—visible enough to report, but not strong enough to transform outcomes. The organisation may be able to demonstrate activity around inclusion, but not necessarily change in who benefits, who participates, or who holds influence.
Read also: Social Impact Design for stronger social sectors in Africa
When inclusion is understood as a system, the focus shifts from expression to design. It becomes about how the organisation is structured in practice. Who sits in decision-making spaces, and whether those spaces are actually empowered. How budgets move, and whether they reinforce or redistribute opportunity. How processes are designed, and whether they assume uniform access or recognise unequal starting points. How accountability is defined, and whether inclusion has consequences attached to it or remains optional.
Inclusion as a system also means recognising that exclusion is not accidental. It is produced through routine organisational choices that accumulate over time. The way recruitment is designed can systematically filter out certain profiles. The way meetings are scheduled can exclude those with different time constraints. The way language is used can limit participation. Even well-intentioned processes can produce consistent patterns of exclusion if they are not intentionally designed otherwise.
This is why symbolic gestures, while visible, are insufficient. Training sessions, awareness campaigns, and representation targets may signal intent, but they do not automatically change how decisions are made or how resources flow. Without structural alignment, they risk becoming surface-level activity layered over unchanged systems. The organisation may look more inclusive externally, while internally the underlying architecture remains intact.
Seeing inclusion as infrastructure rather than aspiration shifts the responsibility. It becomes less about encouraging inclusive behaviour and more about building systems that make exclusion difficult to sustain. It requires asking harder questions about how power is distributed, how decisions are justified, and how outcomes are tracked. It requires moving beyond participation as consultation toward participation as influence, and in some cases, shared decision-making.
Ultimately, inclusion is not defined by what an organisation says about itself. It is defined by what its systems consistently produce. If the systems remain unchanged, the outcomes remain predictable, regardless of intent. But when the systems are redesigned—when decision-making, resource allocation, accountability, and learning are intentionally structured around equity—then inclusion stops being an aspiration and starts becoming an operating reality.