Search

Sign in to launch Copilot/Codex from the palette.

SHOW ME

How we want to see data

Same database. Same quarter. Two people ask for a report.

CEO "How are we doing?"
Engineer "What's happening?"

Same question. Completely different answer expected.

WHAT THEY ACTUALLY WANT

A decision-maker may want

  • One number
  • Direction (up or down)
  • What to do about it
  • Confidence that someone understands the details

An investigator may want

  • The query
  • The methodology
  • Edge cases and caveats
  • Confidence that the number is actually right

A person making a quick operational decision may need the result, direction, and next action before the supporting detail.

A person investigating the result may need the query, method, caveats, and source data before deciding whether the conclusion holds.

SAME DATA, TWO DASHBOARDS
+0% Revenue Growth (Q2)
Jan
Feb
Mar
Apr
May
Jun
Pipeline strong. Double down on outbound.
Decision-ready. 3 seconds to action.
THE PARALLEL

This isn't a data problem. It's a communication problem. And it shows up everywhere.

Data Dashboard vs Query + methodology
Code README vs Source code
Product Landing page vs API docs
Research Abstract vs Full paper
AI Agent summary vs Full context window

Many domains have this split. One audience needs the what. The other needs the how. Neither is wrong. They're solving different problems with the same information.

THE MISTAKE

Most teams build one dashboard and show it to everyone.

CEO gets the engineer's view Drowns in detail. Asks someone else to summarize. That person becomes the bottleneck.
Engineer gets the CEO's view Doesn't trust it. Rebuilds the query from scratch. Now there are two sources of truth.

The dashboard isn't wrong. The audience is wrong. Same data, wrong encoding for the decoder.

THE FIX

Build two views. One source of truth, two presentations.

1
Engineer builds the query. This is the source of truth. Methodology, caveats, edge cases. It lives in version control.
2
Dashboard summarizes the query. Big numbers, direction, recommended action. Derived from the query, not separate from it.
3
Both views link to each other. CEO can drill down. Engineer can zoom out. The bridge exists.

The CEO doesn't need to understand the query. The engineer doesn't need to care about the slide deck. But they both need to know the other view exists.

Data doesn't have an opinion about how it's displayed.
Your audience does.