A control without an owner is a wish

When our firm rolled Claude out, we put one rule in front of every licence. No seat until you had done a fifteen-minute Workspace Tour and passed the quiz at the end. It was hosted in our LMS, completion was tracked, and everyone who finished got a badge.

It worked. Twenty of twenty-two licensed users came through it. The two who didn’t are the lesson.

The number: 20 of 22

The two who missed the gate were not refusing it. They were new starters who joined after the rollout. Nobody put them through the gate because nobody’s job was to put them through it.

The gate lived in the rollout project. The rollout project finished. New starters go through the onboarding checklist, and the gate was not on it. For those two people the control did not exist. Nobody decided to skip it. It stopped having an owner the day the project that created it closed.

That is fixed now. The gate is a step in new-starter onboarding, which has an owner who is still there after every project ends.

What else went wrong

The new-starter gap was the failure that mattered, but it was not the only one.

We planned two weeks to get 13 people through the tour. It slipped. The friction was human, not technical. People who learn by doing pushed back. They asked to be let into the tool while they read about it, not after. We held the line, and I am still not sure that was right. The gate stayed intact. We still don’t know what holding it cost in goodwill.

Day one had its own problems: seats and permission sets that weren’t set up right. None of it was hard to fix, but day one is when people decide whether a new tool is worth their effort.

What went right

The gate itself. Fifteen minutes is a small ask, and a quiz with tracked completion meant the answer to “has everyone been through it?” was a number, not a guess. Twenty of twenty-two is a number we can stand behind. Without the gate we would have had an impression.

What we would do now

Put the gate in onboarding on day one, not in the project plan. A rollout project is temporary by design. Anything it creates that has to keep working afterwards needs a permanent home and a named owner before the project closes. Training is the obvious one. The AI policy is another, and it failed the same way: the copy Claude read stayed four months out of date.

We would also check the seat and permission setup with a handful of people the week before launch, not with everyone on the day.

We would keep the gate. We would talk to the people who learn by doing before launch, not during it.

One thing to try this week

Open your new-starter checklist and look for the AI training step. If it isn’t there, the next person who joins will miss it. Add it, and put a name next to it.

If you are earlier than that and haven’t rolled Claude out yet, start with three things to do before you roll out Claude. The third one is this lesson.