StaffPoint: redesigning a healthcare scheduling platform

The product is under NDA, so this project has no screenshots. The illustrations are mine and show the structure of the problems, not StaffPoint's interface.

StaffPoint is scheduling software for hospitals, care facilities and other businesses that run on shifts: a shift calendar, staff suggestions, automatic calls and texts, attendance tracking and billing in one system. From April 2024 to March 2026 I was its only product designer, part-time, working with the owner and the developers.

Schedulers open StaffPoint at the start of the day and keep it open until the end. Many had used the same screens for years. They didn't need a new look, they needed less friction in the work they already did. Every change had to feel familiar on day one.

The red, blue and green colour code for open, booked and completed shifts stayed. It looks dated, but it's the fastest way to scan a week of shifts and every user already knew it. Replacing it would have made the product look newer and work slower.

Existing clients needed the tool to work better. New clients needed to see what it could become before they signed. I worked at two speeds: careful, gradual changes for people using the product every day, and fast clickable prototypes for sales demos. A prototype that helps close a sale is a design deliverable too.

For the staff view on mobile I designed three layouts for the same list of open shifts, each with a short note on what it gains and what it costs, so the choice was made with the reasons in front of everyone, not on taste.

I kept a component set in Figma, so developers could build each screen from parts they had already built once. Work was often interrupted by new client requests, and shared components meant the parts that did ship still looked and behaved like each other.

Partly shipped. The assignment details repository, released in early 2025, is one of my designs that went live. Others were handed off and are waiting to be built: StaffPoint paused product development in March 2026.

The full case study is on danielpetrevski.com.