---
name: analytics-pitfalls-line-outside-elmers-door
description: "\"The Line Outside Elmer's Door\": 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
---

# The Line Outside Elmer's Door (When the Whole Plan Waits on One Expert)

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/71

## 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/71

## What it sounds like at work

"Ask Dave. He’s the only one who knows how it works."

## The problem

The roadmap is green and yellow except for one red line stretching almost the full width of the screen. Eighteen months. Everyone assumes it's a technology problem.

Then you watch for an afternoon. Every question in that part of the business routes through one person. Does this fit? Which year? Is this right? Three hundred unread messages, half of them the same question as last week from someone else. He answers maybe twenty a day. And if he got hit by a bus tomorrow, all of it would go with him.

The red line on the roadmap is the length of the line outside his door.

## The principle

Codify your Brent. Write down what's in their head, in plain English, and give it to everyone.

Every company has a Brent, the engineer in The Phoenix Project who is the only one who knows how anything works. He isn't the villain. He's the most valuable person in the building and the reason everything is stuck. AI makes it practical to fix that, for the first time, without six months of documentation nobody finishes.

Let the expert talk while the AI listens like an apprentice and asks questions. Turn what they say into rules. Then hand the expert the red pen and make them the owner. The point is to stop them answering the same question five times a day, so they can answer the ones nobody else on earth can.

## The steps

1. **Find your Elmers.** Where does work pile up waiting on one person? Look at whose inbox the whole team routes through, and whose absence would stop a project.
2. **Let them talk.** Two or three hour-long sessions. The AI asks questions like an apprentice. No typing required.
3. **Turn it into rules, then hand over the red pen.** Plain-English rules, with anything uncertain flagged "ask the expert." The expert reviews every line and owns every change.
4. **Share it as one skill.** One shared set of instructions everyone uses, so the answer is the same no matter who asks.
5. **Ask what they'd rather spend their time on.** Being the one who knows is part of who they are. Help them get to the questions only they can answer.

## In practice

ClassicMotors was building a parts business: reproductions of classic car parts that no longer exist. Everything on the plan could be sped up except one line. Catalog and fitment, which part fits which car, which years, which trim: eighteen months.

The fitment data lived in Elmer Novak. Sixty-eight, reading glasses on a cord, thirty-one years behind the counter of his own parts shop in Fresno. "The '66 coupe and the fastback use different hinge pins," he told a caller. "Every catalog on earth says they're the same. They're not." His inbox had 340 unread messages, almost all from his own team.

He hated typing. So Nora Berg set a laptop on his workbench, turned on the microphone and told the AI it was his apprentice: listen, ask follow-up questions, never assume. Elmer started calling it Kid. He talked for almost thirty hours in two weeks, and the AI turned it into rules. When Nora printed the first sixty-two pages, he read every one with a red pen. On page nineteen he wrote, in capitals, NO. THAT IS THE CANADIAN CAR.

"If this thing's going to have my name on it," he said, "it had better be right. I want to see every change."

---

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