From Excel to dashboard: the case for narrative data

Open the most-shared spreadsheet at any company and you'll find the same pattern. There's a tab with the raw data. There's a pivot table on a second tab. There's a chart on a third. And in the middle, somebody added a text cell that says, in effect, "the point of this whole thing is X."

The spreadsheet, in practice, is being used to tell a story. The grid is the medium, not the message.

The grid was meant for something else

Excel was designed when records were the unit of business computing. Sales transactions, invoice ledgers, payroll. The grid is perfect for that — every record gets a row, every attribute gets a column, every cell gets a value.

But most of what people do in Excel today isn't recording. It's arguing. "Here's our MRR by month, and here's why the dip in March was actually a good thing." That's a narrative with evidence, not a record.

And narratives don't work in grids.

What a narrative dashboard does instead

A Plain dashboard has sections, not cells. The sections are:

• A header — what is this dashboard about
• KPI tiles — three to five big numbers
• A chart with a title and a caption
• Another chart with a title and a caption
• A ranking table
• A closing section — what to take away

You read it top to bottom. The structure is the argument. The data supports the argument. The reader is meant to come away with the takeaway, not look at the data and make their own.

This isn't anti-spreadsheet

Spreadsheets are still the right tool for: working with the data before you know what story it tells; doing the modeling that becomes the data; collaborative number-crunching among analysts. We're not building a spreadsheet replacement.

We're building the medium that comes after the spreadsheet — when you've done the analysis and need to communicate the result to someone who won't open the .xlsx.

What changes when you make this shift

Three things, in our experience:

First, you produce dashboards faster. Going from "open Excel, chart, copy to PowerPoint, write context, copy to email" to "type a sentence, generate, share link" is a real time compression.

Second, you write the takeaway. Because the format demands a closing section, you actually do the thinking about "what does this mean." Spreadsheets don't make you do that.

Third, the dashboard becomes a referenceable URL. The number from last week's review is still there. Cross-reference it from a doc. Embed a panel from it in a deck. The data has a permanent address.

The pattern, generalized

We think more of work follows this shape than people realize. The artifact you ship is rarely a raw record. It's a curated story with evidence. Treat the artifact as a story-first document, and use real data engines underneath to make the evidence trustworthy.

That's the Plain Sheet model: a narrative dashboard with SQL underneath. Story on the surface; rigor in the source.