Designing an internal communications dashboard from scratch

How to Build an Internal Communications Dashboard, Step by Step

By Nicolas Saliba · 8 min read

A five-step build process from measurement questions to a live view

Key takeaways

Build in order: questions first, metrics second, data sources third, layout fourth, automation last. Reversing the order is why dashboards fail.
Choose metrics that answer a question and that you can act on; drop anything that fails either test.
Automation is the step that makes a dashboard survive; one that needs manual rebuilding each month will be abandoned.

Step 1: start with the questions
Step 2: choose metrics that answer them
Step 3: connect the data sources
Step 4: design the layout
Step 5: automate and iterate
Keeping the dashboard alive

Introduction

Most internal communications dashboards are built metric-first: someone lists every available number and arranges it on a screen. The result is dense and unused. This guide builds in the opposite order, starting from the questions, which is the difference between a dashboard people read and one they ignore. For what belongs on the finished view, pair this with our guide to dashboard design.

The order of the steps is the whole method, so it is worth saying why. Each step constrains the next: the questions decide the metrics, the metrics decide the data sources, the sources shape what the layout can show, and only then does automation make it repeatable. Teams that start in the middle, with the data they happen to have or a layout they admired, end up with a dashboard that answers no clear question and is abandoned within a quarter. Build in order and each decision has a reason behind it.

Step 1: start with the questions

Before opening any tool, write the three to five questions the dashboard must answer: are we reaching the workforce, did the strategic message land, are the right people engaged, is the intranet working. The dashboard exists to answer these, and any metric that does not serve one of them is clutter. This step takes an afternoon and saves weeks.

The questions also need an owner's sign-off, because a dashboard built to answer the IC team's questions may miss the ones leadership actually asks. Getting the IC lead, and ideally a representative stakeholder, to agree the question list before any building starts is what aligns the dashboard with the decisions it is meant to support. It is far cheaper to negotiate the questions on one page now than to rebuild the dashboard after its first unimpressed leadership viewing.

Practical step: Write your dashboard's questions on one page and get the IC lead to sign off before you build anything. The page is your scope.

Step 2: choose metrics that answer them

For each question, choose the smallest set of metrics that answers it. 'Are we reaching the workforce' needs cross-channel reach and segmented reach, not a dozen activity counts. Apply two tests to every candidate metric: does it answer a question, and can someone act on it. If it fails either, it does not go on the dashboard.

The smallest-set discipline is harder than it sounds, because every metric has an advocate and adding one feels safer than leaving it out. But each extra metric dilutes attention and slows the read, so the cost of a metric that answers no question is real even if it seems harmless. The two tests, does it answer a question and can someone act on it, are deliberately strict, because a dashboard earns its usefulness by what it excludes as much as by what it shows.

Practical step: For every metric you are tempted to include, name the action someone would take based on it. No action means no place on the dashboard.

Step 3: connect the data sources

Now map each metric to its source: SharePoint, Viva Engage, Teams, the newsletter, and your audience model. This is where the build gets hard, because the valuable metrics are cross-channel and need deduplication and a single segmentation model. A build-your-own approach carries this work itself; a dedicated platform brings the sources pre-connected.

This step is where many dashboard projects quietly fail, because the metrics that matter most, unique cross-channel reach and consistent segmentation, depend on joining and deduplicating data across sources that do not naturally connect. A single-channel dashboard is straightforward; the cross-channel one that answers the real questions requires either sustained engineering to build the joins yourself or a platform that arrives with the sources already unified. Discovering this at step three, rather than after committing to a build, is exactly why the ordered method is worth following.

Practical step: List the data source behind each chosen metric. Any metric whose source you cannot reliably access is a gap to solve before layout, not after.

Step 4: design the layout

Lay the dashboard out to be read top to bottom: the headline number first, then the answer to each question in priority order, with segmentation one click away. Keep one view for the IC team and a simpler one for leadership. Resist decoration; every element should earn its place by answering a question.

Layout is communication, not decoration, so design it for how a reader's eye moves rather than for visual impact. The most important number goes where the eye lands first, supporting metrics follow in priority order, and detail sits one level down for those who want it, so the dashboard reads as a sentence rather than a wall. The two-view discipline, a detailed one for the team and a stripped-down one for leadership, prevents the single most common layout failure, which is trying to serve both audiences with one cluttered screen.

