---
name: analytics-pitfalls-everything-runs-through-you
description: "\"Everything Runs Through You\": a pitfall card from Analytics Pitfalls & Principles. Use when a plan, request, dashboard, metric or AI project might be falling into it."
license: CC-BY-4.0
---

# Everything Runs Through You (When the AI Lead Becomes the Bottleneck)

A pitfall card from Analytics Pitfalls & Principles, drawn from *The Second Factory*, Brian Cariveau's next novel (https://www.analyticspitfalls.com/second-factory).
https://www.analyticspitfalls.com/cards/77

## How to use this card

Use it when what someone is working on, or something they heard at work, looks like the problem below: a plan, a roadmap, a request, a dashboard, a metric, an AI project.

1. Name the card by its title and say in a sentence why it fits. Say the work looks like this pitfall; never tell someone they have it.
2. Give the principle in the card's own words. Don't rewrite it.
3. Take the steps one at a time against their actual situation: what is already done, what isn't, and which to do first. If you need a fact to do that, ask one question, not five.
4. Then push past the technical fix, if the work needs people to work differently (most does). The steps are the if-then part. Ask what has to change in how people work, what they have to learn or believe, or what they give up, for it to stick. That's the adaptive work (Ronald Heifetz's term), and it's usually the real work.
5. If the card doesn't fit, say so plainly. Don't stretch it.
6. Finish with the card's link: https://www.analyticspitfalls.com/cards/77

## 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.

## The steps

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.

## 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.

---

© 2026 Brian Cariveau, Analytics Pitfalls & Principles. Free to share and adapt under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/): keep this credit, "Brian Cariveau, Analytics Pitfalls & Principles (https://www.analyticspitfalls.com)", and say if you changed it.
The names Analytics Pitfalls & Principles, The Auction Block and The Second Factory are not part of the license. Don't use them for your own version, or to suggest it comes from us.
