Create an account and succeed at first use

1 / 5 · Information

Define the first useful result

Screen: welcome. For a fictional project app, the goal is to create and reopen one draft project. Explain the required fields, verification step and next action before asking for an account.

Expected result: One first task has a visible completion criterion.

Common mistake: Avoid a long tour without a concrete task.

• Review form errors and recovery

2 / 5 · Decision

Check the account prerequisites

Can the test user receive the required verification and complete the first task with the requested permissions? If not, retain the context and explain the missing requirement before proceeding.

Expected result: Verification and access requirements are understood and available.

Common mistake: Do not bypass verification or request unnecessary permissions.

3 / 5 · External action

Create and verify the test account

Screens: registration, error, verification. In your own app, submit the test form, correct a harmless validation error without losing non-secret input, then complete the required verification. Use the existing guide and Pack to design these states.

Perform this yourself in your tool, only if authorized. This button updates local progress; it runs no operation.

Expected result: The verified account reaches its authorized starting screen.

Common mistake: A submitted form or sent email does not prove account access.

• Read the form Pack unchanged

4 / 5 · External action

Complete one useful task

Screens: empty state, create draft, project list. Create the fictional draft in your test app. If the first task involves finding content, use the search recipe to distinguish missing input, no results and outage, retaining explicit constraints.

Perform this yourself in your tool, only if authorized. This button updates local progress; it runs no operation.

Expected result: The draft is visible with a clear next action.

Common mistake: Do not mark onboarding complete merely because a tour closed.

• Try search and recovery

5 / 5 · Verification

Return and verify the first result

Revisit the app through its normal entry. Verify account access, reopen the draft and check its saved content. Test keyboard navigation and 320 px layout separately. Keep failures and untested cases visible.

Expected result: Access and the first saved result survive a fresh visit.

Common mistake: A local mission check is a declaration, not proof of account creation.