Helping Healthcare Clinicians Compare and Manage Per-Diem Shifts
BravoCare is a marketplace that connects healthcare clinicians with facilities offering on-demand shifts.
I designed and tested a high-fidelity clinician experience for finding shifts, submitting hourly-rate bids, reviewing facility information, and managing upcoming work.
DELIVERABLE
Usability testing completed, with iteration and development handoff identified as next steps
Please note that certain details and information have been omitted or altered to protect the privacy and confidentiality of the organizations involved.*
THE CHALLENGE
BravoCare supports three groups with different responsibilities. This phase focused on clinicians. They needed to compare opportunities, submit bids, apply for shifts, and manage upcoming work while keeping important details about pay, commute, timing, and facilities within reach.
Healthcare Facilities
Managing staff, reports, and administrative tasks
Clinicians
Finding, applying, and managing shifts
PROJECT FOCUS
BravoCare internal team
Supporting both sides of the marketplace
UNDERSTANDING THE WORKFLOW
Ground the Experience in
Existing Knowledge and Direct Input
BravoCare provided foundational research and knowledge gathered through its daily contact with members. The project team also interviewed nurses already using the platform to validate its working assumptions.
I translated the available evidence into task and user flows mapping how clinicians moved between available shifts, facility information, bid submission, applied shifts, and booked work. These flows established what information clinicians needed at each stage and how the screens should connect.
EVIDENCE INFORMING THE JOURNEY
Existing research supplied by BravoCare
Knowledge from daily member support
Interviews with clinician nurses using the platform
Clinician task and user flows
CLINICIAN SHIFT JOURNEY
01
Available Shifts
compare opportunities
02
Shift Details
review facility and shift details
03
Apply and Bid for Shift
bid the hourly rate
if booked
04
Booked Shifts
manage upcoming shifts
Comparing available shifts
Design for Different Shift Priorities
Testing showed that pay rate and commute distance were central to how participants evaluated opportunities, but the weight they gave each factor varied. One participant placed greater value on compensation, while another prioritized the commute.
The experience therefore needed to make both factors easy to find without assuming that every clinician evaluated a shift in the same order.

COMPARING BOOKED-SHIFT LAYOUTS
The results revealed a tradeoff rather than a clear winner. The case study shows the evidence without claiming a final direction was selected.
Condensed Calendar
3 of 5 preferred a simpler, familiar calendar layout

Clinicians familiar with the facility only needed its name and the shift time in the weekly view, and participants recognized the familiar email-calendar pattern.
Detailed Layout
2 of 5 preferred to see more context at a glance

Clinicians unfamiliar with a facility valued seeing more essential shift information at a glance without opening each shift.
THE TESTED EXPERIENCE
Using BravoCare’s existing component library, I connected shift discovery, bidding, application, and booked-work management into one consistent, testable clinician journey that could be evaluated before development.
01
Browse and Review Available Shifts

02
Apply and submit Hourly rate

03
Manage booked Shifts

Validation and next steps
Five usability sessions with current BravoCare clinicians clarified how they compared opportunities and revealed different preferences for reviewing booked work.
next steps
Prepare the updated designs for development handoff
Begin addressing the other user groups
REFLECTION
Clinicians could complete the same workflow while prioritizing different information. Making pay, commute, timing, and facility details easy to compare was more useful than imposing one fixed decision hierarchy.
The project also reinforced the value of testing competing layouts when users need different levels of context.
OTHER CASE STUDIES