Practical step: Show a draft to someone outside IC and ask what the dashboard is telling them. If they cannot say in 30 seconds, simplify.

Step 5: automate and iterate

A dashboard that must be rebuilt by hand each month will be abandoned by quarter two. Automate the refresh so it reproduces itself, then iterate: drop metrics no one uses, add the question that keeps coming up. Native tooling and build-your-own make automation hard; a platform with reproducible templates makes it the default. Tryane produces cross-channel dashboards on executive-ready templates, is SOC 2 Type 2 certified, and deploys in a couple of hours.

Automation changes what the team's time is spent on. When the data refreshes itself, the monthly effort shifts from rebuilding numbers to interpreting them and acting, which is the work that actually adds value. Iteration is the other half: a dashboard is never finished, and the discipline of dropping metrics that no one acts on and adding the question that keeps recurring is what keeps it relevant. A dashboard that is automated and iterated stays alive; one that is manual and frozen is abandoned.

Practical step: Time the monthly rebuild of your current dashboard. If it is more than 30 minutes, automating the refresh is the highest-value change you can make.

Keeping the dashboard alive

The failure mode for dashboards is not a bad launch but a slow death, and preventing it takes deliberate maintenance. Schedule a quarterly review of the dashboard itself, separate from reading its numbers, to ask which metrics are actually used, which questions have changed, and what should be dropped or added. A dashboard that is never pruned accumulates dead metrics until it becomes the cluttered screen you set out to avoid, while one that is reviewed stays lean and trusted.

Ownership is the other half of survival. A dashboard with no named owner drifts when its creator moves on, the refresh breaks and no one fixes it, the questions go stale and no one updates them. Naming an owner who is responsible for the quarterly review and the health of the data pipeline is what turns the dashboard from a project that ends at launch into a living instrument the function relies on, which is the only kind worth building.

Practical step: Name an owner and put a quarterly dashboard review in the calendar. The review keeps it lean; the owner keeps it running.

Tryane is SOC 2 Type 2 certified, GDPR / RGPD compliant by design, and EU-hosted by default, with data residency in other countries (notably the US) available on demand. Deployment takes a couple of hours: SSO via Azure AD or Entra ID plus channel connection. Power BI integration is on the roadmap; in the meantime Tryane provides its own dashboards with executive-ready templates.

Next step. To build an internal communications dashboard that reproduces itself on your actual cross-channel data, book 30 minutes with Jérémy: https://tryane.com/en/#contact-home

This article reflects information as of 2026-05-19. Adapt the build steps to your tooling and data sources.

FAQ

How do I build an internal communications dashboard?

Build in order: start with the three to five questions it must answer, choose the smallest set of metrics that answers them, connect the data sources, design the layout to be read top to bottom, then automate the refresh and iterate. Reversing that order is why most dashboards fail.

What is the most common mistake building an IC dashboard?

Building metric-first: listing every available number and arranging it on a screen. The result is dense and unused. Starting from the questions, and dropping any metric that does not answer one, is the fix.

Which metrics belong on the dashboard?

Only metrics that pass two tests: they answer one of your defined questions, and someone can act on them. Cross-channel reach, segmented reach, engagement-to-reach, and campaign results usually qualify; raw activity counts usually do not.

Why does automation matter for a dashboard?

Because a dashboard that must be rebuilt by hand each month gets abandoned. Automating the refresh so it reproduces itself is what lets the team curate the narrative instead of rebuilding the data, which is what keeps the dashboard alive.

How do I keep a dashboard from dying after launch?

Name an owner and run a quarterly review of the dashboard itself, asking which metrics are used, which questions changed, and what to drop or add. Unpruned dashboards accumulate dead metrics; unowned ones break when their creator moves on.

Does Tryane build IC dashboards?

Yes. Tryane produces cross-channel dashboards on executive-ready templates that reproduce automatically, with audience segmentation and unlimited history. It is SOC 2 Type 2 certified and EU-hosted by default with other regions on demand.

Sources

• Gallagher State of the Sector 2025

• Microsoft Learn, SharePoint site usage and analytics

• Microsoft Learn, Viva Engage analytics for admins

• Gallup State of the Global Workplace 2025

• Deloitte Human Capital Trends 2026