Why Tables and Matrices Are the Worst Visual for a Mobile BI Dashboard

Ask BI teams which visual breaks hardest on a phone and the same answer comes up in both the Power BI and Tableau communities: not the bar chart, not the line chart — the plain table or matrix. Dense charts at least degrade gracefully; a shrunk table just stops being readable, because the entire point of a table is precision, and precision is the first thing a small screen takes away.

What people are actually saying

One Power BI consultancy put it as bluntly as possible: default mobile views are "very small, very hard to read, and hard to interact with", and they specifically call out matrices and detailed tables as the visual to leave off a phone layout entirely unless it's down to a handful of rows. On the Tableau side, the problem shows up even when a table is paired with another visual: Tableau's automatic phone layout strips containers and stacks worksheets in a strict top-left order, so — in a documented example from TableauFit, a scatter plot and its lookup table end up separated by a scroll, breaking the point-to-name lookup the table existed for in the first place.

Why a table can't just "shrink" the way a chart can

A bar chart survives compression because it has a fallback mode: even squeezed into 300 pixels, you can usually still tell which bar is tallest. A table has no equivalent fallback. Every column needs enough width to show its actual value, and every row needs enough height to stay legible. There's no "gist" version of a spreadsheet — either you can read the number in the cell, or the table has failed at the one thing it's for.

That's why the usual mobile fixes don't help much here. Shrinking the font doesn't reduce how much horizontal space ten columns need; it just makes ten columns of text too small to read. Scrolling sideways technically works, but it turns a glance into a research project, and it's the exact horizontal-scroll problem mobile-first design is supposed to eliminate in the first place.

It's worse when the table drives interaction, not just display

Microsoft's own documentation on Power BI's mobile layout canvas notes that metric visuals aren't interactive on the mobile layout canvas, and tooltips are disabled there too — they only come back in the mobile app itself. So the two ways people normally get extra context out of a dense table — hovering for a tooltip, or interacting with a metric — are either missing or delayed until a different surface. On a phone, mid-meeting, that gap usually just means the context doesn't get checked at all.

What to use instead

Cut to a ranked top-N list. If the table is answering "who's leading, who's lagging," show the top 5 rows by the metric that matters, labeled directly — not the full table sorted differently.
Pull out the one number the table exists to support. Often a table is really tracking a single aggregate (total open cases, overdue count) with the rows as backup detail. Lead with that number as a KPI card; let the table stay a desktop-only drill-down.
Turn columns into stacked label-value pairs per row. Instead of five columns crammed into one row, show one row's worth of data as five stacked lines — trades vertical space for horizontal space, which is what a phone actually has more of.
Replace status columns with a single glanceable indicator. A color dot or a short label reads faster than a numeric column when the question is just "is this okay or not."

For the cases where nothing beats the real table — financial reconciliation, line-by-line audits — the honest answer is to keep it on desktop and put a summary card on mobile with a link into the full detail, rather than pretend a shrunk version of the same table is still usable.

A 10-second test for your own dashboard

Open any table or matrix on your dashboard on your phone. If you have to scroll sideways to see the last column, or squint to tell one row's numbers from the next, that visual has already failed on mobile — no amount of font-size tweaking fixes a problem that's fundamentally about column count, not pixel size.