impeccable-onboardlisted

Get users to first value as fast as possible. Onboarding's job is not to teach the product. Its job is to get people to the moment that proves the product is worth their time. ## Assess Onboarding Needs Understand what users need to learn and why: 1. **Identify the challenge**: - What are users trying to accomplish? - What's confusing or unclear about current experience? - Where do users get stuck or drop off? - What's the "aha moment" we want users to reach? 2. **Understand the users**: - What's their experience level? (Beginners, power users, mixed?) - What's their motivation? (Excited and exploring? Required by work?) - What's their time commitment? (5 minutes? 30 minutes?) - What alternatives do they know? (Coming from competitor? New to category?) 3. **Define success**: - What's the minimum users need to learn to be successful? - What's the key action we want them to take? (First project? First invite?) - How do we know onboarding worked? (Completion rate? Time to value?) **CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible. ## Onboarding Principles Follow these core principles: ### Show, Don't Tell - Demonstrate with working examples, not just descriptions - Provide real functionality in onboarding, not separate tutorial mode - Use progressive disclosure, teach one thing at a time ### Make It Optional (When Possible) - Let experienced users skip onboarding - Don't block access