KPI dashboard Data Studio builds for leadership teams

What makes a good KPI dashboard Data Studio one-pager?

A good one-pager answers "are we on track?" in under a minute. It shows a small, fixed set of metrics, each against its target and its trend, with color only where something needs attention.

Leadership pages fail when they try to hold everything. We push back on adding a fourteenth scorecard, because the page stops being read. Detail belongs on the pages beneath, one per function, where department heads can go as deep as they need.

• Commercial: revenue, new customers, pipeline coverage, win rate.
• Operations: on-time delivery, output, utilization, backlog.
• Finance: gross margin, cash, receivables over 60 days.
• People: headcount against plan, attrition.

How do you show targets vs actual in Data Studio?

We store targets in a Google Sheet by month and metric, then join them to actuals so every scorecard and chart can show both. Finance or the KPI owner edits the sheet when a target changes, and the dashboard follows.

Scorecards show actual, target and percent to target, with conditional formatting for on track, at risk and behind. Bullet charts work well for monthly progress, and a line chart with a target series shows whether the gap is closing. Where a target is cumulative, such as year-to-date revenue, the calculated field accumulates both series the same way, so the comparison is fair on day ten as well as day thirty.

How does drill-through work from the summary page?

Each scorecard on the summary links to the page that explains it, and filters carry across. A leader who sees on-time delivery slipping clicks through to the operations page already filtered to the same period and region.

We use report-level filter controls so date and region selections persist between pages, cross-filtering so clicking a bar in one chart filters the others, and drill-down on dimensions such as region to site to line. Cross-data-source filtering, added in January 2026, lets one control filter charts that read from different sources, which used to need workarounds.

Where does the data for an executive dashboard come from?

It comes from each department's own system, brought into one model. Sales data from the CRM, operations data from production or logistics systems, finance data from accounting exports and HR data from a headcount sheet.

Pulling five systems into one page is beyond what a blend handles well, since blends join at most 5 sources and only on equal keys. For most leadership dashboards we build a small model in Google Sheets or BigQuery with one row per metric per period, which makes the summary page fast and every number traceable. The manufacturing dashboard we built, tracking units produced and lost, productivity per machine and maintenance cost, is a typical example of a department page that feeds a leadership view.

How do you get a leadership team to agree on KPIs?

We run a short definitions workshop before building anything. For each proposed KPI we write down the exact formula, the source system, the owner, the target and how often it changes.

This is usually where the real work is. Two departments often define "active customer" or "on time" differently, and the dashboard cannot settle that on its own. Once definitions are agreed and signed off, they appear in the report as info text next to each metric, so a new manager reads the same definition the leadership team agreed.

A KPI dashboard Data Studio project that skips this step tends to be rebuilt within a year. One that starts with agreed definitions usually only needs new targets each financial year.

How is the dashboard delivered to busy executives?

Most executives get it in their inbox. A scheduled email sends the summary page as a PDF and link every Monday morning, and the full report is there when they want the detail.

On Data Studio Pro, schedules can run hourly and deliver to Slack or Google Chat, and alerts can notify an owner when a metric crosses a threshold. Viewers do not need a Pro licence, so the leadership team reads the dashboard at no extra licence cost.

Why do executive dashboards stop being used?

They usually stop being used because one number was wrong once and nobody trusted the rest. The second most common reason is that the page grew until it answered every question badly.

We guard against both. Every KPI is checked against its source before launch by a second analyst, and the summary page shows the date each source last loaded, so stale data is visible rather than silent. A change request process sends new metrics to department pages by default, and only a leadership decision promotes one to the summary.

We also design for the way executives actually read: the page fits a laptop screen without scrolling, numbers are rounded to what matters for a decision, and comparisons are always to target first, then to last period. Small details, but they decide whether the report is opened on Monday or ignored.