| # | Location | Description | Severity | Frequency | Evaluator Quote |
|---|---|---|---|---|---|
| F-01 | Workspace Setup | Required "workspace URL" field uses an unfamiliar slug format with no explanation or example. 4 of 6 evaluators paused here for 30+ seconds. 1 abandoned. | Critical | I don't know what a workspace URL is supposed to be. Is this my company name? A website? | |
| F-02 | Email Verification | Verification email takes 2–4 minutes to arrive with no indication of expected wait time on the confirmation screen. 1 evaluator assumed the process had failed and re-registered. | Critical | Nothing is happening. Did it send? I'm going to try signing up again. | |
| F-03 | Workspace Setup | "Plan type" selector appears mid-setup before any product value has been shown. Evaluators felt they were being asked to commit before understanding what they were buying. | High | Why do I have to pick a plan now? I haven't even seen the product yet. | |
| F-04 | Invite Team Members | Skipping the invite step is possible but the "Skip for now" link is visually de-emphasised to near invisibility. 3 evaluators spent time trying to fabricate email addresses rather than skipping. | High | I'm not going to invite anyone right now but I can't figure out how to move on without doing it. | |
| F-05 | Account Creation | Password requirements not shown until submission failure. Evaluators had to guess the rules after an error appeared. | High | It just says "invalid password." I have no idea what it wants from me. | |
| F-06 | Workspace Setup | Progress indicator shows 4 steps but setup actually takes 7 screens. Evaluators felt misled once the step count was exceeded. | High | It said step 4 of 4 like two screens ago. How long is this? | |
| F-07 | Create First Project | "Project type" dropdown has 14 options with no descriptions. Non-technical evaluators could not determine the difference between "Scrum," "Kanban," and "Agile" options. | Medium | What's the difference between these? I'll just pick the first one and hope for the best. | |
| F-08 | Account Creation | No social sign-in or SSO option on the sign-up form. Two evaluators specifically looked for Google sign-in before filling in the form manually. | Medium | I always use Google login for things like this. Having to create yet another password is annoying. | |
| F-09 | Workspace Setup | Timezone selector defaults to UTC with no auto-detection. All evaluators had to manually search for their timezone. | Medium | Why doesn't it just know my timezone? Every other app does this automatically. | |
| F-10 | Create First Project | "Start date" field requires a specific date format (YYYY-MM-DD) not shown as placeholder text. Most evaluators entered MM/DD/YYYY and received a silent validation failure. | Low | Why didn't it tell me what format it wanted? I just had to figure it out by trial and error. | |
| F-11 | Invite Team Members | Success confirmation after project creation is a small toast notification that disappears in 2 seconds. Several evaluators weren't sure if their project had actually been saved. | Low | Did that save? I'm not sure if it worked. I don't see it anywhere. |
This single field caused the most confusion of any element in the flow and directly caused one abandonment. Add a placeholder like "e.g. acme-corp" and a one-line explanation beneath the field: "This is your team's unique address in Claritask. You can change it later." This is a 30-minute fix with outsized impact.
The verification screen should tell users to expect a 2–5 minute delay and display a countdown or progress indicator. A visible "Resend email" button prevents users from assuming failure and re-registering, which creates duplicate accounts and drops the user from the flow.
Asking users to choose a plan before they have experienced the product creates friction and distrust. Move the plan selection prompt to after the first project is successfully created, or offer a default "free trial" that bypasses the decision entirely during onboarding. This is a structural change but directly addresses the most-cited source of negative sentiment.
The invite step should be visually optional from the start. Elevate the skip action to a secondary button with clear label. Users who are evaluating the product solo shouldn't feel forced to fabricate team data to proceed.
Two quick wins that reduce unnecessary friction. Display password rules as inline helper text beneath the password field. Auto-detect timezone using the browser API and pre-populate the field — let users override if needed. Both changes are low effort and address issues that affected the majority of the panel.