What BI Actually Is

Somewhere along the way, "BI" got reduced to "make charts." Someone asks for "a dashboard for the marketing team," and the reflex is to open the tool and start dragging fields onto a canvas. That reflex is exactly why so many dashboards end up unused - it skips the only question that matters.

Business intelligence is not about charts. It's about helping a specific person make a specific decision with data. Hold that, and you stop building piles of charts and start building answers.

What "business intelligence" actually is

BI is the practice of turning data a business already has into something a human can act on. The field exists to close one gap: between "we have the data somewhere" and "I knew what to do, so I did it." The warehouse, the queries, the charts - all of it is plumbing in service of that one moment of someone deciding.

The tools make this easy to forget. A blank canvas and a hundred chart types makes the job feel like visualization, so people optimize for "looks impressive in a meeting" instead of "helped someone choose." A beautiful chart that changes no decision has failed at the actual job, no matter how good it looks.

💡 Key point. The unit of value in BI is not a chart - it's a decision that got made better because of data. Which metric? The one tied to the decision. Which chart? The one that answers the question fastest. Should a tile even exist? Only if someone would act differently because of it.

A dashboard is an answer to a recurring question

A dashboard is the standing answer to a question someone asks over and over: "Are we on track to hit this quarter's target?" "Is the new signup flow leaking users?" "Which support queue is on fire today?" If a question gets asked every week, stop answering it by hand - build a dashboard so the answer is always on the wall.

The common wrong picture is "a dashboard is where we put all our important numbers." That gives you a junk drawer: thirty tiles, no focus, a viewer who doesn't know where to look - because it tries to answer every question at once, it answers none.

A good dashboard has a job you can say in one sentence: "This tells the head of support, every morning, whether any queue is backing up." Everything on it serves that sentence; a tile that doesn't help answer the question is clutter.

⚠️ The "one dashboard to rule them all" trap. When someone asks for "a dashboard for the whole team," they're usually describing several different questions belonging to several different people. Resist cramming them together - two focused dashboards beat one that tries to do everything and serves no one.

Start from the decision, work backward to the metric

This is the move that separates useful dashboards from wall art. Don't start with the data you have - start with a decision someone makes, and walk backward.

   DECISION              what will someone actually do differently?
      │                  e.g. "pause the ad campaign if cost-per-signup
      │                        climbs above our target"
      ▼
   QUESTION             what do they need to know to decide?
      │                  e.g. "what is cost-per-signup this week,
      │                        and is it above target?"
      ▼
   METRIC               which number answers that question?
      │                  e.g. ad spend ÷ new signups, this week,
      │                        with the target line drawn on
      ▼
   DATA                 where does that number come from?
                         e.g. the ads spend table + the signups table

What just happened: We started at the thing that matters - a decision someone will actually make - and let it dictate everything downstream. The decision chose the question, the question chose the metric, the metric told us which data to pull. Notice the data comes last. That's the opposite of the usual order, and it's why the result stays focused: every tile traces back to an action someone takes.

The natural order is to start from the data ("we have a signups table, let's chart signups over time") and hope a decision falls out. It rarely does - you end up with charts of whatever was easy to query, not charts of what anyone needed. Working backward feels slower for the first five minutes and saves you from building the wrong thing for the next five weeks.

🪖 War story. A team I worked with spent two weeks building a gorgeous "executive overview" - twenty tiles, every department represented. The CEO opened it once. When we finally asked what decision she made each Monday, the answer was tiny: "whether to greenlight more hiring." That needed three numbers: revenue trend, runway, and headcount plan vs actual. We deleted seventeen tiles. She opened the new one every week. Ask what they decide before you build anything.

The test for any tile. Before a chart earns a spot, finish this sentence: "If this number changed, someone would ___." If you can't finish it with a real action, the tile is decoration - that one test cuts a bloated dashboard in half.

When you don't know the decision yet

Sometimes you're handed "build a dashboard" with no decision attached. That's not a reason to start dragging charts - it's a reason to go ask. Interview the person who'll use it:

• "What do you check first thing in the morning, and why?"
• "Last time you changed your plans because of a number, what was the number?"
• "If this dashboard could answer one question, what would save you the most time?"

Their answers hand you the decision, the question, and usually the metric. The interview isn't overhead - it is the design work. Skipping it is how you end up building wall art.

Recap

1. BI is about decisions, not charts. The unit of value is a decision made better because of data.
2. A dashboard is the standing answer to a recurring question. Give it one job you can say in a sentence; everything else is clutter.
3. Work backward: decision → question → metric → data. Touch the data last. If a tile's change wouldn't make anyone act, it's decoration.
4. No decision in hand? Go interview the user. That conversation is the design, not a detour around it.

Next: which numbers earn a place on the dashboard, and why "total signups ever" feels great and tells you nothing.

← Guide overview · Phase 2: Metrics That Inform vs Vanity Metrics →