How this track works
Six sessions, thinking-mode, zero code. You will never write a query in this track - you will learn to ask better questions of the people and dashboards that do. A sibling builder track (b1-b10) exists for your analysts and engineers; the two tracks share the same Daybreak warehouse, so when your team says "the semantic layer" you will know exactly what they built. Each session is 45 minutes: concepts live, self-study cards for later, and one or two moments where you touch real data yourself.
Where the six sessions go:
- a1 (tonight) - what BI is, what it is not, and how to read a chart
- a2 - reading a whole dashboard: anatomy plus a five-question interrogation
- a3 - one number, one truth: why teams report different revenues and how to end it
- a4 - commissioning dashboards that actually get used
- a5 - self-service without chaos: letting everyone explore without forking the truth
- a6 - the tool landscape and what AI changes (and does not)
What BI actually is 9 min live
Strip away the vendor logos and business intelligence is one promise: the questions your team asks every week get answered automatically, from agreed definitions, for people who never write a query. Here is the test that never fails - the 9am test. If a question is recurring, standardized, and asked by non-technical people, it is BI. If it is a one-off "wait, why did that happen?", it is not, and forcing it into a dashboard wastes everyone's time.
LiveBI vs analytics vs data science - who answers what4 min▶
These three get blurred in every org chart and every budget line, but the split is clean when you look at the question each one answers:
- BI answers "what is happening?" - recurring, standardized, self-serve. Revenue this month, churn by plan, top cities. Freshness and trust beat cleverness.
- Analytics answers "why did it happen?" - ad-hoc investigation by a skilled human. One-off, exploratory, ends in a finding, not a dashboard.
- Data science answers "what will happen?" - models and forecasts, built on the same trusted data BI standardized.
Why a leader should care about the routing: when the three blur, your analysts spend Monday mornings re-running the same numbers for the same managers - questions a dashboard should answer without them. Every repeat question you push into BI buys back analyst hours for the "why" work only humans can do. Routing is a leadership decision, not a technical one.
The 9am test in one line. If the same question gets asked every Monday at 9am by someone who cannot write SQL, it is BI - build it once, refresh it forever. If the CFO asked it once after a strange board meeting, it is analytics - send a human. Teams that route both through the same inbox burn out their best people on the boring half.
Self-studyWhat BI cannot do3 min read▶
Knowing the limits keeps you from asking a dashboard to do a job it structurally cannot:
- It cannot fix garbage inputs. A dashboard is a mirror of the data underneath. If orders are logged wrong, the chart is confidently wrong - polish included. "The dashboard says so" is not evidence of quality.
- It cannot answer "why". BI shows revenue dipped in March; it cannot tell you whether the cause was pricing, a competitor, or a broken checkout page. Correlation on a chart is a starting point for investigation, never the verdict. When you catch yourself reading causality off a line chart, stop and commission the analysis instead.
- It is not a strategy. "We are becoming data-driven" plus a wall of dashboards changes nothing if decisions still get made the old way. BI accelerates decisions you were already willing to make on evidence - it does not create that willingness.
Why dashboards fail 8 min live
Here is the uncomfortable industry secret: most dashboards get built, launched with fanfare, opened a few times, and then quietly ignored. Stephen Few spent a career cataloguing why. The pattern is not technical failure - the numbers are usually right. It is a funnel of abandonment, and the leaks happen at points a leader controls: what was asked for, whether it is trusted, and whether anyone built the habit of using it.
LiveThe three failure roots4 min▶
Few's opening chapters boil down to three roots, and every abandoned dashboard you have ever sponsored hit at least one:
- Wrong question. The dashboard answers what was easy to build, not what the Monday meeting actually needs. Symptom: people screenshot one corner of it into slides and ignore the rest. Fix: commission from the decision backwards (that is session a4).
- Wrong trust. The first time a number on it disagrees with someone's spreadsheet and nobody can explain why, the room quietly stops believing it - forever. Symptom: "let me just double-check that in Excel." Fix: one agreed definition per number (session a3).
- Wrong habit. Nobody wired it into a recurring moment - no meeting opens with it, no alert fires from it. A dashboard without a ritual is a poster. Symptom: usage stats spike at launch and flatline in week three.
Trust dies in one meeting. A sales VP once challenged a single number on a brand-new pipeline dashboard - his own tracker said something different, and nobody in the room could explain the gap on the spot. The dashboard was right; his tracker double-counted renewals. It did not matter. From that meeting on, every review opened with his spreadsheet, and the dashboard was wallpaper. The lesson for a leader: pre-wire the definition conversations before launch, because trust is only ever lost live.
Self-studyFew's 13 mistakes, leader edition6 min read▶
Stephen Few's famous chapter 2 lists thirteen common dashboard design mistakes. You will never build a dashboard, but you will review plenty - here is each mistake translated into what you would notice from the audience seat. Skim it now; use it as a review checklist in a4.
| Few's mistake | What a leader notices |
|---|---|
| Exceeding a single screen | You scroll to find the number that matters - key facts hide below the fold |
| Inadequate context | A number sits alone: no target, no trend, no comparison - is 4.2M good? |
| Excessive detail or precision | $4,382,916.42 where $4.4M would decide the same thing faster |
| Choosing a deficient measure | The number shown is not the one the decision needs (visits, not conversions) |
| Wrong display media | A pie chart asking you to compare eight nearly-equal slices by eye |
| Meaningless variety | Every chart a different type "to keep it interesting" - reading cost, no gain |
| Poorly designed display media | 3D bars, legends far from the data, labels you have to hunt for |
| Encoding data inaccurately | A bar chart whose axis starts at 80, making a 3% gap look like a cliff |
| Arranging data poorly | The most important number lives bottom-right; trivia owns the top-left |
| Highlighting ineffectively | Everything is bold and red, so nothing is - your eye has no landing spot |
| Useless decoration | Logos, gauges, background photos - ink that answers no question |
| Misusing or overusing color | Color everywhere with no meaning, or red/green as the only signal |
| Unattractive display | So visually rough that people distrust the numbers on looks alone |
Read one chart together ★ 12 min · everyone reads
Enough theory - here is a real chart on real data. This little box is a working BI tool running Daybreak's actual warehouse in your browser. You will never build one of these, but you will read hundreds. So let us install the reading protocol: four questions, in order, every time a chart lands in front of you. Twenty seconds once it is habit.
What is measured? The box says Revenue. But revenue defined how - with refunds? with shipping? Someone decided; a leader knows to ask who. (Press Show SQL - the definition is written right there, even if you do not read code.)
Over what? By month, across the whole company - no region filter, no channel filter. A chart is only as honest as its scope, and scope is invisible unless you ask.
Says who? This comes straight from the warehouse via a governed measure - not somebody's exported spreadsheet. Provenance is the difference between evidence and opinion.
So what? Now, and only now, read the shape. Steady growth... and then look at March 2026. Something dipped. What would you do next - decide, or investigate? (Hold that answer; the builder track solves this exact mystery in b9.)
Your turn: three questions of any chart ★ 10 min · you interrogate
Different chart, same warehouse: revenue by city instead of by month. Before you accept what it seems to say ("our top city is crushing it"), practice the three interrogations that expose most misreads. Work through the cards against the chart below.
LiveInterrogation 1 · Definition - what counts?3 min▶
Is this revenue billed, collected, or recognized? Gross or net of refunds? On this chart, press Show SQL: the answer is literally the formula. In your company the answer lives with whoever owns the semantic model - and if three teams answer differently, you have found the problem session a3 exists to fix. Rule: never compare two numbers until you know they share a definition.
LiveInterrogation 2 · Freshness - as of when?3 min▶
Our playground recomputes on every click, so it is always current. Real dashboards refresh on a schedule - nightly is typical - and a chart carrying yesterday's data into a pricing decision made at 4pm can be a problem or a nothing, depending on the decision. The question costs five seconds: "when did this last refresh?" Good dashboards print the answer in a corner. If yours do not, that is a finding for your homework.
Self-studyInterrogation 3 · Denominator - out of what?3 min read▶
The top city has the tallest bar - but is that because customers there spend more, or simply because there are more of them? Totals reward size; rates reveal behavior. Try it: switch the measure to Avg order value and watch the ranking reshuffle. Neither view is "correct" - they answer different questions - but a leader who only ever sees totals will keep mistaking big for good. Ask "out of what?" whenever a ranking is used to praise or blame.
Try it yourself - this week ◐ 20-30 min total
- Pick one dashboard you already receive weekly and audit it with the reading protocol: what is measured, over what, says who, so what. Write your answers down - the gaps are the finding.
- Note whether that dashboard shows its refresh time and its definitions anywhere. If not, ask the owner both questions and see how long the answer takes.
- Write the 9am-test list for your team: every question that gets asked of an analyst more than twice a month. Each item is a dashboard candidate - bring the list to a4, where you will learn to commission them properly.
- Optional: skim your list against Few's 13-mistakes table above using any one dashboard you own. Count the hits. More than four is normal - and fixable.
Official sources covered
The leader track distills the strategy half of the Google BI certificate and the design judgment of Stephen Few and Cole Nussbaumer Knaflic - the parts an executive actually needs, minus the tooling. This page covers:
Three questions before you go 🎯 ◐ 90 seconds
1 · Your regional managers ask for the same churn-by-plan numbers every Monday morning. Where should that question live?
Recurring + standardized + non-technical audience = BI. Routing it to an analyst burns skilled hours on repeat work; routing it to a model answers a question nobody asked yet.
2 · Revenue dipped in March and the dashboard clearly shows it. What can the dashboard NOT tell you?
BI answers "what is happening". Causality is an analytics job for a skilled human - reading a cause directly off a line chart is the classic executive misstep.
3 · A number on a dashboard looks suspiciously high. Your first question?
Most "wrong" numbers are actually definition mismatches - gross vs net, billed vs collected. Definition first; provenance and freshness next; spreadsheets never.