Everything Runs Through You (When the AI Lead Becomes the Bottleneck)
The Problem
Your AI program is working, and all of it runs through you. You run three sessions a week and answer questions in between. When IT writes eleven pages of AI guidelines, every new workflow has to be reviewed before anyone can share it, and the review queue has one person on it. You. Your best builder reads the email and stops posting what he builds. He's waiting until somebody approves it. Nobody has approved anything yet. You're working fourteen-hour days and you're faster than you've ever been. Adoption has gone flat anyway. People come out of every session on fire and slide back within six weeks, because nobody's sitting next to them anymore. You helped your experts stop being bottlenecks and never noticed you were turning into one.
The Principle
One person is one tap. If every path to the new way of working runs through you, the first Brent to codify is you. Donella Meadows taught us to think in stocks and flows. Your daily users are water in a bathtub. Sessions are the tap, and people drifting back to old habits are the drain. You can't fill the tub by running one tap harder. So write down what you do and give it away. Turn your session into a playbook anyone can run, and ask the respected people in each function to host. Replace the eleven pages with one: what's fine, what needs a second look and what's never allowed. Let a small group from IT and Legal handle the edge cases. Then sit in the back of someone else's session, and don't rewrite their plan.
5 Steps to Take Action
- 1
Draw the boxes
On a whiteboard, draw how work gets from the old way to the new one. Count the arrows that go through you.
- 2
Turn your best session into a playbook
Record yourself running it, have the AI draft a plain guide, and fix it with a red pen. Now it's a shared skill instead of a slot on your calendar.
- 3
Recruit hosts
Ask respected people in each function to run sessions for their own teams. Give them an hour a week and public credit. Then sit in the back.
- 4
Replace the approval queue with one page
What's fine, what needs a second look, what's never allowed. Approve the common cases in advance. Send edge cases to a small group, never to one person.
- 5
Watch the six-week number
Daily use the week after a session, against six weeks later. If it slides, the drain is open, and more sessions won't close it.
💡 Inspired By
Chapter 6 of The Second Factory, "Everything Runs Through Nora." And Donella Meadows' Thinking in Systems: you can't fill a bathtub by running the tap harder while the drain is wide open.
This is what Analytics Pitfalls & Principles is about: people helping people.
In Practice
Fifty-three days into leading AI for a 900-person company, Nora Berg was running three Bring Your Own Problem sessions a week, three hours each. She had 217 unread emails and nineteen meeting requests for the next week alone. IT's new eleven-page AI guidelines required every workflow to be reviewed before it was shared, and the reviewer was her. Two days later Theo, her best builder, stopped posting his workflows. "I figured I'd wait until somebody approved it." Then the data team showed her a chart. Daily use had climbed for weeks and gone flat. People came out of her sessions at forty, fifty, sixty percent daily use. Six weeks later, many were back under twenty-five. She went up to the catwalk above the data floor and drew it on the whiteboard. Nine hundred people on the left. A company that worked differently on the right. In the middle, one small box with her name in it. Every arrow went through it. It was Elmer's inbox, the one she'd spent weeks helping him clear. She'd been building the same thing around herself.
