Metrics Catalog

Keep metric definitions, owners, formulas, lineage, freshness, and approved usage in one governed catalog. The screen connects Metrics and Dimensions so product analysts can find the “Define metric” action while checking certified and draft.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Monthly active users · Certified and Activation rate · Certified, rather than an empty visual shell.

Metrics Catalog

Template facts

Screen

Workspace

Primary action

Define metric

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product analysts need a clear “Define metric” action without losing sight of certified, draft and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Define metric is clearly available where the task happens.
  • Main view: Metrics keeps the starting point obvious.
  • Connected view: Dimensions supplies nearby context.
  • Metric: Certified is visible with a meaningful value.
  • Another signal: Draft helps people judge what to do next.
  • Representative record: Monthly active users · Certified makes the example specific.
  • Second record: Activation rate · Certified shows the pattern works beyond one item.

States worth designing

  • First-use workspace; show what people can do instead of leaving a blank panel.
  • Loading metrics without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for dimensions; clarify who can continue.
  • Success after choosing Define metric; 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

Metrics → Dimensions → Define metric → Review outcome

Patterns used

Workspace, Metrics, Dimensions, Owners, accessible states, contextual actions

Why these choices work

Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.

In this design, people should be able to compare Monthly active users · Certified with Activation rate · Certified. Make certified clear, then use draft 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 “Define metric” action. The happy path alone is not enough.

Related UI examples: Data Explorer, Alerting Center, Reporting Builder.

Start from this in Figr

Design a metrics catalog screen for our existing software product. Use our real design-system tokens, components and product language. Show Metrics and Dimensions, include believable records such as Monthly active users · Certified, and make define metric easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr