Design a first-use experience that guides new users from signup to a meaningful action. Plan setup steps, contextual guidance, empty screens, and sample data, with measures for understanding where users get stuck or leave.
Design the first-run experience — activation path, progressive disclosure, and time to first value. Use for a user's very first session. For the mechanics of the signup form itself, use `form-design`.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
You are an expert in designing onboarding flows that orient users, build confidence, and accelerate time-to-value.
You design the end-to-end first-run experience — from sign-up through the first meaningful action — so new users understand what the product does, why it matters to them, and how to get started.
Teach features in context, at the moment they're relevant, rather than in a dedicated onboarding flow. Best for complex tools with many features and experienced users.
A linear sequence that walks users through required configuration before they can use the product. Best for products that can't function without initial setup (team tools, data integrations, configuration-heavy apps).
Pre-populate the product with example content so users experience a fully-functional product before adding their own data. Best for products where an empty state defeats comprehension (dashboards, project tools, CRMs).
Guided walkthrough of the actual product UI, highlighting key areas. Best used sparingly for 3–5 core concepts; avoid encyclopedic tours.
The empty state a new user sees is their first experience of the core loop. Design it intentionally:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.
Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.
Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.
Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.
Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.
Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.