Writing · MARGIN NOTESFor founders
Rebuilding a dashboard nobody wants to use
Most dashboards fail because they show everything and decide nothing. The rebuild starts by naming the decision the screen is for.
- Author
- Nicola Riker Urdaneta
- Published
- October 12, 2026
- Reading time
- 1 min read
Contents
The chart is not the product
If people export to a spreadsheet before they will trust the page, the page is a poster. Filters nobody remembers, charts that do not answer a question, and a table that is doing the real work: that is the usual shape. I have watched this inside product teams. The fix is rarely another chart type.
Name the decision
A useful screen supports one decision. Ship this run or hold it. Call this account or wait. The rebuild starts there. Everything that does not serve that decision is a candidate to cut, even if it took a week to draw.
Then build the smaller thing
Keep the table if the table is the job. Give it a stable order, a name for each column, and a way back to the record. Add a chart only when it changes the decision faster than reading the row. Dashboards that survive are usually quieter than the ones they replaced. If the current screen is where work goes to stall, that is a product problem before it is a visual one.