Coming next: The Second Factory →

Back to Library
Data Foundations⚠️ Pitfall

The Messy Garage (When Clutter Holds You Back)

The Problem

Your data platform looks like a messy garage. Expired ETL jobs from 2019 still running—like tools you haven't touched in years. Datasets nobody remembers building, piled like boxes labeled "misc stuff." Duplicate tables with names like "customer_v2," "customer_final," "customer_FINAL2"—like having three sets of wrenches because you can't find the first two. Dashboard folders 12 levels deep. Every time you need something, you have to search through the clutter. New projects take forever because you can't find existing work—easier to just rebuild it. Team morale tanks because navigating the mess is exhausting. It's like trying to fix a car in a garage where half the tools are broken, everything's buried under junk, and you spend more time searching than working. The clutter isn't just messy—it's slowing down everything you do.

The Principle

Clean the garage. Manufacturing plants run "5S" programs (Sort, Set in order, Shine, Standardize, Sustain)—regular cleanup cycles to eliminate waste. Apply same to your data platform. Monthly cleanup ritual: archive unused jobs, delete duplicate tables, consolidate redundant dashboards, organize folders logically. Create "days since last use" metric for everything: data, jobs, dashboards, code. If it's been >90 days without use, archive it. If someone needs it later, unarchive it. The magic happens when your platform is so clean that finding what you need takes seconds, not hours. Every team member can find existing work before building new. Think classic car restoration: you can't work on the Mustang if you can't even get into the garage. Clutter elimination = velocity increase.

🎯

3 Steps to Take Action

  1. 1

    **Inventory the Mess** Create "clutter report": - ETL jobs: how many? Days since last run? - Tables/datasets: how many? Days since last query? - Dashboards/reports: how many? Days since last view? - Code repos: how many? Days since last commit? - Folders: how deep is nesting? How many empty? Calculate "clutter score": Sum of (items × days unused) Higher score = more clutter = more drag on team velocity.

  2. 2

    **Monthly Garage Cleaning Ritual** Last Friday of every month: 2-hour team cleanup session. Agenda: 1. Review "unused in 90+ days" list (15 min) 2. Archive or delete unused items (45 min) 3. Rename confusing things (30 min) 4. Reorganize folders (30 min) Rules: - If nobody remembers what it does, archive it - If it's a duplicate, delete the worse version - If name is confusing, rename it - If folder is >3 levels deep, flatten it Celebrate: Track items archived/deleted each session. Aim for 10%+ reduction monthly until steady state.

  3. 3

    **Prevent Future Clutter** Create "clean as you go" standards: - New items must have clear names and descriptions - Duplicate work requires justification - Items unused for 90 days auto-flagged for review - Folder depth limit: 3 levels max - Code repos require README with purpose Quarterly "deep clean": Bigger cleanup session, 4 hours. Goal: Platform stays so clean that new hires can navigate it independently within 1 week. Bonus: Tie promotions to "left platform cleaner than you found it."

💡 Inspired By

Manufacturing 5S principles (Sort, Set in order, Shine, Standardize, Sustain). Classic car garage metaphor aligns with fable's automotive theme (Sarah's 1981 Porsche 911, Ben's Mustang).

This is what Analytics Pitfalls & Principles is about: people helping people.

In Practice

A major bank's analytics team had 2,300+ ETL jobs. Nobody knew what half of them did. Dashboards in folders so nested that finding anything took 20 minutes. New projects always started from scratch because finding existing work was harder than rebuilding. They implemented monthly "garage cleaning": Last Friday of every month, 2-hour team session. Review "unused in 90+ days" list. Archive anything nobody needed. Delete duplicates. Rename confusing things. Reorganize folders. First session: archived 420 ETL jobs (18%), deleted 180 duplicate dashboards, flattened folder structure from 12 levels to 3. Developer experience transformed: "I can finally find things!" Time to find reusable work dropped from 45 minutes to 5 minutes. New project velocity up 30% because teams reused existing work instead of rebuilding. The garage cleaning became cultural ritual: "Clean platform = fast team."

More on Data Foundations

From the book

In the book, a new hire takes six months to become useful, mostly because of table names nobody can read. And there are five definitions of an active seller.

This card is one of 57 drawn from The Auction Block by Brian Cariveau — the story of an analytics leader with 90 days to fix what the cards describe.

Each leadership pattern falls into a few pitfalls most often. Find your pattern.The Analytics Leadership Mirror: free, 5 minutes, no account