Inclusion Is an Engineering Standard, Not a Values Statement

Most organisational inclusion work begins with a statement of values. It is sincere, it is well-drafted, and it is almost entirely disconnected from the mechanism by which people are actually excluded.

Exclusion at work is rarely an act of hostility. It is far more often a mismatch — between what a task demands and what a person can readily supply, under the conditions the organisation has set. A values statement does not address a mismatch. An engineering standard does.

The reframe

Consider a role that requires processing verbal instructions in a fast-moving huddle. That is a task demand. It sits alongside dozens of others: sustained attention in an open-plan environment, rapid context-switching between unrelated priorities, reading unstated social expectations in a client meeting.

Some of those demands are genuinely essential to the work. Many are not — they are incidental, inherited from how the role happened to be designed rather than from what the role has to achieve. The distinction matters enormously, because incidental demands are the ones you can change without compromising anything.

Once you see a role as a stack of demands rather than a single object, the inclusion question becomes tractable. It stops being how do we feel about difference and becomes which of these demands are load-bearing, and which are simply how we have always done it.

Redesign happens at the task level, for a defined audience. Everything downstream of that is accommodation — useful, but reactive, and always arriving after someone has already struggled.

What changes when you take this seriously

Accountability moves. A values statement belongs to everyone and therefore to no one. A task demand belongs to whoever designed the role — which means a specific manager, in a specific function, with the authority to change it.

Measurement gets honest. Sentiment surveys tell you how people feel about the organisation’s intent. Task-level audit tells you what the organisation is actually asking of people. These are very different findings, and only one of them tells you what to fix.

Adjustment stops being exceptional. If a demand was incidental all along, removing it is not a concession granted to an individual — it is a design correction that usually improves the role for everyone in it. Written follow-ups after verbal briefings help the person who asked. They also help the colleague who was too junior to ask, and the one who was on leave that day.

The uncomfortable implication

This framing is less comfortable than a values statement, because it is falsifiable. You can check whether a task demand is essential. You can check whether it was removed. You can check whether the removal held six weeks later.

That is precisely the point. An organisation that treats inclusion as an engineering standard has to show its work — and an organisation that has to show its work tends to do better work.