---
name: analytics-pitfalls-41000-hours
description: "\"The 41,000 Hours\" (Saved From What, Spent Where?): 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 41,000 Hours (Saved From What, Spent Where?)

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

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

## What it sounds like at work

"AI saved us 41,000 hours this year."

## The problem

Finance surveyed everyone. How many hours a week does AI save you? They multiplied it out, and now the board slide says it in very large type: 41,000 hours saved.

Ask one person where their four hours went last week. There's a long pause, and the pause is the answer. Nothing in anyone's week was designed to catch the time, so the next thing swallowed it.

Meanwhile, something happened that no survey asked about. AI took the easy work first: the clean case, the routine email, the five-minute task that used to sit between two hard ones. Every team is finishing more than ever. And by four o'clock everyone's fried, because an eight-hour day is now eight hours of hard.

## The principle

Never skip the middle. Engagement, experience, effectiveness, efficiency: in that order, every time.

Most AI programs measure engagement because it's easy, then leap to efficiency because that's what the board wants. Are people using it? Is it a good experience for them? Is it actually working? Only when all three are true does the hours-saved number mean anything.

Pair every efficiency number with its counterbalance. Hours saved, next to where they went. Heavy use, next to good use, because some of your heaviest users are agents stuck in a loop. Output, next to the share of AI use that happens after eight at night. And treat tokens like clicks: they tell you how much behavior there was, not whether it was any good.

## The steps

1. **Run the four-hour test.** In your next team meeting, ask: roughly how many hours did AI save you last week? Where exactly did they go? Then the question that matters: next week, where do you want them to go? Do it on yourself first.
2. **Build the four-row dashboard.** One row per E, in order, top to bottom, each with one measure and its counterbalance. If a row is empty, leave it empty and visible. An empty row on a board slide gets filled faster than a missing one.
3. **Pull the after-hours share.** The share of AI use after eight at night, by team, and whether it's rising. It's the experience number that shows up before the resignation letters do.
4. **Give some easy work back.** On one team, with HR in the room, send one easy case in five or six back to a person. Throughput dips first, and errors and burnout take longer to move, so don't call it after a week.

## In practice

ClassicMotors' CEO had his next board slide ready. Two numbers, very large: hours saved, 41,000; cycle time, down 32%. Finance had surveyed everyone and multiplied it out.

A few days earlier, Rita, who runs seller verification, had stopped Nora by the coffee machine. "I'm getting more done than I ever have in my life. My team is too. So why am I more tired than I've ever been?"

Nora sat with Rita's team for an afternoon. The agents now handled almost all the easy cases, so every case left on a human's desk was an estate sale or a lien dispute. "We used to do an estate, then a few easy ones, then another estate," Rita said. "The easy ones were where you caught your breath."

At her next session, Nora asked the room how many hours AI had saved them last week. Three, five, six. Then she asked where those hours went. Nobody answered. Finally a woman from Operations said, "I think I just did more stuff."

Then Nora asked the data team when people were using it. Fourteen percent of all AI use happened after eight at night. Near the top of the list was her own name.

---

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