How to become a DEI practitioner

Is this worth doing?

Inclusion work has a credibility problem that has almost nothing to do with whether it matters. Organizations announce commitments, run a session, and produce nothing anybody can point at a year later, which teaches everyone who watched that the work does not produce results. That is a measurement and mandate failure rather than a failure of the subject.

The practitioners who last are the ones who treat it as a discipline: a baseline, a small number of funded priorities, owners, and reporting that includes the quarter that went backwards. That is a learnable set of skills, and it is what separates being interested in this from being trusted with it.

Step 1: Choose your route in

The core skills are the same in each of these, and the constraints are not. Deciding which one you are aiming at changes what you build first.

Most people start inside an organization, often because the work landed on them rather than because they applied for it. That is a normal beginning, and it is the one this guide is written for.

Step 2: Establish the mandate

Before announcing anything, find out what you have actually been asked to change, who holds the budget, and what leadership would count as success in twelve months. Write their answer down in their words. Most of the time it is narrower than the title suggests, and occasionally it is something you would never have guessed.

Then find out what this will cost. A first year of cash lines is usually smaller than people expect, and the internal hours are usually larger. Both belong in the plan, separately.

The mandate conversation, the business case and the budget are Unit 3 of the course, and there is a free strategic plan structure to write it into.

Step 3: Take a baseline

An opinion about representation is arguable. A number is not, and the number is usually already sitting in a system somebody else owns. Ask HR what data exists, confirm with legal what you may lawfully hold where your people work, and agree a minimum group size below which you will never report a figure.

Get headcount by level rather than in aggregate, and hiring, promotion and exit numbers for the last two years even if they are rough. Whatever the data cannot answer is what listening has to cover, so write that list down too.

If you are considering advisory work rather than an internal role, the same rigour applies to your own pricing. This is what the work is usually charged at:

The measures worth reporting, and the small-numbers rules that keep them publishable, are covered in Unit 3 and laid out in the free metrics dashboard guide.

Step 4: Listen, and report back

People will tell you what is wrong once. If nothing visible follows, the second round gets polite answers and a lower response rate, and the goodwill does not come back cheaply. So decide what you will do with the answers before you ask anything, including what you cannot act on.

• Say who reads the responses and how they are anonymised, plainly and up front.
• Talk to people who left in the last year, not only to the people still there.
• Go where the work happens, including shifts that are not nine to five.
• Ask about specific decisions rather than about feelings in general.
• Report back within three weeks, including the parts that are uncomfortable to repeat, and name what you are not going to do.

Step 5: Pick three priorities and cost them

Everything is a candidate, so the discipline is subtraction. Sort what you found by how many people it affects and how much control you have over it, then pick no more than three for the first year and write down what you are consciously deferring.

Do the change that costs almost nothing first. Publishing pay ranges, fixing an application form that will not accept a name, sending interview questions in advance: a visible result is what buys the budget for the expensive things.

Step 6: Make it survive you

Initiatives that depend on one committed person end when that person changes jobs. Put every commitment into somebody's objectives, agree what happens when a manager simply does not do the thing they agreed to, and build the reporting rhythm before there is anything good to report.

The Advanced course covers the communications, compliance and governance work that mature programmes run on. If you are weighing up what the work pays, see what DEI roles and consulting actually pay.

Common mistakes to avoid

• Announcing before you have a mandate. A promise nobody resourced is the fastest way to be judged on it.
• Surveying with no plan for the answers. You spend your one round of goodwill and learn nothing you can act on.
• Training everybody before the decision-makers. It invites the obvious objection that nothing changed where decisions are made.
• Reporting activity instead of outcomes. Sessions run and people attended tells a sceptic nothing.
• Only reporting the good quarters. Credibility is built on showing the measure that went backwards.

Your first ninety days

1. Weeks 1 to 2: Establish the mandate, the sponsor and the budget, and write down what success looks like in their words.
2. Weeks 3 to 5: Take the baseline from systems other teams own, and agree the reporting thresholds before you see any results.
3. Weeks 6 to 9: Listen properly, then report back what you heard within three weeks of hearing it.
4. Weeks 10 to 13: Present three priorities with owners, measures and a cost, and get them approved in writing.

Follow that and you will have a funded plan rather than a set of intentions. To do it with the frameworks, the templates and a credential behind you, that is what the courses are for.