What it actually takes to get colleagues ready for AI

The council had an AI policy. What it didn’t have was a way to make sure anyone actually understood it, or what it meant for them day to day.

There’s a gap between a governance document and colleagues genuinely knowing what’s expected of them. Reading twelve pages of policy isn’t training. It’s just reading.

I’ve done enough mandatory online training courses over the years to know what bad looks like. Walls of text, a multiple choice question you can answer without reading anything, a certificate at the end that means nothing. I didn’t want to build that. I wanted something short, clear, and actually useful. Colleagues finishing it and knowing the dos and don’ts of AI at the council. That’s it.

I built it using Claude Code, which made the whole thing significantly faster than it would have been otherwise. HTML first, then converted to SCORM so it could sit inside Rugby’s existing LMS rather than live as a standalone file somewhere.

What I couldn’t do alone was the rollout. HR handled deployment, identified who needed to complete it, and managed the comms. That side is easy to underestimate when you’re focused on building. It made a real difference to whether it actually landed.

It’s not perfect. But people complete it, they know what’s expected of them, and there’s a record that they’ve done so. For something built by someone with no background in training design, that feels like the right place to land.