Product Tour

Guide new users through the core product with contextual steps, progress, and skip or resume behavior. The screen connects Tour and Steps so workspace admins can find the “Start tour” action while checking starts and completion.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Welcome · Product overview and Create your first workspace, rather than an empty visual shell.

Use this template in Figr

Template facts

Screen

Workspace

Primary action

Start tour

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Workspace admins need a clear “Start tour” action without losing sight of starts, completion and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

Primary action: Start tour is clearly available where the task happens.
Main view: Tour keeps the starting point obvious.
Connected view: Steps supplies nearby context.
Metric: Starts is visible with a meaningful value.
Another signal: Completion helps people judge what to do next.
Representative record: Welcome · Product overview makes the example specific.
Second record: Create your first workspace 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 tour without changing the layout unexpectedly.
Unavailable or restricted panel; explain the problem and preserve work.
Permission denied for steps; clarify who can continue.
Success after choosing Start tour; 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

Tour → Steps → Start tour → Review outcome

Patterns used

Workspace, Tour, Steps, Segments, 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 Welcome · Product overview with Create your first workspace. Make starts clear, then use completion 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 “Start tour” action. The happy path alone is not enough.

Related UI examples: First Run Checklist, Verification Center, Profile Setup.

Start from this in Figr

Design a product tour screen for our existing software product. Use our real design-system tokens, components and product language. Show Tour and Steps, include believable records such as Welcome · Product overview, and make start tour easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr