Redesigning the Onboarding Flow
What is the goal?
Reduce drop-off during onboarding by simplifying the first-time user experience. Currently 62% of new sign-ups abandon the product before completing setup. The goal is to get that below 30% within 6 weeks of launch by removing unnecessary steps and introducing progressive disclosure.
Solution brainstorming
A streamlined 3-step onboarding wizard that replaces the current 7-step process. Step 1: Pick your role (designer, developer, PM). Step 2: Connect one integration (Figma, Slack, or Jira). Step 3: Create your first project with a guided template. Each step has a skip option and a progress indicator. We defer profile completion, notification preferences, and team invites to contextual prompts later in the journey.
Research
Problem Definition
Define the problem clearly
What is the problem you're solving?
New users are overwhelmed by the amount of information and steps required before they can use the product. The onboarding flow asks for too much upfront -- profile details, team setup, integrations, preferences -- before users have experienced any value. This creates a wall between sign-up and the "aha moment".
Who experiences this problem?
Every new user who signs up for the first time, but especially individual contributors (designers and developers) who are evaluating the tool on their own before recommending it to their team. These users have low patience and high expectations -- they want to see value within the first 2 minutes.
When does it happen?
Immediately after account creation. The user lands on a multi-step setup wizard that feels like a tax form. They are asked to fill in their job title, upload an avatar, invite team members, connect integrations, and set notification preferences -- all before they have seen a single feature of the product.
Problem Clarity
Understand what the user is trying to accomplish
What is the user trying to accomplish?
The user wants to quickly understand what this product does and whether it solves their problem. They want to see the core interface, try a key action, and decide if it is worth investing more time. They are not ready to commit to full setup yet.
If your design could only do ONE thing well, what would it be?
Get the user to their first meaningful interaction with the product as fast as possible. Everything else -- team setup, integrations, profile -- is secondary and can happen later when the user has context and motivation.
What exactly is the user struggling with right now?
Users are struggling with decision fatigue and a lack of context. They are asked to make choices (like which integrations to connect) before they understand how those integrations will be used. They are also frustrated by mandatory fields that feel irrelevant at this stage.
User & Context
Features don't exist in isolation
Who is the primary user for this feature (not the product)?
Individual contributors evaluating the tool solo -- typically mid-level designers or frontend developers who found the product through a blog post, recommendation, or Product Hunt. They are trying it during a break or after work hours and have about 5 minutes of attention to give.
What's the job they're trying to finish when this feature appears?
They are trying to evaluate whether this tool will help them organize and reflect on their design decisions better than their current process (which is usually scattered notes in Notion or no process at all).
Product Intent & Leverage
Why this feature exists for this product
How does this feature reinforce the product's core value?
The product is about thoughtful design reflection. A bloated onboarding experience contradicts that core value. By making onboarding itself a well-designed, respectful experience, we demonstrate the product philosophy before the user even starts using it.
If we removed this feature later, would users revolt or barely notice?
Users would immediately notice. The current onboarding is the first thing they see, and if we reverted to the 7-step wall, we would see drop-off rates spike back to 62% or higher. The streamlined flow is not a nice-to-have -- it is the front door.
Success Definition
If you can't measure it, you're guessing
What user behaviour should change if this works?
Users should complete onboarding and create their first diary entry within the first session, instead of abandoning during setup. We should also see more users returning for a second session within 48 hours because they actually experienced the product.
What does "success" look like in one week? One month?
One week: Onboarding completion rate above 70%. One month: Second-session return rate increases by 25%. We also track time-to-first-entry as a key metric -- target is under 3 minutes from sign-up.
What metric moves because of this feature?
Onboarding completion rate (from 38% to 70%+), time-to-first-entry (from 8 minutes average to under 3), and 7-day retention (expecting a 15-20% lift from users who actually experience the product).
Constraints & Trade-offs
Designing is choosing what not to do
What constraints are you working within?
Engineering capacity is limited -- we have 2 frontend developers for 3 weeks. The backend team cannot change the user model or auth flow. We also need to maintain backwards compatibility for existing users who have already completed onboarding. Legal requires us to keep the terms acceptance step.
What design debt might this create?
By deferring profile completion and team setup, we will need to build contextual prompts throughout the app to collect this information later. This creates multiple touchpoints that all need to be designed and maintained. We are trading one complex flow for several smaller ones.
Discoverability & Learning
A feature unused is a bug
How will users discover this at the right moment?
This is the first thing users see after sign-up, so discoverability is not an issue. The challenge is more about pacing -- making sure each step feels lightweight and the skip option is visible but not the default path.
How will they understand it without reading?
Each step uses a large illustration, a single question, and 2-3 clickable options. No paragraph text, no tooltips needed. The progress bar at the top shows exactly where they are. The skip link is subtle but always present in the bottom-left corner.
Pre-Mortem
Imagine your design failed
What went wrong?
The simplified onboarding gets users in faster but they arrive at the main interface without enough context. They create a diary entry but do not understand the Research section, so they leave it blank and never return. We optimised for speed but sacrificed comprehension -- the aha moment never actually lands because users skipped the context that would have made it meaningful.
Want to create your own design diary entries?