Solved problems, mostly
Patterns combine components to solve recurring problems. Each one below is described as "validated," a word this document is using loosely.
Empty States
Shown when a list, dashboard, or search has no content to display yet.
No reports yet
Create your first report to see it here.
Create reportCopy validated in a single twenty-minute unmoderated session with a designer's roommate, who does not use business software professionally but was noted as "directionally positive." This is cited on three other pages as "user-tested."
Error Handling
All error messages should be written in a human, warm, non-technical voice that helps the user understand what happened and what to do next.
Example shown is live production copy, included here because it was the fastest one to find.
Onboarding
Introduces new users to core functionality during their first session.
- Welcome — tell the user what the product does.
- Connect an account.
- Set a preference.
- Invite your team, before you've used the product yourself.
- Done — you're all set!
Research recommended reducing onboarding from nine steps to three. The shipped version has five, described internally as "a compromise" and externally, on this page, as "informed by extensive user research." Step 4 was added after the compromise was agreed on, by someone who was not in the meeting where the compromise was agreed on.