Name the pattern.

A team came to us six months into an AI rollout. The dashboards were green. Adoption was up. The partner deck looked like a success story. And yet, in 1:1s, the same anxieties kept surfacing — people checking the AI's work twice, then a third time, before showing it to anyone.

We didn't need new metrics. We needed a name. Silent veto. The org could use AI; the org wanted to use AI; but somewhere in the unspoken layer of how work gets graded, AI-augmented behaviour was being quietly punished. Once named, the thing became actionable. Without a name it was a vibe — a thousand small frictions that nobody could justify raising.

This is the work. Not predicting what AI will do to people; not forecasting adoption curves. Naming the pattern people are already sitting in — so the move that follows can be deliberate rather than reactive.

Throughout this Journal we'll publish the names we've found. Some are ours; some are well-known elsewhere. None are secret. The naming is the small, slow part of the work — the part that compounds.