The Operations Bridge

Point sixteen. If I had to explain why some teams get fluent with AI and others stall after the kickoff, it comes down to reps versus rollouts.

The rollout mindset versus the reps mindset

A rollout is an event: a big training day, a platform launch, a memo that says we’re an AI company now. It feels like progress because it’s visible and it’s scheduled. But I’ve watched enough Kaizen weeks drift back to the old way to distrust the energy of an event. Fluency isn’t installed in a day. It’s the residue of a hundred small, unglamorous uses — the same reason Coaching Kata builds an improvement habit that stand-alone events never quite do.

Small daily reps compound

The person who uses AI on one real task a day isn’t ahead because of any single task. They’re ahead because a hundred small reps later, they’ve built an instinct for what the tool is good at, where it lies to you, and how to hand it a problem. That instinct can’t be transferred in a slide deck. It has to be earned in reps, and it accumulates quietly in a way that’s easy to underestimate until you’re standing next to someone who has a year of reps on you.

Make the reps visible

The best thing I’ve seen leaders do here isn’t mandate usage — it’s make the reps visible and shared. Someone shows how they used AI to untangle a scheduling conflict in the huddle. Someone else steals the approach the next day. That’s how a practice spreads on a floor: not through a policy, but through people seeing a peer do something useful and quietly copying it.

A question for leaders

Stop asking “have we rolled out AI?” and start asking “how many reps did my team get this week?” One is an event you can check off. The other is the thing that actually compounds — which, not coincidentally, is where this series is heading.