Photo collage of three KARE Hero caregivers wearing "Do You KARE" shirts, with a banner reading Earn Extra Income, Flexible Schedule, Get Paid with HERO Real-Time Pay
Case Study: Healthcare Staffing / Mobile App

The Form That Was Losing KARE Hero's Nurses

15%
Increase in user registrations after the wizard shipped
20%
Reduction in time-on-site during sign-up
Lower
Cognitive load, replacing one dense form with visible step-by-step progress
KARE Hero app welcome screen
KARE Hero shift search screen listing available healthcare shifts with pay rates, including Floor Nurse and Medication Aide roles

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.

That form was dropping an estimated 48% of new users before they ever saw a shift, per analytics at the time. The real question was whether a guided wizard was worth the engineering cost of rebuilding the flow from scratch.
RoleSenior User Experience Designer & Product Designer
CompanyKARE Technologies
ClientKARE Hero
Team1 junior designer, 5 developers, 1 product owner, 1 stakeholder
Duration1 year (2023–2024)

My Role

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.

Focus: Form-to-Wizard Redesign · Tools: Figma, LucidChart, Hotjar, Google Analytics · Accessibility: WCAG 2.1 Audit

A single form asking for everything at once

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.

What shipped

  • License type, state, and SSN collected on one screen, with no explanation of how the SSN would be used
  • A second checklist-style screen gating resume, documents, tax form, terms, and bank info, all before background check or drug testing would even unlock
  • No progress indicator on either screen

Why it mattered

  • A CNA raising a kid alone couldn't spare an evening on a form that never showed how close she was to done
  • Every required document was regulatory, not optional, but the form never said which state requirement each one satisfied
  • A hero who dropped off mid-form had no shift to show for the time already spent
  • Analytics at the time estimated 48% of new users dropped off somewhere in this flow, before ever seeing a single shift
  • A confusing first form reads as a red flag on a platform asking for a Social Security number, and there was only one shot to earn that trust
Old KARE Hero license information form asking for license type, state, SSN, license number, expiration date, and photo all on one screen

The license screen in production: six fields and an optional photo, with no signal of where this step fit within sign-up.

Old KARE Hero document checklist screen listing Personal Information, Resume, Documents, Tax Form, Terms and Conditions, Primary Market, and Bank as required, with Background Check and Drug Testing greyed out

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.

Two heroes, one shared complaint

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.

KARE Hero user personas: Cynthia Morgan and Tom Bennett

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."

Customer journey map showing the Wait stage after applying to a shift

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.

Affinity map cluster: onboarding and apply pain points

Raw findings clustered directly under "Onboarding apply": easy onboarding, visual queue indicators, clear documentation, a fast way to upload extras.

A guided wizard, or patch the form?

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.

Patch the form

  • Days of engineering work, not months
  • No new navigation pattern for users to learn
  • Doesn't fix the core problem: still one long wall of fields
  • No visible progress, no reason for a half-finished user to come back

Build the wizard

  • A visible stepper turns "how much is left" into a known quantity
  • Each screen asks for one category of information, with a reason attached
  • A natural place to add "finish later" without losing progress
  • Real engineering cost: five new screens, new state to manage between them
Low-fidelity wireframes of the proposed wizard: enter license information, uploading documents, add experiences, resume builder, message support, and a completion screen

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.

From one form to five honest steps

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.

The five-step flow: sign-up through cleared-to-work
Sign up screen with photo, name, email, and password fields
Sign up
Personal information step with address and identity fields
Personal information
License verification step, empty, with explanation text
License verification
License verification step, filled, ready to submit
Ready for review
License submitted confirmation screen
License submitted
Interview scheduling step with KARE team
Interview scheduled

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.

Shipped: a last-minute catch

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.

License verification step with an "I do not own a License Number" checkbox, checked
The checkbox that lets someone flag they don't have a license number yet
Heads up disclaimer modal: without a license, applicants can only apply to contingent offers and unlicensed roles like Home Health Aide or Nursing Assistant
The disclaimer it triggers: what's still available without a license, before they submit
View interactive prototype in Figma →

What testing showed once it shipped

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.

What worked

  • The stepper gave them confidence: they always knew exactly where they stood
  • The visible progress bar made the process feel clear and well explained

What didn't

  • No clear next step for someone mid-process of getting their license; the flow just said someone would call them
  • Hesitation about handing over a Social Security number this early
  • "Finish later" didn't actually save progress; some heroes had to start over

Built native, tokens borrowed from the web

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.

Platform guidelines

  • iOS builds follow Apple's Human Interface Guidelines for navigation, spacing, and native form controls
  • Android builds follow Material 3: dynamic color, elevation, and component behavior native to the platform
  • Progress steppers, buttons, and form fields were validated on both platforms rather than assumed to look identical

Design tokens

  • Color, spacing, and type scales named and structured the way Tailwind CSS organizes its utility classes
  • A shared naming convention made tokens easy to hand off to developers on both platforms
  • Kept the visual language consistent even where iOS and Android components render differently

What a cleared hero sees next

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.

KARE Hero shift search results in list view

Search, filtered by date and rate, with map and list views: the core loop the whole onboarding decision existed to protect.

Shift detail screen for a Floor Nurse shift at Florida Healthcare Plus, showing estimated pay, schedule, address, the poster's contact card, and the community's HEART Score and ratings

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.

Shift Details tab for a completed shift, showing check-in and check-out time, total net hours, net rate, and total pay

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.

15% increase in user registrations.

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.

Clearer
Visible progress at every step, instead of one long form
Honest
Every document request paired with a plain-language reason
Native
iOS and Android builds validated against each platform's own guidelines

“His expertise in translating product requirements and ideas into simplified workflows, high fidelity mockups, and prototypes is truly exceptional.”

Lindsay Evans , VP of Product, KARE
The wizard fixed how it felt to be inside the form: heroes always knew exactly where they stood. It didn't fix what happens the moment they leave it. Once a license went into review, the same wait-and-wonder returned, just relocated to a step the design never touched. A progress bar can only cover the part of the process it's actually watching.
Next case study
Ashley Furniture