The practical version is simple: remove barriers, widen access, and measure whether people can contribute on fair terms
- The UK baseline is legal as well as cultural: the Equality Act 2010 and the public sector equality duty shape what public bodies must do.
- DEI is not one initiative. The biggest gains usually come from recruitment, reasonable adjustments, progression, and accessible service design.
- One-off training rarely shifts outcomes unless it changes how managers hire, reward, and run meetings.
- Progress should be tracked by grade, function, location, and protected characteristic where data is safe to use.
- A strong plan is usually simple: 30 days to diagnose, 60 days to change practice, 90 days to prove movement.
What DEI means in a UK public-sector setting
At the legal level, the baseline is clear. The Equality Act 2010 and the public sector equality duty require public bodies to eliminate discrimination, advance equality of opportunity, and foster good relations. In plain English, that means the work is not only to avoid harm; it is to design systems so that different people can apply, speak up, progress, and access services fairly.
GOV.UK’s guidance makes the point well because it ties law to working practice rather than leaving DEI as a values statement. There are 9 protected characteristics in the Act, and many teams also look at socio-economic background because a workplace can be lawful and still feel closed to people with fewer networks, less confidence, or less flexibility. I think that distinction matters: compliance keeps you safe, but inclusion changes outcomes.
| Baseline | What it means in practice | What leaders should check |
|---|---|---|
| Equality Act 2010 | No direct or indirect discrimination on the protected characteristics | Are recruitment, promotion, and service decisions defensible and consistent? |
| Public sector equality duty | Three duties: eliminate discrimination, advance equality of opportunity, and foster good relations | Are equality impacts considered before decisions are locked in? |
| Reasonable adjustments | Support changes people need to do their jobs or use services fairly | Can people request support without delay, friction, or stigma? |
| Accessibility | Services, documents, and digital tools should work for more people by default | Can people use the system without needing insider knowledge or special help? |
| Equity | Different barriers may need different support | Are you treating everyone the same, or treating barriers seriously? |
Once that frame is clear, the next step is choosing the actions most likely to change behaviour rather than just reassure stakeholders.
The actions that change outcomes fastest
In my experience, the quickest gains come from process changes, not awareness campaigns. Government Project Delivery guidance says to build equality, diversity and inclusion into working practices, solutions, and outcomes, and that is exactly where I would start: the points where people apply, get heard, or are turned away by friction. If time is limited, focus on the actions below before you add anything else.
| Action | What it changes | First move |
|---|---|---|
| Structured recruitment | Reduces subjectivity and the influence of “fit” language | Use scored criteria, consistent questions, and a diverse panel where possible |
| Transparent promotion criteria | Makes progression easier to understand and challenge | Publish what good looks like and calibrate decisions before they are finalised |
| Reasonable adjustments | Removes avoidable barriers for disabled staff and service users | Give people one clear route to request support and one owner to manage it |
| Accessible meetings | Improves participation and quality of challenge | Send agendas and papers early, use captions where needed, and leave time for quieter voices |
| Inclusive service design | Prevents exclusion before complaints appear | Test with real users from the groups most likely to face friction |
| Data review | Shows whether the work is changing experience | Track outcomes by grade, function, location, and protected characteristic where safe |
If I had to pick only three starting points, I would choose recruitment, adjustments, and meeting design. Those are visible quickly, they affect daily experience, and they send a signal about whether inclusion is real or just aspirational. If those three are right, the rest of the system has a much better chance of following.
How to make policies usable, not just compliant
Policies fail when they are written as declarations and then handed to managers with no operating instructions. I usually check three things: can a new starter understand the rule in one minute, can a line manager apply it without special knowledge, and can the person affected use it without having to ask the same question three times? That is where reasonable adjustments, accessibility, and plain language matter.
- Write the process, not just the principle. Say who owns it, how people request support, and what turnaround time they should expect.
- Make adjustments normal. Under UK law, reasonable adjustments can include changes to buildings, policies, procedures, and staff training, not just equipment.
- Build accessibility in from the start. If forms, PDFs, intranet pages, or meeting packs are hard to use, people experience exclusion before they ever speak to a manager.
- Use inclusive language with care. The goal is not to make everything bland; it is to stop assuming one experience is the default.
- Train managers on scenarios. A short case-based session is usually more useful than a long slide deck.
- Carry the standard into procurement. If suppliers interact with your staff or users, their processes should not undo your internal standards.
For public bodies, digital accessibility deserves particular attention because it is one of the quickest ways to turn a good policy into an unusable one. Once the policy works on paper and in practice, you can start measuring whether it is changing experience rather than just intent.
What to measure so you can see progress honestly
The mistake I see most often is measuring what is easy instead of what is changing. Headcount alone tells you very little. You need a small dashboard that shows who applies, who progresses, who stays, and who can use the system without friction. That usually means combining numbers with short qualitative feedback, because small groups and uneven turnover can distort the picture.
| Indicator | What it tells you | How often to review |
|---|---|---|
| Hiring funnel by stage | Where candidates drop out or get screened out | Monthly or quarterly |
| Representation by grade and function | Whether diversity is concentrated at entry level | Quarterly |
| Promotion and pay data | Whether progression is fair and explainable | Quarterly for management review, annually for formal reporting |
| Retention and exit reasons | Whether people stay at similar rates and for similar reasons | Quarterly |
| Adjustment turnaround time | Whether support is usable in practice | Monthly |
| Speak-up and bullying or harassment data | Whether people trust the culture enough to raise issues | Quarterly |
If the sample is tiny, use 12-month rolling data and be careful about over-reading one quarter. I would rather see a simple dashboard reviewed consistently than a sophisticated report that nobody uses. The numbers tell you what changed; the common mistakes explain why change often stalls.
The mistakes that make DEI look busy but change little
I see the same mistakes repeatedly, and most are well intentioned. The problem is that they create movement without reducing barriers.
- Making training the strategy. Training can help, but by itself it rarely changes who gets hired, promoted, or heard.
- Tracking representation without fixing the pipeline. If hiring improves but promotion criteria stay opaque, the gap just moves upstream.
- Expecting marginalised staff to do all the work. Staff networks should inform the work, not carry it alone.
- Using positive action as a slogan. It can be lawful in specific circumstances, but it still needs a clear rationale and proper documentation.
- Calling the job done after a policy is published. A policy only matters when people can use it quickly and safely.
- Leaving middle managers out of the picture. They are the people who decide whether standards are normal or optional.
The fastest way to avoid these traps is to keep the work close to real decisions. Once you know where the friction lives, a short 90-day plan becomes much easier to run.
A 90-day plan for a manager or team lead
A 90-day window is long enough to prove momentum and short enough to keep focus. I would use it to diagnose, change, and then verify.
| Time frame | What to do | What success looks like |
|---|---|---|
| Days 1-30 | Audit hiring, progression, adjustments, and meeting practices; speak to 6-10 people across grades; identify the three biggest barriers | A clear baseline that leaders can agree on and act on |
| Days 31-60 | Change 2 or 3 high-friction processes, such as structured interviews, a standard adjustment route, or an accessible meeting template | People notice fewer delays, fewer surprises, and less ambiguity |
| Days 61-90 | Review the same metrics again, share what improved, and set the next quarter’s priorities | Evidence of movement, not just intention |
The point is not to launch a large programme. It is to prove that the team can remove friction in places people feel every week. If that works, the organisation gets something much more valuable than a campaign: a repeatable way of improving how work is done.
How to keep inclusion moving when the first push is over
When DEI lasts, it stops depending on one enthusiastic leader. It lives in recurring habits: line managers use the same criteria, data is reviewed on a schedule, adjustment requests are handled quickly, and service teams involve affected users before decisions are locked in. I do not care much which label an organisation prefers if the substance is unchanged; belonging, accessibility, and fairness still have to show up in recruitment, progression, and service design.
- Review the same core metrics every quarter, not only when attention spikes.
- Keep meeting and recruitment templates simple enough that busy managers actually use them.
- Bring staff networks or user representatives in early, before a solution becomes expensive to change.
- Make ownership explicit so DEI is part of normal management, not a side project.
If I were choosing the first place to invest effort, I would start with recruitment, adjustments, and data review. Those three areas show very quickly whether inclusion is becoming part of how the organisation works, and they give leaders a clearer basis for everything that follows.
