Experimentation

Track active experiments, statistical confidence, guardrail metrics, exposure, and the decision each test is driving. The screen connects Experiments and Metrics so product analysts can find the “New experiment” action while checking running and winning.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Onboarding checklist · +6.4% and Pricing CTA copy · +2.1%, rather than an empty visual shell.

Experimentation
Use this template in Figr

Template facts

Screen

Analytics

Primary action

New experiment

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 “New experiment” action without losing sight of running, winning and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New experiment is clearly available where the task happens.
  • Main view: Experiments keeps the starting point obvious.
  • Connected view: Metrics supplies nearby context.
  • Metric: Running is visible with a meaningful value.
  • Another signal: Winning helps people judge what to do next.
  • Representative record: Onboarding checklist · +6.4% makes the example specific.
  • Second record: Pricing CTA copy · +2.1% 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 experiments without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for metrics; clarify who can continue.
  • Success after choosing New experiment; 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

Experiments → Metrics → New experiment → Review outcome

Patterns used

Analytics, Experiments, Metrics, Audiences, 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 Onboarding checklist · +6.4% with Pricing CTA copy · +2.1%. Make running clear, then use winning 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 “New experiment” action. The happy path alone is not enough.

Related UI examples: Retention Cohorts, Reporting Builder, Funnel Analysis.

Start from this in Figr

Design a experimentation screen for our existing software product. Use our real design-system tokens, components and product language. Show Experiments and Metrics, include believable records such as Onboarding checklist · +6.4%, and make new experiment easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr