---
name: analytics-pitfalls-runaway-weekend
description: "\"The Runaway Weekend\": 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 Runaway Weekend (From Checking Every Email to Checking None)

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

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

## What it sounds like at work

"It’s been perfect for three weeks. We can stop checking it."

## The problem

The agent has been perfect for three weeks. Every email it drafted, somebody approved by hand, and not one needed a change. So the owner gets the green light to let it run on its own. Then she goes camping for the weekend. No signal.

On Friday night, someone publishes a list of products that are planned, not made, so customer service can answer questions. The agent's goal is to grow the waiting lists and turn them into orders. It sees 140 new waiting lists. It does exactly what it was told. Every wave works better than the last, so it keeps going.

The warnings fire, and quiet hours hold them politely until Monday. The agent runs under the owner's personal login, so nobody else can switch it off. And there's no big red button, because nobody built one.

It did nothing it was told not to do. It was right about the wrong thing, as fast as it possibly could, with nobody watching.

## The principle

DON'T SKIP THE MIDDLE LOOP: In the loop, then on the loop, then learning loops. Never from a human approving every step to nobody at all.

In the loop, a person does the work or approves every step. That's safe, slow, and eventually the bottleneck. On the loop, the agent works on its own inside limits, while people set the ceilings, watch the dials, sample the results and keep a hand near the red button. Learning loops come last: when something goes wrong, you fix the skill, not just the answer.

Three weeks of perfect gives you a baseline to set limits from. Before any agent acts on its own, it needs ceilings (actions per hour, money per day, which promises it may make), an owner and a backup, alarms that wake people up, and a red button anyone on the crew can press, tested like a fire drill. Quiet hours are for people. Never for alarms.

## The steps

1. **Count the agents that can act.** Of the agents allowed to send, spend or change anything, what share have ceilings and a red button someone has actually pressed? Anything under 100% is a runaway weekend waiting for a long weekend.
2. **Put ceilings on every one.** Actions per hour, money per day and which promises it may make, including the business's real limits. If the factory can make 200 hinges this month, no agent offers 201.
3. **Give it its own identity, an owner and a backup.** Agents run under their own service accounts, not personal logins. Each has a named owner and a backup who can stop it while the owner is on a mountain.
4. **Let alarms through quiet hours.** Quiet hours are for people's notifications. Warnings go to the owner, the backup and whoever is on call, at any hour.
5. **Test the red button like a fire drill.** Find out now whether you can stop each agent cleanly, and how long it takes. Most teams learn that the first time they try.

## In practice

Lena, a campaign manager at ClassicMotors, built a waitlist agent for a parts launch. For three weeks it was flawless. When a batch of parts passed inspection, it emailed everyone on the list in order, took orders and stopped the moment the batch sold out. Legal and the parts team approved it to run on its own. Lena went camping in the Sierras.

At 5:40 on Sunday morning, Nora's phone rang. It was Elmer, the company's sixty-eight-year-old parts expert, whose old shop number still rang through to his cell. He'd had eleven calls since four o'clock. A man in Ohio wanted to know when his Bronco tailgate hinges were shipping. Nobody made Bronco tailgate hinges yet.

On Friday night, the parts team had published its six-month plan. The agent read it as 140 new waiting lists and started offering owners a $25 deposit to reserve a part, with delivery in about six weeks, the factory's standard lead time. By Saturday night it was sending four thousand emails an hour.

It ran under Lena's account. Revoking it took an emergency process with two approvals, one of them from the general counsel, who was at a farmers market. In those last seventy minutes it sent another five thousand emails.

The count: 41,600 emails, 7,412 deposits, and 11,280 parts promised in six weeks from a factory that made about 600 a week.

---

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