Analytics & BI Tools · Chapter 6 of 8
Choosing, with real scenarios
Five situations, and what actually fits each. The answer is rarely the best tool.
Tool selection questions are decided by context far more than by capability. Here are the scenarios that recur, and what usually fits.
| Situation | Usually fits | Because |
|---|---|---|
| Microsoft-heavy enterprise, thousands of report consumers, tight budget | Power BI | Licensing is already paid for and per-consumer cost is the dominant term at that scale |
| A hundred genuine analysts doing exploratory work | Tableau | Exploration is what it is best at, and the creator count is small enough that cost is bearable |
| Numbers must agree across the company, and they currently do not | Looker or a semantic layer | The problem is definition governance, not visualisation |
| Startup, small team, everything in one warehouse | Metabase or Superset | Open source, cheap, adequate — and the money is better spent on the warehouse |
| Regulated function needing auditable, analyst-built preparation | Alteryx, with a promotion path | Visible workflow logic satisfies audit; the promotion path prevents shadow production |
What actually decides it in practice
- Who your users are — analysts who explore, or consumers who read. This single question decides more than any feature comparison.
- What you already own. A bundled tool at effectively zero marginal cost beats a better tool at full price for most organisations, and pretending otherwise wastes everyone's time.
- Whether you have someone to model. A semantic layer needs an owner; without one, buying Looker gets you an expensive report tool.
- Where the metric definition will live. Decide this before choosing a tool, and the tool choice narrows considerably.
- Migration cost is usually underestimated by a factor of two or three, because rebuilding reports is the visible part and rebuilding trust in the numbers is not.
The answer that lands in an interview
Not a favourite. Establish the users, the existing estate, and where definitions live — then recommend, and say what you would give up. “I would take Power BI here because the consumer count makes licensing the dominant cost, and I would accept weaker exploratory analysis and invest the saving in a proper semantic layer” is a senior answer.
Naming what you sacrifice is what separates a recommendation from a preference.