Recommendation Studio

Build and tune recommendation strategies with clear audience rules, placements, fallbacks, and performance signals. This example brings Overview and Strategies together so product and growth teams can find the next task without losing context.

It includes representative records such as Homepage · Popular with similar teams and Checkout · Frequently bought together. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Recommendation Studio
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Create strategy

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to create strategy while keeping active strategies, ctr and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Strategies keeps the related context close.
  • Primary action: Create strategy stays visible when people need it.
  • First signal: Active strategies shows a useful value (18).
  • Second signal: CTR gives additional context (6.8%).
  • Sample record: Homepage · Popular with similar teams.
  • Next record: Checkout · Frequently bought together.

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Strategies → Create strategy → Review outcome

Patterns used

Workspace, Overview, Strategies, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to overview and strategies. People need to distinguish Homepage · Popular with similar teams from Checkout · Frequently bought together. Keep active strategies visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Create strategy”. Make error recovery as clear as the happy path.

Related screen examples to explore next: .

Start from this in Figr

Design a recommendation studio screen inside our existing product. Use our current components, tokens and content language. Include Overview and Strategies views, credible records like Homepage · Popular with similar teams, and a clear “Create strategy” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr