An executive dashboard should include six things: a brief of what changed, a small set of signals that each name an owner, a definition and source attached to every number, a freshness and status label, a stated comparison rule, and a path back to the evidence. Everything else belongs one layer down. The test for the first screen is whether a number can survive being questioned out loud.

What actually belongs on the first screen?

Six pieces of furniture, not six charts. A chart is a rendering choice. These are the things that have to be present regardless of how you draw them.

1. A brief of what changed. Under a hundred words, in business language, written before anyone scrolls. Not "organic sessions down 12 percent" but which segment moved, whether the move is outside the normal range, and whether the same move shows up anywhere else.

2. Signals that name an owner. Every signal on the executive layer names the person who investigates when it moves. Uber's engineering team listed lack of ownership as one of six named data problems in their March 16, 2021 writeup on data culture: datasets frequently carried no quality guarantee because nobody was accountable for them. A signal with no owner is a notification, and notifications get ignored.

3. A definition and a source, attached to the number. Not in a wiki, not in a data dictionary somebody last opened in 2024. On the page, one click from the figure.

4. A freshness and status label. When was this last updated, and is it live, delayed, estimated, or demo data.

5. A comparison rule, stated. Against what prior period, on what basis. If a metric compares to trailing 28 days and the one next to it compares to last calendar month, the page is lying by juxtaposition.

6. A path to the evidence. Every summary points back to the query, the window, and the segment underneath it.

That list is short on purpose. The argument for why the design work starts before the data does is made in why executive dashboards fail before the data arrives. This piece is the inventory that comes after you accept that argument.

Why does the same metric show two different numbers?

Because nobody wrote down which definition was the real one, and both are now shipping.

Uber published the anatomy of this on January 12, 2021, in their uMetric writeup by Will Yu, Yun Wu, Xiaodong Wang, and Wenrui Meng. Their Shopping Session metric, queried with identical parameters, returned 6.53 million in one internal tool and 6.20 million in another. The cause was mundane: one tool carried stale filters that did not reflect current rider states. Uber counted over 10,000 metrics across the company, and noted that a popular metric would spawn 10 to 100 separate instances of itself as teams tweaked SQL and built their own pipelines.

Airbnb told the same story from the executive's chair. In Robert Chang's April 30, 2021 post on the Airbnb Tech Blog, the framing is direct: when the CEO asked which city had the most bookings the previous week, Data Science and Finance sometimes gave diverging answers, using slightly different tables, metric definitions, and business logic. Airbnb's answer was Minerva, a single source of truth that as of that post carried more than 12,000 metrics and 4,000 dimensions from more than 200 data producers.

Note the sizes. These are not small companies with sloppy habits. They are companies that got large enough that the ambiguity became visible, and both concluded that the definition is the asset and the chart is the byproduct.

The operating consequence for the executive page is narrow and concrete. A number with no definition attached is an opinion in a nice font. If a leader cannot answer "what does this count" without asking someone, the number should not be on the first screen yet.

What does a freshness label actually need to say?

More than a timestamp. Uber's data quality framework, in the same March 2021 writeup, runs five checks on every dataset: freshness (defaulting to three nines on completeness delay), completeness against the source system, duplication (0 percent on raw data by default), cross-datacenter consistency, and semantic checks like null and range constraints. They also tier datasets from Tier-1 (compliance, revenue, or brand impacting) down to Tier-5 (temporary, auto-deleted when unused), and the tier sets the incident severity and the bug-fix SLA.

You do not need Uber's infrastructure to steal the idea. An executive dashboard needs three fields per connected source: last updated, status (live, delayed, estimated, demo), and tier. Tier is the one most dashboards skip, and it is the one that tells a leader how hard to lean on the number. A Tier-1 revenue figure and a Tier-4 marketing estimate should not look identical on the page just because they are both blue.

What belongs one layer down?

Most of it. Specifically:

  • Any metric with no named owner. If nobody investigates when it moves, it is decoration.
  • Segment and cohort breakdowns. Useful the moment a signal fires, noise before that.
  • Charts that only show shape. If the takeaway is "it goes up and to the right," a sentence is cheaper.
  • Anything that needs an analyst to interpret. That is an analyst view, and it is a good thing, just not here.
  • The chat box. Practitioners are openly unconvinced. On r/BusinessIntelligence, a thread titled "The 'AI chat' feature bolted onto most BI tools doesn't actually solve the underlying problem" drew 22 comments, and a companion thread asking "Are any of your BI users actually moving from dashboards to chat?" pulled 73 comments on 26 points. That comment-to-upvote ratio is the tell: it is an open question in the field, not a settled feature. A chat box on top of undefined metrics returns confident sentences about numbers nobody agreed on.

How do you decide what makes the cut?

Run every candidate through three questions before it earns pixels.

  1. Who owns it? Name a person, not a team.
  2. What decision changes if it moves? If the honest answer is "we would look into it," that is not a decision, that is a hobby.
  3. How would we know if it were wrong? If there is no answer, the metric is not ready for the executive layer at any size. This is not theoretical fussiness. The recurring shape of the practitioner complaint is the same everywhere. On r/BusinessIntelligence, someone asked how to turn messy HR data into insights for an executive leadership presentation. The most useful reply in the thread was not about charts or tools. It asked how leadership defines health, talent, and budget efficiency, or whether that had quietly been left to the person building the deck. Parallel threads asking "what's the most annoying part of building BI dashboards" run on r/BusinessIntelligence (39 comments) and r/tableau (29 comments) with the same standing answer underneath: the requirements were never definitions.

Definitions first, then ownership, then freshness, then charts. That is the order Beacon is built in: an executive layer that summarizes what changed across brand, web, search, marketing, social, sales, and competitors, with the source and status of each number carried alongside it rather than buried.

It is also why a serious dashboard is a software project and not a reporting exercise. Authentication, permissions, normalized sources, metric contracts, and supportable deployment are the actual work, which is the same reason this overlaps with SaaS platform development. The chart is the last five percent.

Build the page so that every number on it can be questioned in a meeting and survive. If a figure cannot survive that, it does not belong on the first screen. It belongs one layer down, where somebody has time to check it.