Cynthia works CNA shifts and raises a kid on her own. The last thing she can spare is an evening lost to a broken sign-up form, but that's exactly what KARE Hero's onboarding was asking of her: a single-page form requesting a license, a resume, tax documents, and background-check consent all at once, before she'd even seen a shift she could work.
This case study is about one decision: replacing that form with a guided, step-by-step onboarding wizard.
I worked on KARE Hero as a Senior User Experience Designer & Product Designer at KARE Technologies, leading the research, strategy, and design behind the onboarding decision covered in this case study: replacing the single-page sign-up form with a guided, multi-step wizard.
The team was small: a junior designer, a five-person development team, a product owner, and one business stakeholder, across the roughly year-long span from early research to the wizard's launch.
This is what a hero actually saw in production: one screen asked for license type, state, and SSN, plus a license number and expiration date, all at once.
A second, separate screen worked like a checklist gating resume, tax forms, terms and conditions, primary market, and banking details, all before a hero could so much as look at an open shift. Nothing on screen explained why a document was needed, and nothing showed how many steps were left.
Google Analytics flagged the 48% drop-off, and HotJar heatmaps pointed to the exact spot: the SSN field, where engagement dropped off hard inside the license screen. That's what made this form, specifically, the target of the redesign.
The license screen in production: six fields and an optional photo, with no signal of where this step fit within sign-up.
The checklist screen: seven requirements stacked behind an asterisk, with two more greyed out waiting their turn, no indication of which came first or why.
Research centered on two personas built from real interviews with medical staff and platform users: Cynthia Morgan, a CNA caregiver and single mother, and Tom Bennett, a registered nurse working toward becoming a therapist. Both pointed at the same friction point, independently.
Cynthia's frustration: "too much time being wasted throughout a difficult onboarding process that involves endless phone calls." Tom's: "unorganized shift schedulers, lack of clarification during the process, and overwhelming information."
The journey map's "Wait" stage: users expected confirmation quickly, but review time varied for anyone new to the platform, with no visibility into which case they were in.
Raw findings clustered directly under "Onboarding apply": easy onboarding, visual queue indicators, clear documentation, a fast way to upload extras.
KARE Hero's registration was a single long form: personal details, license number, resume, tax forms, background-check consent, all on one screen, with no sense of progress. I had two paths on the table. Patch the existing form: trim fields, add inline validation, ship it fast. Or rebuild registration entirely as a multi-step wizard: slower to build, but able to collect information progressively and show a hero exactly where they stood.
The wireframes that backed the "build" call: low-fidelity sketches of the full wizard before a single line of production code was written, the evidence that the engineering cost was real but manageable.
I chose the wizard. Below is the guided flow that replaced the single-screen form you saw above, sign-up through the moment a brand-new hero is cleared to apply for their first shift.






Every step carries the same progress bar and a plain-language reason for the request: the two things the old single form never gave a hero.
The license step almost shipped assuming everyone filling it out already had a license in hand. They didn't: some heroes apply on a contingent offer while they're still getting one, and some roles don't require one at all. The first applicants found this out on their screening call, late in the process, and were understandably annoyed. The fix was a checkbox right on that step, to flag not having a license yet without derailing the rest of sign-up.
I tested the shipped wizard with heroes going through onboarding for real, to see whether the stepper actually fixed what the old form couldn't.
As a native iOS and Android app, every wizard screen was checked against each platform's own conventions rather than a single cross-platform mockup. The underlying design tokens still followed a Tailwind-style naming convention for consistency across the design file.
Once onboarding is complete, a hero lands directly in shift search, the reason they signed up in the first place. What's below is a short look at that handoff, not a separate case study of the search-and-apply experience itself.
Search, filtered by date and rate, with map and list views: the core loop the whole onboarding decision existed to protect.
Tapping a result opens the full shift detail: estimated pay, schedule, location, and the community's own ratings, before a hero ever has to apply.
Once worked, that same shift shows check-in and check-out time alongside the exact pay breakdown, so a hero never has to guess what they're owed.
Rebuilding onboarding as a guided wizard was the more expensive path to build, and the one that actually addressed why heroes were dropping off. Progressive disclosure and a visible stepper gave people a reason to keep going: they could see exactly how close they were to being done.
“His expertise in translating product requirements and ideas into simplified workflows, high fidelity mockups, and prototypes is truly exceptional.”