
Homebase
Making it easy for 3.5M+ hourly workers to share when they can’t work.
Role
Product Designer
Context
Internship
Timeline
May - Dec 2026
Tools
Problem
Employees couldn't enter their true availability using just the app.
Due to limitations in our current availability model, employee availability requests repeated weekly with no end date.
Class schedules, other jobs, and one-off changes were more easily communicated outside of Homebase.
The majority of availability updates typically happened over text, email, or in-person conversations, meaning the availability saved in the app was often out of date.
My Role
I owned the availability redesign end to end, from initial research to eng handoff.
Background Research
Every scheduling app I studied asked for days and times first, which isn’t how employees think about availability.
These days-and-times forms work, but our testing showed they didn’t match how employees generally think about when they can and can’t work.
7shifts
Deputy
When I Work
Gusto
Initial Insight
One availability request could be hiding several reasons, each with its own cadence and end date.
Employees had to put every commitment into one availability request, but each reason they couldn’t work had its own end date or recurrence, which our existing system couldn’t capture.
A single weekly schedule could hide several commitments (old UI).
Iterations
The availability form went through four major revisions, with each round of changes informed by user research.
I tested every version before starting the next one, with teammates, customers or employees depending on the round.
Final Design
The form starts by asking why you can’t work, then builds the request around your answer.
Splitting requests into one entry per reason is a new way of thinking about availability in Homebase, so the form has to work for active employees who are used to putting every reason they can’t work into a single request. To teach one request per reason, the form opens on a single question, “Why can’t you work?”, and builds the request around that one reason.
Validation
A final usability test settled the last few open decisions about the form.
In addition to presenting prototypes at design crits, I ran a usability test with several members of Homebase’s internal CX and Growth teams (who were great proxies for customers), and built the final form around those findings.
Success Metrics
More employees with availability in the app, and updating their availability there instead of over text.
Of the millions of employees with a shift in the last 90 days, about 1 in 4 had set their availability, and about 1 in 7 edited their availability in that time. Twelve months after launch, we’re aiming for:
27% → 35%
of scheduled employees with availability on file
14% → 20%
of scheduled employees with updated or confirmed availability in the last 90 days
Reliable availability is also a prerequisite for unlocking Homebase Assistant!
To support future agentic scheduling tooling, we’ll need reliable employee availability. The new availability design empowers employees to say something like “My class on Tuesday got canceled, let my manager know I can work,” and the assistant could find the Classes entry, mark Tuesday available and tell their manager, all in one go.
Reflection
Availability is a surprisingly complex surface.
Exploring ideas in Figma and Claude Code made changes cheap to test, which left more time for choosing the “right” option and making the inputs clear enough that a 16-year-old working at an ice cream shop could understand them.











