Excel & BI Tools

Not all statistics happens in code. A great deal of it happens in a spreadsheet, where an analyst types a quick =AVERAGE, and a great deal of it is consumed in a dashboard, where a manager filters a chart without writing a line of anything. Excel, Power BI, and Tableau are the tools of that world. They will not replace R or Python for modeling, but they are often where a study begins (a fast look at the numbers) and where it ends (a result that a non-technical audience can actually use). Knowing their strengths, and their limits, is part of being a complete analyst.

Excel is the most widely used data tool on earth, and for good reason. Its grid is immediate, its formulas recalculate the instant you change a number, and it hides a surprisingly complete statistics kit. You can go a long way without leaving it.

The defining property is that everything is live. A summary cell holds a formula, not a typed number, so when the data changes the summary changes with it. The companion workbook below is built entirely this way, so you can feel it.

A spreadsheet is a place to do analysis; a dashboard is a place to share it. Business intelligence tools exist to turn a data source into an interactive report that a non-technical audience can explore on their own, filtering, drilling down, and hovering for detail, without touching a formula or a query.

The shift is from a static snapshot to a live, connected view. A BI dashboard plugs into a database or warehouse, refreshes on a schedule, and lets each viewer slice the same numbers their own way. Underneath sits a data model (a semantic layer) that pre-defines the tables, relationships, and measures, so that ‘revenue’ means the same thing to everyone who uses it. This is what people mean by self-service analytics: the analyst builds the model once, and the organization asks its own questions of it.

Two products dominate business intelligence, and most teams standardize on one. They do broadly the same job, connect to data, build interactive dashboards, share them, but they come from different worlds and reward different priorities.

For a statistician, the important thing both share is that they are descriptive and exploratory by design. They excel at showing what the data says, counts, trends, comparisons, breakdowns, and at letting an audience probe it interactively. What they do not do out of the box is inference: a dashboard will happily show two bars of different heights, but it will not tell you whether the difference is statistically significant. That judgment still comes from the methods in this book, run in the tools of the next comparison.

This is the comparison that matters most, because it decides which tool does which part of a study. The short version: BI tools optimize for accessibility and interactivity; the code and commercial-stats tools optimize for statistical depth and reproducibility. They are complements, not competitors.

How do statisticians actually use the dashboard tools, then? Mostly for the parts of the work that are visual and exploratory: a first look at a new dataset, a monitoring dashboard that tracks a metric over time, a way to let collaborators explore results, and the final report that goes to leadership. The inference stays in code: you fit the model, run the test, and compute the interval in R, Python, or SAS, then feed the tidy results into a dashboard so an audience can see them. Better still, both Power BI and Tableau can run Python or R scripts directly, so a chart in the dashboard can be powered by a real model underneath. The line between the two worlds is not a wall; it is a handoff.

All three tools are being reshaped by AI, and the changes matter for how studies get done. Excel now ships Python in Excel, which runs pandas and the plotting libraries in a spreadsheet cell, and a Copilot assistant that writes formulas and summaries from a plain-language request. Power BI and Tableau have added AI features too: natural-language querying (‘ask a question, get a chart’), automatic anomaly and trend detection, and Copilot-style assistants that build visuals for you.

Used well, they earn a real place in a statistical study. A dashboard is an excellent home for exploratory data analysis, for monitoring an experiment or a process over time, and for communicating findings to people who will never open a notebook. The discipline is to remember what they are not: a dashboard describes and displays, it does not, by itself, establish that an effect is real, control for a confounder, or quantify uncertainty. Those are the jobs of the methods this book has taught. Pair the two, rigorous analysis in code, clear communication in a dashboard, and you get the best of both.

Eight questions on Excel, dashboards, Tableau and Power BI, and how they compare to code tools. Answer them, hit Check Answers, and keep refining until you score 100%. Your progress is saved.