pulse

Unifying shift scheduling, payroll, and recruitment for healthcare staffing

This case study reflects a real product I designed professionally. To respect client confidentiality, the name, branding, and interfaces shown here have been recreated independently and do not represent the actual shipped product.

YEAR

2025

TIMEFRAME

6 Months

CATEGORY

Product Design

TEAM

1 Product Manager,4 Developers

PROBLEM

Healthcare staffing runs on people showing up to the right shift, at the right facility, on time - but the tools managing that were never built to talk to each other. Scheduling lived in one system, payroll in another, recruitment somewhere else entirely. Managers were stitching

RESEARCH & DISCOVERY

The starting point wasn't a blank page - it was a system already carrying years of operational logic that had never been designed, only accumulated. Before any screens, the work was mapping how shifts, staff, and payroll actually moved through the business today: sitting with the people who filled shift gaps by hand, walking through how a manager currently confirmed someone was qualified, available, and going to show up, and cataloguing every place that confidence broke down. That process surfaced a few things worth designing around directly: "Available" and "reliable" are different questions. A manager didn't just need to know who was free - they needed to know who tended to cancel, who communicated well, who was new enough to need extra check-ins. None of that lived anywhere structured; it lived in individual managers' memory. A shift's staffing state matters more than a headcount. "3 of 4 filled" isn't reassuring the way "4 of 4" is - a partially staffed shift needed to be visibly, urgently different from both a fully open one and a fully filled one. The fallback path was the actual pain point. Most shifts filled fine. The ones that didn't - where no internal staff were available - were where managers lost the most time, because "then what?" wasn't a designed path, it was a phone call to recruitment. Automation needed an off switch. Smart suggestions and auto-fill were wanted, but not trusted blindly - compliance-sensitive shifts needed a human to stay in the loop.

DESIGN PROCESS

The single structural change everything else follows from: the shift became the central object, not the schedule. Previously, scheduling, staffing status, and payroll were three separate systems a manager had to reconcile by hand. The redesign made an individual shift carry its own full lifecycle - Open → Partially Staffed → Filled → In Progress → Completed - and attached everything relevant (assigned staff, timesheet, payslip trigger) directly to that object instead of to three disconnected tools. The part that mattered most in practice: when a shift couldn't be filled internally, that wasn't a dead end - it became a defined branch into recruitment, with the shift itself tracking that it was now sourcing externally, and looping back the moment someone was hired. Before, that handoff didn't formally exist; it was a manager remembering to make a call.

FINAL SOLUTION

01

Operations dashboard

A unified operations dashboard that gives managers real-time visibility into workforce health, shift fulfillment, staffing risks, payroll, and scheduling—enabling faster, data-driven operational decisions.

02

Shift monitoring

Shift monitoring table for triaging attention, priority, staff coverage, and confirmation status across upcoming hospital shifts.

03

Create shift flow

Create-shift flow that keeps requirements, timing, department, location, staffing needs, and notes in one focused workspace.

04

Assign staff workspace

Staff assignment workspace for reviewing availability, fit, workload, and ratings before confirming the right team member.

05

Review and confirmation

Review and confirmation screen that summarizes role, time, location, staffing requirements, notes, and assigned staff before publishing.

06

Recruitment overview

Recruitment overview that surfaces pipeline health, pending roles, completion bands, onboarding counts, and application activity.

07

Candidate list

Candidate list view for tracking role, region, progress, stage, assigned recruiter, and next actions across applicants.

DESIGN DECISIONS WORTH CALLING OUT

• I used specific behavior tags (frequently cancels, strong communicator, new starter) instead of a single reliability score, because a manager filling an urgent gap needs to know why someone is a risk, not just that they scored low — "cancels often" and "hard to reach" call for different decisions. • I made auto-fill an offered suggestion, not a default action, because compliance-sensitive staffing (qualifications, hours worked, registration status) needed a manager to stay accountable for who actually got booked — automation could recommend, but shouldn't get to decide alone. • I gave "Partially Staffed" its own explicit state instead of treating staffing as filled/unfilled, because a shift with 3 of 4 people is a fundamentally different, more urgent thing to a manager than a fully open one, and collapsing them into one status hid that urgency.

OUTCOMES & IMPACT

The dispatch model - route-based jobs, a capacity-aware assignment view, automatic rerouting of out-of-stock orders, and exception alerts - made up the core scope. Driver-facing extras like per-delivery earnings, commission tracking, and salary views were deliberately held back for a later phase so the dispatch core could come first.

KEY TAKEAWAYS

The hardest tension in this project wasn't a screen, it was a trust question: how much should the system decide versus surface and let a person decide? Every automation opportunity - auto-fill, smart suggestions, tagging - ran into the same wall, that healthcare staffing carries real compliance weight, and a manager who's accountable for who shows up needed to feel like the system was making their judgment faster, not replacing it. I'd want to talk about where I think that line landed right, and at least one place I'd push it differently with what I know now.

CHALLENGES

CHALLENGES

CHALLENGES

Designing for things going wrong: no stock at the main warehouse, a driver who never starts, a missed express window, or a delivery that can’t be confirmed by OTP.

FUTURE OPPURTUNITIES

FUTURE OPPURTUNITIES

FUTURE OPPURTUNITIES

  • Driver-facing views for earnings per delivery, commission and targets.

  • Smarter assignment that suggests jobs from route, load and due time.

SAY HELLO

i'm open for freelance projects, feel free to email me to see how can we collaborate

SAY HELLO

i'm open for freelance projects, feel free to email me to see how can we collaborate

Made with ❤️ by Vaisakh

Made with ❤️ by Vaisakh

Create a free website with Framer, the website builder loved by startups, designers and agencies.