Free to read · No account

The Library

Everything from The Auction Block you can use on Monday morning. Find the pitfall you are standing in, read the principle that answers it, and take the first step.

Pitfalls & principles

57 cards, all free

Each card names a pitfall or a principle, shows it in practice, and gives you steps to take on Monday morning.

Type
Data Foundations

Garbage In, Powerhouse Out? (Nope.)

You spent $2M building a state-of-the-art ML platform. Hired a team of PhDs. Bought the fanciest tools. Launch day comes, predictions are wildly off. Turns out your customer data has 40% duplicates, purchase dates are wrong half the time, and nobody has cleaned the source systems in 5 years. Garbage in, garbage out. Except now it's expensive garbage with a PhD babysitting it. It's like building a Ferrari and filling it with contaminated fuel—doesn't matter how good the engine is if the inputs are trash. Data quality is the foundation. Skip it and everything built on top is a house of cards. Yet teams constantly underinvest here because it's not sexy. Cleaning data doesn't win awards. But it's what separates powerhouses from pretenders.

⚠️ PitfallRead more →
Metrics & Evidence

The Million User Mirage (Celebrating the Wrong Wins)

Board meeting. "We hit 1 million users!" Champagne pops. Everyone celebrates. Three months later you're laying off half the team because revenue is in the toilet. Turns out 97% of those "users" signed up, looked around for 30 seconds, and never came back. You were measuring signups when you should've been measuring engagement. Revenue. Retention. The stuff that actually pays the bills. Or your data team celebrates "We built 47 dashboards this year!" Leadership claps. Until someone asks: "How many have 5+ weekly active users?" Silence. Turns out 28 of those 47 dashboards have 2 or fewer users. Some have zero. It's like a manufacturing plant celebrating "we made 1 million widgets!" while ignoring that 970,000 are sitting unsold in a warehouse. Vanity metrics feel good but they're a trap—they let you lie to yourself about success while the business bleeds out.

⚠️ PitfallRead more →
Delivery & Execution

Build the Picture First: Why Mockups Beat Requirements Documents

Your team wants to build an AI solution. Or a new dashboard. Or a data product. So they do what teams always do: Jump straight to the data. "What tables do we need?" "Where does this data live?" "How do we join these sources?" If requirements get written at all, they look like this: "The user shall be able to filter by date range, product category, and region. The system shall display aggregated metrics with drill-down capability. Performance shall be sub-2-second response time." Verbose. IT-centric. Not particularly useful. Six months later, you build exactly what the requirements specified. You demo it. The response? "Yeah... this isn't really what we needed." Because nobody could see it. They couldn't picture it. They approved words on a page, not a solution to their problem. You built what was asked for, not what was needed.

⚠️ PitfallRead more →
Metrics & Evidence

Finding What You Wanted to Find (Even When It Wasn't There)

CEO wants to prove the new pricing strategy is working. Asks analytics for a report. Analyst finds data showing revenue is up in two regions—ignores the three regions where it's flat or down. Presents the good news. CEO is thrilled. Strategy continues. Six months later, overall revenue is down 8%. What happened? Confirmation bias. We see what we want to see. We cherry-pick data that supports our hypothesis and ignore data that doesn't. It's human nature. But it's deadly in analytics. You end up making decisions based on a partial, distorted view of reality. It's like a factory manager only checking the machines that are working and ignoring the broken ones. Eventually, production grinds to a halt.

⚠️ PitfallRead more →

Ten named frameworks

The vocabulary from the book, defined

Each framework gets a one-sentence definition, the real story behind it, and what to do about it Monday morning.

1Adaptive

Manufacturing Mindset

The Manufacturing Mindset treats data work as factory work — measuring throughput, cycle time, waste, and yield instead of counting deliverables.

2Technical

Usage Is the Receipt

Usage Is the Receipt means the only proof an analytics product worked is whether people actually use it — adoption is the receipt, everything else is a claim.

3Technical

The 70% Confidence Principle

The 70% Confidence Principle means shipping a directional answer at 70% confidence and learning fast, instead of chasing 95% certainty while the business waits.

4Adaptive

Build That!

Build That! means validating ideas with a mockup people can react to before writing requirements — the picture is the spec, not a document nobody can quite picture.

5Technical

Data Tables as Hieroglyphics

Data Tables as Hieroglyphics is the argument that cryptic schema names like fact_trx_dtl_v3 are gatekeeping dressed up as rigor, not a technical necessity.

6Technical

Medallion Architecture Disdain

Medallion Architecture Disdain argues that Bronze/Silver/Gold layer naming describes processing stage, not content — call it the Paint Department instead, a name that tells you what happens there.

7Technical

The AI Hype Cycle Trap

The AI Hype Cycle Trap is building the impressive AI demo instead of the boring, high-value fix — because demo success and production value are not the same thing, and the gap between them is where budgets go to die.

8Adaptive

The Four E's

The Four E's — Engagement, Experience, Effectiveness, Efficiency — describe the order analytics maturity actually moves through, and the order is non-negotiable: chase efficiency before anyone is engaged and you optimize something nobody uses.

9Technical

Ecosystems Over Products

Ecosystems Over Products means building an interconnected system of analytics assets that reference and reinforce each other, instead of a pile of isolated dashboards and models that each stand alone.

10Adaptive

It Was Never About the Tech

It Was Never About the Tech is the observation that analytics transformations fail on politics, people, and principles far more often than on tooling — the technology is rarely the binding constraint.

📊 5-minute assessment

Where do you stand as an analytics leader?

20 questions. 6 dimensions. Get a personalized profile of your analytics leadership — mapped to the pitfalls and principles from The Auction Block.

Take the Assessment →

📖 Chapter 1 Preview

The Dashboard That Broke Everything

Read the opening chapter of The Auction Block — free.

Sarah Chen stared at the email for the third time, willing the words to rearrange themselves into something that made sense. They didn’t. The subject line read: “Dashboard Audit Results — URGENT” and beneath it, a number that made her stomach drop.

Forty-seven.

Forty-seven active dashboards across the analytics organization she’d inherited three weeks ago. She’d expected a mess — the job description had practically screamed “fixer needed” — but forty-seven dashboards for a company with eight product lines was a special kind of chaos.

Continue reading in the book...

📝 Essay Preview

The Manufacturing Mindset

From Part 2 of The Auction Block — the leadership essays.

I was standing on a factory catwalk in Minneapolis, watching a production line that had been running for decades, when it hit me: everything I was trying to fix in analytics had already been solved — just in a different building.

The factory floor below me was a masterpiece of systems thinking. Raw materials entered on one end. Finished products came out the other. Every step was visible, measurable, and improvable. Bottlenecks had names. Waste had categories. And the people doing the work could actually see the whole system, not just their piece of it.

Then I walked back to my office and looked at our analytics org. Same company. Same building, even. But a completely different universe. Work entered from every direction — Slack messages, emails, hallway conversations, executive texts. Nobody could see the full queue. Nobody knew what was actually in progress versus stuck. And the “finished products” — our dashboards, analyses, and models — often disappeared into the void with no feedback on whether they actually helped anyone make a better decision.

The full essay continues in the book...

New pitfalls and principles, as they publish

Occasional notes on analytics leadership — new frameworks, new cards, and the stories behind them. Written by Brian, not a marketing team.

No spam. Unsubscribe anytime.

Ready for the full experience?

The book includes 15 chapters, 4 leadership essays, and the principles behind every card. Available on Kindle, in paperback and in hardcover.

Get The Auction Block on Amazon →

Kindle $9.99 · Paperback $17.99 · Hardcover $24.99