Workplace inclusion, engineered for proof

Where intent meets lived reality.

Most organisations already intend to be inclusive. What breaks down is the everyday behaviour in between — the ambiguous instruction, the meeting that moves too fast, the assumption made about a colleague nobody thought to ask. InclusionEdge builds that behaviour deliberately, then measures whether it held.

Inclusion is an engineering standard, not a values statement.

Exclusion at work is rarely hostility. It is a mismatch — between what a task demands and what a person can readily supply, under conditions the organisation set. A values statement cannot address a mismatch. A design standard can.

That reframe changes everything downstream. Roles become stacks of demands rather than single objects. Adjustment stops being an exception granted to an individual and becomes a correction that usually improves the role for everyone in it. And accountability lands with whoever designed the work — a specific manager, in a specific function, with authority to change it.

Read the full argument
The problem

Inclusion training has an evidence problem.

Long-running research into workplace diversity practice — most notably the multi-decade work of Frank Dobbin and Alexandra Kalev across several hundred organisations — points consistently to the same finding: one-off, compliance-driven, awareness-only training rarely changes what people do, and can entrench the defensiveness it was meant to remove.

01

Awareness isn’t behaviour

Knowing the definition of neurodivergence does not change how a manager responds when a colleague asks for something in writing rather than verbally, in a meeting already running late.

02

One session, no reinforcement

A single workshop with no manager layer, no leadership conditions and no measurement is a certificate exercise. It documents that something occurred. It does not demonstrate that anything changed.

03

Buyers are proof-hungry

HR and business leaders have been sold culture change with no way to verify it happened. They now ask for evidence before they ask for a proposal — and they are right to.

How we work

End to end, by one practice — because the seams are AI-first.

Discovery, design, co-development, delivery and impact measurement are not handed between departments. One practitioner runs the full arc, supported by infrastructure that absorbs the work a delivery team would otherwise carry.

That is not an operational footnote. It is why a single practice can deliver at the depth an MNC expects, and why the proof arrives with the programme rather than a quarter later.

See the full journey

Start with a diagnostic, not a proposal.

The first conversation is about where your organisation actually stands. Bring the problem; we will bring the framework.

Start a conversation