First Run Checklist

Help a newly activated workspace reach its first useful outcome with a short, visible checklist. The screen connects Checklist and Quick starts so workspace admins can find the “Finish setup” action while checking steps complete and activation.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Create first project · Done and Invite a teammate · Done, rather than an empty visual shell.

First Run Checklist
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Finish setup

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 “Finish setup” action without losing sight of steps complete, activation and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Finish setup is clearly available where the task happens.
  • Main view: Checklist keeps the starting point obvious.
  • Connected view: Quick starts supplies nearby context.
  • Metric: Steps complete is visible with a meaningful value.
  • Another signal: Activation helps people judge what to do next.
  • Representative record: Create first project · Done makes the example specific.
  • Second record: Invite a teammate · Done 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 checklist without changing the layout unexpectedly.
  • Unavailable or restricted panel; explain the problem and preserve work.
  • Permission denied for quick starts; clarify who can continue.
  • Success after choosing Finish setup; 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

Checklist → Quick starts → Finish setup → Review outcome

Patterns used

Workspace, Checklist, Quick starts, Templates, 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 Create first project · Done with Invite a teammate · Done. Make steps complete clear, then use activation 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 “Finish setup” action. The happy path alone is not enough.

Related UI examples: Verification Center, Product Tour, Profile Setup.

Start from this in Figr

Design a first run checklist screen for our existing software product. Use our real design-system tokens, components and product language. Show Checklist and Quick starts, include believable records such as Create first project · Done, and make finish setup easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr