Executive BI

Give leaders a compact view of growth, retention, revenue, efficiency, and the few risks that need a decision now. The screen connects Overview and Growth so product analysts can find the “Share report” action while checking arr and nrr.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Enterprise growth · 24% and Mid-market growth · 18%, rather than an empty visual shell.

Executive BI

Template facts

Screen

Analytics

Primary action

Share report

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product analysts need a clear “Share report” action without losing sight of arr, nrr and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Share report is clearly available where the task happens.
  • Main view: Overview keeps the starting point obvious.
  • Connected view: Growth supplies nearby context.
  • Metric: ARR is visible with a meaningful value.
  • Another signal: NRR helps people judge what to do next.
  • Representative record: Enterprise growth · 24% makes the example specific.
  • Second record: Mid-market growth · 18% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading overview without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for growth; clarify who can continue.
  • Success after choosing Share report; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Overview → Growth → Share report → Review outcome

Patterns used

Analytics, Overview, Growth, Revenue, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Enterprise growth · 24% with Mid-market growth · 18%. Make arr clear, then use nrr to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Share report” action. The happy path alone is not enough.

Related UI examples: Alerting Center, Metrics Catalog, Data Explorer.

Start from this in Figr

Design a executive bi screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Growth, include believable records such as Enterprise growth · 24%, and make share report easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr