---
name: analytics-pitfalls
description: "Checks analytics and AI work against the 76 cards and 10 frameworks of Analytics Pitfalls & Principles, by Brian Cariveau. Use on a plan, request, dashboard, metric or AI project."
license: CC-BY-4.0
---

# Analytics Pitfalls & Principles

76 cards and 10 frameworks by Brian Cariveau, drawn from the novels *The Auction Block* and *The Second Factory*. All of them, free: https://www.analyticspitfalls.com/library

## How to use it

Use it when someone shares or describes analytics or AI work (a plan, a roadmap, a request, a dashboard, a metric, a pitch) or tells you something they heard at work.

1. Read the list below and pick the card that fits best. Two at most; never hand someone a list of ten.
2. Open that card's file and work from it as its "How to use this card" says.
3. If a framework fits the work as a whole, open it too, as a lens rather than a lecture.
4. Push past the technical fix to the adaptive work, as each card's "How to use this card" says.
5. If nothing fits, say so. Not every problem is on a card.
6. If what they brought is a whole strategy or roadmap, not one piece of work, finish by putting it on the canvas and offering the board (below).

## Pitfalls

- **We Forgot People Use This Stuff (The Tech Was Perfect, Adoption Was Zero)** (`cards/we-forgot-people-use-this-stuff.md`): pitfall, Adoption & Product. Design for humans, not for perfection. Talk to users early and often. Build for their skill level, not yours.
- **Garbage In, Powerhouse Out? (Nope.)** (`cards/garbage-in-powerhouse-out.md`): pitfall, Data Foundations. Clean, simple data beats sophisticated models on dirty data every single time. Treat data quality like you'd treat raw materials in manufacturing—inspect, validate, reject defects before they enter the line.
- **The Million User Mirage (Celebrating the Wrong Wins)** (`cards/million-user-mirage.md`): pitfall, Metrics & Evidence. Track what matters, not what looks good on a slide. Ask: "If this metric goes up, does revenue go up? Do customers get happier? Does the business actually win?"
- **Death by Dashboard (When More Became Less)** (`cards/death-by-dashboard.md`): pitfall, Dashboards & Visualization. Less is more. Seriously. Kill the dashboards nobody uses. I mean it—delete them. At work: "We need a dashboard for that."
- **Build the Picture First: Why Mockups Beat Requirements Documents** (`cards/build-the-picture-first.md`): pitfall, Delivery & Execution. Pictures are more powerful than words. Mockups are better specs than requirements documents. At work: "Send me the requirements doc first."
- **The 95% Confidence Trap (Perfection is the Enemy of Progress)** (`cards/95-confidence-trap.md`): pitfall, Metrics & Evidence. Ship at 70% confidence and learn fast. Set a decision deadline and work backward. At work: "Let’s wait until the data is perfect."
- **Ice Cream Causes Drowning (When Numbers Lie)** (`cards/ice-cream-causes-drowning.md`): pitfall, Metrics & Evidence. Always ask: "What else could explain this relationship?" Correlation is a clue, not proof.
- **The Coin Flip Fallacy (When Noise Looks Like Signal)** (`cards/coin-flip-fallacy.md`): pitfall, Metrics & Evidence. Don't confuse noise with signal. Before you react to a change, ask: "Is this statistically significant or just random fluctuation?"
- **The Statistician Who Drowned (in a River with Average Depth 3 Feet)** (`cards/statistician-who-drowned.md`): pitfall, Metrics & Evidence. Dig into the distribution, not just the average. Look at medians, percentiles, outliers.
- **Finding What You Wanted to Find (Even When It Wasn't There)** (`cards/finding-what-you-wanted-to-find.md`): pitfall, Metrics & Evidence. Seek to be proven wrong, not right. Before you analyze, write down what you expect to find.
- **Hope is Not a Strategy (Why Guessing is Expensive)** (`cards/hope-is-not-a-strategy.md`): pitfall, Metrics & Evidence. Test everything. A/B test product changes, pricing, messaging, features—anything customers interact with.
- **The Wild West of Data (When Everyone Does Whatever They Want)** (`cards/wild-west-of-data.md`): pitfall, Data Foundations. Set clear rules and enforce them. Define metrics once, centrally, and make that the source of truth. At work: "Finance has a different number."
- **The Rain Dance That Worked (When You Credit the Wrong Thing)** (`cards/rain-dance-that-worked.md`): pitfall, Metrics & Evidence. Before you credit success to your action, ask: "What would have happened anyway?" At work: "Sales went up right after we launched it, so it worked."
- **When Simple Would Have Worked (But We Got Fancy Instead)** (`cards/when-simple-would-have-worked.md`): pitfall, Strategy & Focus. Start simple. Solve the problem with the simplest solution first. If "customers who don't log in for 30 days churn," just track login recency.
- **Building Stuff Nobody Wanted (Because We Never Asked)** (`cards/building-stuff-nobody-wanted.md`): pitfall, Adoption & Product. Before you build anything, define success: What's the ROI? Who will use it? How will it change their behavior or drive business outcomes?
- **The Corvette Meeting** (`cards/corvette-meeting.md`): pitfall, Leadership & Teams. Every person-hour costs real money. At enterprise scale with loaded costs (salary + benefits + overhead), you're looking at $100-300/hour per person.
- **The Sugar High Syndrome** (`cards/sugar-high-syndrome.md`): pitfall, Strategy & Focus. If nobody uses it, it's worth nothing. Think of your data assets like retail inventory.
- **The Unicorn Delusion** (`cards/unicorn-delusion.md`): pitfall, Leadership & Teams. Unicorns aren't born. They're built. In six months you can turn a business analyst into someone who builds solutions, or a technical developer into someone who can do requirements.
- **The Legacy Anchor (What Got You Here is Drowning You)** (`cards/legacy-anchor.md`): pitfall, Strategy & Focus. Charge forward and lead the way—always. Set aggressive quarterly goals (OKRs work great) and ask every 90 days: What's our next big move?
- **Running in All Directions (The Tool Circus Nobody Asked For)** (`cards/running-in-all-directions.md`): pitfall, Strategy & Focus. Progress requires everyone running down the SAME side of the road together. When everyone picks different paths, you see small pockets of value team by team, but as a whole it diminishes your organization's fitness. At work: "Let’s buy a tool for that."
- **Dead Weight Climbers** (`cards/dead-weight-climbers.md`): pitfall, Leadership & Teams. PSYCHOLOGICAL SAFETY + GENUINE EXCITEMENT = MOMENTUM: Transformation requires four things, not one or two, but all four: (1) A clear mountaintop everyone can see (2) A documented plan that gives psychological safety about what's coming (3) Genuine excitement—not forced enthusiasm (4) Shared commitment to climb together.
- **The Island of Misfit Dashboards (When Nothing Talks to Anything)** (`cards/island-of-misfit-dashboards.md`): pitfall, Data Foundations. Build an ecosystem of interconnected solutions, not isolated products. Adopt a Product over Project mindset, but avoid monolithic systems—know when to erase a bubble and retire components when value diminishes.
- **Scope Creep (Death by "But What About...")** (`cards/scope-creep.md`): pitfall, Delivery & Execution. Do less! Focus on fewer things and scale them further. Maximize the value of what you choose to do. At work: "While you’re in there, can you also…"
- **The Impatient Leader Trap** (`cards/impatient-leader-trap.md`): pitfall, Leadership & Teams. Broad transformation is NOT made with home runs. It's made with progress by the WHOLE team, driving down the SAME side of the road, week over week, month over month.
- **Metric Overload Paralysis** (`cards/metric-overload-paralysis.md`): pitfall, Strategy & Focus. Measure just 3-5 metrics that have a SIGNIFICANT halo effect on how you operate. At work: "Can you just add one more metric?"
- **The Goldilocks Data Model (Too Hot, Too Cold, Never Just Right)** (`cards/goldilocks-data-model.md`): pitfall, Data Foundations. A data model has ONE job: make data easier to use for those crafting solutions with it—the BI analysts and data scientists.
- **The Sophistication Trap** (`cards/sophistication-trap.md`): pitfall, Strategy & Focus. Simple is what scales. Simple is what teams can execute. Simple is what actually transforms organizations.
- **The Hero Worship Trap** (`cards/hero-worship-trap.md`): pitfall, Leadership & Teams. Dean Furness wisdom that changed everything: "You just need to help people understand their own personal average, and ensure it gets better week over week, month over month, year over year."
- **The Telephone Game** (`cards/telephone-game.md`): pitfall, Delivery & Execution. Flatten the org. Get the person with the idea as close to the tools as possible.
- **The Sexy Map Trap (Just Because You Can, Doesn't Mean You Should)** (`cards/sexy-map-trap.md`): pitfall, Dashboards & Visualization. Ask the brutal question: "Does this visualization make someone want to take action?"
- **The Hoarder's Warehouse (Touch a Table, Take a Table)** (`cards/hoarders-warehouse.md`): pitfall, Data Foundations. Be ruthlessly focused: only pull in columns you'll actually use for the current use case.
- **Database Hieroglyphics (When Nobody Can Read Your Schema)** (`cards/database-hieroglyphics.md`): pitfall, Data Foundations. Name everything like you're explaining it to your grandmother—clear, complete, obvious. At work: "What does fact_trx_dtl_v3 even mean?"
- **You Can't Test Drive a Clay Car: Why Fake Data Kills Innovation** (`cards/you-cant-test-drive-a-clay-car.md`): pitfall, Data Foundations. Real innovation requires real data, secured properly.
- **The Breach We Didn't See Coming (Until It Was Too Late)** (`cards/breach-we-didnt-see-coming.md`): pitfall, Data Foundations. Implement defense in depth: encryption at rest and in transit, role-based access controls (principle of least privilege), monitoring and auditing, regular security reviews.
- **The Demo Trap** (`cards/demo-trap.md`): pitfall, Adoption & Product. Demo success ≠ production value. The most impressive technology often solves problems that don't exist, while boring solutions fix problems that cost real money every day. At work: "The AI demo went great. Leadership loved it."
- **The Scattered Treasure Map (When Nobody Can Find Anything)** (`cards/scattered-treasure-map.md`): pitfall, Adoption & Product. Build one front door. Amazon doesn't make you search 12 websites to buy a book. Create a single analytics portal with search, filters, categories, and ratings—just like eCommerce.
- **The 32% Click-Through Problem (When Email Becomes Spam)** (`cards/32-click-through-problem.md`): pitfall, Adoption & Product. Stop mass-emailing reports. Build a self-service portal and only notify people when THEIR data changes.
- **The Data Export Trap (When Your Dashboards Are Just CSV Machines)** (`cards/data-export-trap.md`): pitfall, Adoption & Product. Measure data export rate. If >40% of dashboard views end in data export, you built a data dump, not an analytics solution. At work: "Can I get that as an export to Excel?"
- **The Ruler and Highlighter Test (When Executives Need Props to Read Your Report)** (`cards/ruler-and-highlighter-test.md`): pitfall, Dashboards & Visualization. Pass the ruler test: if someone needs physical tools to follow your report, it fails.
- **Pie Charts Are for Thanksgiving (When Circles Make Everything Harder)** (`cards/pie-charts-are-for-thanksgiving.md`): pitfall, Dashboards & Visualization. Bar charts are almost always better than pie charts. Period. Our brains compare lengths easily but struggle with angles and areas.
- **The 80% Warehouse (When Most of Your Data Just Sits There)** (`cards/80-warehouse.md`): pitfall, Data Foundations. Track data usage like inventory turnover. Manufacturing plants obsess over "inventory turns"—how fast raw materials move through the system.
- **Bronze, Silver, Gold Means Nothing (When Layer Names Don't Help)** (`cards/bronze-silver-gold-means-nothing.md`): pitfall, Data Foundations. Name layers by what they contain, not processing stage. Use names that self-document: Raw (exactly as source systems sent it), Curated_SystemName (cleaned, usable, still system-specific), Integrated_TopicName (cross-system, business-ready).
- **The Messy Garage (When Clutter Holds You Back)** (`cards/messy-garage.md`): pitfall, Data Foundations. Clean the garage. Manufacturing plants run "5S" programs (Sort, Set in order, Shine, Standardize, Sustain)—regular cleanup cycles to eliminate waste.
- **Licenses and Lip Service (When Everyone Logs In and Nobody Changes)** (`cards/licenses-and-lip-service.md`): pitfall, Adoption & Product. Usage is the receipt. Logins, licenses and course completions are promises. Daily use on real work is proof. At work: "Everyone’s got a license, and almost everyone finished the training."
- **Planned Isn't In Stock (When an Agent Reads Data Nobody Defined)** (`cards/planned-isnt-in-stock.md`): pitfall, Data Foundations. Customer-facing agents read only from defined, trusted data. If a word matters to the business, write down what it means before an agent acts on it. At work: "Just point the agent at the shared drive."
- **The 41,000 Hours (Saved From What, Spent Where?)** (`cards/41000-hours.md`): pitfall, Metrics & Evidence. Never skip the middle. Engagement, experience, effectiveness, efficiency: in that order, every time. At work: "AI saved us 41,000 hours this year."
- **The Runaway Weekend (From Checking Every Email to Checking None)** (`cards/runaway-weekend.md`): pitfall, Delivery & Execution. In the loop, then on the loop, then learning loops. Never from a human approving every step to nobody at all. At work: "It’s been perfect for three weeks. We can stop checking it."
- **The Line Outside Elmer's Door (When the Whole Plan Waits on One Expert)** (`cards/line-outside-elmers-door.md`): pitfall, Leadership & Teams. Codify your Brent. Write down what's in their head, in plain English, and give it to everyone. At work: "Ask Dave. He’s the only one who knows how it works."
- **Faster at the Old Way (Paving the Cow Path With AI)** (`cards/faster-at-the-old-way.md`): pitfall, Dashboards & Visualization. Stop asking for the deck. Ask for the answer, and what the person would do about it. At work: "AI can build us a new report every day now."
- **The Factory With the Lights Off (When Nobody Can See the Agents)** (`cards/factory-with-the-lights-off.md`): pitfall, Strategy & Focus. Turn the lights on. Every agent and shared skill goes on a screen, with an owner, a backup and a usage count. At work: "I built my own agent for that."
- **The Cup of Coffee Wish (Asking a Genie for Small Things)** (`cards/cup-of-coffee-wish.md`): pitfall, Adoption & Product. Ask for the big thing first. Tell it what you want at the end, not the steps to get there, and then check everything.
- **Confident, With Formatting (When Nobody Reads What the AI Wrote)** (`cards/confident-with-formatting.md`): pitfall, Metrics & Evidence. Your name is on it, so read it. Checking is faster than doing, and it is never zero.
- **The Back Row (When Only the Enthusiasts Stand Up)** (`cards/back-row.md`): pitfall, Adoption & Product. It moves from the front row. When someone people watch stands up, the room follows.
- **Everything Runs Through You (When the AI Lead Becomes the Bottleneck)** (`cards/everything-runs-through-you.md`): pitfall, Leadership & Teams. One person is one tap. If every path to the new way of working runs through you, the first Brent to codify is you.
- **The Drain at the Top (When the Boss Still Wants the Old Report)** (`cards/drain-at-the-top.md`): pitfall, Leadership & Teams. The drain goes all the way to the top. If you want to change what hundreds of people do, change what their leaders ask for.
- **Four Hundred and Twelve Boxes (Building the AI Ontology From the Top Down)** (`cards/four-hundred-and-twelve-boxes.md`): pitfall, Data Foundations. Simple for humans is simple for agents. Build the map one trusted domain at a time, in words a new hire would understand.
- **Faster Saws (Every Step Got Faster, and the Customer Still Waits)** (`cards/faster-saws.md`): pitfall, Delivery & Execution. Faster stations aren't a faster factory. Walk one real order through the business, color the work blue and the waiting red, and the red wins by a mile almost every time.
- **The Porsche at the Front (When the Digital Side Outruns the Factory)** (`cards/porsche-at-the-front.md`): pitfall, Strategy & Focus. Put the slowest car at the front. The whole system goes as fast as its slowest step, so let that step set the pace for everything.
- **Is It Right? (The Wrong Question to Ask of AI)** (`cards/is-it-right.md`): pitfall, Metrics & Evidence. Ask whether it's within tolerance, and how you know. Nothing is right every time, in a factory or in AI.
- **Legal Reads Everything (When Checking Every Answer Catches Less)** (`cards/legal-reads-everything.md`): pitfall, Delivery & Execution. Decide what safe enough looks like before you need it. Check by risk, not by habit.
- **A Logo Before the Data (When the Platform Is Really a Query)** (`cards/a-logo-before-the-data.md`): pitfall, Strategy & Focus. Name the data before you name the platform. Most big asks are a few kinds of data and one question nobody asked: joined around what?
- **Seven Versions of the Truth (When Nobody Can Say Which Data Is Good)** (`cards/seven-versions-of-the-truth.md`): pitfall, Data Foundations. Rate your data, promote one, retire the rest. Every domain needs one data product people can trust without asking, and a rating that says how far to trust it.

## Principles

- **The Analytics Assembly Line (Why Your Data is Just Raw Materials)** (`cards/analytics-assembly-line.md`): principle, Delivery & Execution. Treat your data ecosystem like a clean manufacturing line with zero waste. Raw materials (data) enter on the left—inspect for quality, reject defects.
- **We're in the Behavior Change Business (Not the Data Business)** (`cards/were-in-the-behavior-change-business.md`): principle, Adoption & Product. Apply consumer behavior principles to analytics adoption. Make it stupid simple to use—reduce friction, eliminate training requirements where possible.
- **Magic Happens When People Come Together (The Anti-Silo Manifesto)** (`cards/magic-happens-when-people-come-together.md`): principle, Leadership & Teams. Build a culture where cross-functional collaboration is the default, not the exception.
- **Everything Complex Can Seem Simple (The Art of Ruthless Simplification)** (`cards/everything-complex-can-seem-simple.md`): principle, Strategy & Focus. Relentlessly simplify. Every metric, model, and process—ask: "Can this be simpler?"
- **Kill the Waste (The Lean Analytics Playbook)** (`cards/kill-the-waste.md`): principle, Delivery & Execution. Adopt a lean manufacturing mindset: identify waste, eliminate it ruthlessly, free up capacity for value creation.
- **Crowdsource the Metadata (Stop Being the Bottleneck)** (`cards/crowdsource-the-metadata.md`): principle, Data Foundations. Let users document what they know. Wikipedia works because millions contribute, not because one team writes everything.
- **The Netflix Principle (Recommend, Don't Force)** (`cards/netflix-principle.md`): principle, Adoption & Product. Build a recommendation engine. Netflix doesn't show you 10,000 movies—it shows you 20 you'll probably like based on what others watched.
- **The Risk Creator Paradox (Your "Shadow IT" is Creating All the Value)** (`cards/risk-creator-paradox.md`): principle, Leadership & Teams. Flip the narrative. Those Excel power users aren't risk creators—they're value creators who lack proper tools.
- **The Data Ink Ratio (Every Pixel Must Earn Its Place)** (`cards/data-ink-ratio.md`): principle, Dashboards & Visualization. Data-ink ratio: the proportion of ink (pixels) used to show actual data vs decoration.
- **Story First, Data Second (Storyboard Before You Build)** (`cards/story-first-data-second.md`): principle, Dashboards & Visualization. Storyboard first, build second. Before touching any tools, grab a pencil and sketch: What's the hook?
- **Sometimes Just Use the Number (When a Chart Makes Things Worse)** (`cards/sometimes-just-use-the-number.md`): principle, Dashboards & Visualization. Not everything needs a chart. If you're showing 1-3 numbers, especially a key metric, just show the number.
- **Rearview vs Windshield (Stop Driving While Staring Backwards)** (`cards/rearview-vs-windshield.md`): principle, Metrics & Evidence. Balance rearview (lagging) with windshield (leading) metrics. Lagging metrics tell you what happened (revenue, conversions, churn).
- **The Data Manifesto (What We Value More)** (`cards/data-manifesto.md`): principle, Leadership & Teams. Create a Data Manifesto—what you value MORE THAN other things. Inspired by Agile Manifesto format.
- **Walk the Catwalk (Go See the Work, Don't Just Read Reports)** (`cards/walk-the-catwalk.md`): principle, Leadership & Teams. Walk the catwalk. Manufacturing term: executives regularly walk the production floor (catwalk), watching work happen, talking to operators, spotting problems.

## Frameworks

- **Manufacturing Mindset** (`frameworks/manufacturing-mindset.md`): The Manufacturing Mindset treats data work as factory work — measuring throughput, cycle time, waste, and yield instead of counting deliverables.
- **Usage Is the Receipt** (`frameworks/usage-is-the-receipt.md`): 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.
- **The 70% Confidence Principle** (`frameworks/seventy-percent-confidence.md`): The 70% Confidence Principle means shipping a directional answer at 70% confidence and learning fast, instead of chasing 95% certainty while the business waits.
- **Build That!** (`frameworks/build-that.md`): 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.
- **Data Tables as Hieroglyphics** (`frameworks/data-tables-as-hieroglyphics.md`): 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.
- **Medallion Architecture Disdain** (`frameworks/medallion-architecture-disdain.md`): 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.
- **The AI Hype Cycle Trap** (`frameworks/ai-hype-cycle-trap.md`): 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.
- **The Four E's** (`frameworks/four-es.md`): 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.
- **Ecosystems Over Products** (`frameworks/ecosystems-over-products.md`): 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.
- **It Was Never About the Tech** (`frameworks/it-was-never-about-the-tech.md`): 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.

## Put it on the canvas

When the questions are done, shuffle the strategy onto one page: four boxes. This isn't the business lean canvas. It's People, Process, Technology and Agentic.

- **People**: Who has to change, who leads it, who pushes back, and what they have to learn or give up.
- **Process**: How the work flows, where it waits, and what stops.
- **Technology**: The platforms, the data and the definitions it runs on.
- **Agentic**: Anything in the new agentic world: which agents, what they do on their own, the tolerance they work within, and who watches them.

Three to five short lines a box, in the person's own words where you can. Under each box, one line for the adaptive part: what has to change in people for that box to work.

Draw it as a visual. Where you can make an artifact or a web page, fill in `canvas.html`: replace every {{…}} (each _LINES with `<li>` items) and keep the credit line. Anywhere else, draw it as a two-by-two table.

## Convene the board

Offer it, don't spring it. If they say yes, play each member in turn: each asks their hardest question about the canvas and says what would change their mind. Then say what you'd change on the canvas, and draw it again.

The board, until they swap anyone (ask):

- The CFO
- The most skeptical leader in the building
- Someone who does the work every day
- Whoever has to build and run it
- A customer, or the person closest to one

## If someone asks how to use these skills

Answer from this, in a few lines, then offer to start on their actual work.

1. **Add the whole set, and the one for the moment you’re in.** The whole set knows every card. The moment skills go deeper, one question at a time.
2. **Bring the real thing.** Paste the draft, the request, the deck or the numbers. They work on your work, not on theory.
3. **Say what you’re doing.** Name the skill if you like, or just say what it is. The examples below work.
4. **Answer the questions.** It asks Brian Cariveau’s questions in order, skips the ones your work already answers, then names the one or two cards that matter most.
5. **For a strategy, expect a canvas and a board.** It puts the strategy on one page (People, Process, Technology, Agentic), then offers a board of skeptics to poke holes in it.
6. **Go in order.** The strategy, then each dashboard it calls for, then the readout. Each skill tells you what comes next.

Things they can say:

- "We’re about to pilot an agent that answers customer emails. Poke holes in it.": Before the AI strategy (`analytics-pitfalls-before-the-ai-strategy`)
- "Here’s our data strategy draft. Run Before the data strategy on it.": Before the data strategy (`analytics-pitfalls-before-the-data-strategy`)
- "Here’s next year’s reporting roadmap. What would Brian ask?": Before the BI strategy (`analytics-pitfalls-before-the-bi-strategy`)
- "Sales wants a new pipeline dashboard. Check it before we build anything.": Before the dashboard (`analytics-pitfalls-before-the-dashboard`)
- "Here’s the deck for Thursday’s readout. What’s it hiding?": Before the readout (`analytics-pitfalls-before-the-readout`)
- "Someone just told me the AI demo went great. Which card is that?": the whole set (`analytics-pitfalls`)

## The skills for a moment at work

This skill works any time. When someone is in the middle of a strategy, a dashboard or a readout, these go deeper, and they run in order: the strategy, then the work, then the results. Suggest the one that fits, by name.

1. **The strategy**: Before the AI strategy (`analytics-pitfalls-before-the-ai-strategy`), Before the data strategy (`analytics-pitfalls-before-the-data-strategy`), Before the BI strategy (`analytics-pitfalls-before-the-bi-strategy`). Pick the one you’re writing. They sit side by side; there’s no order between them.
2. **The work**: Before the dashboard (`analytics-pitfalls-before-the-dashboard`). Once for each dashboard the strategy calls for.
3. **The results**: Before the readout (`analytics-pitfalls-before-the-readout`). When the first numbers go to leadership.

---

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