Barber-OS Platform Redesign for Optimal Usability

Quick Context Barber-OS had a working prototype that confused everyone. Beta testers said they'd rather stick with paper appointment books than figure out the clunky system. As the sole designer on a dev-heavy team, I had to redesign the foundation while building 19 new features—without direct user access and with a rigid component library.

Restructured the chaos Worked with barbershop industry experts to understand real workflows, audited competitors, and reorganized a flat, overwhelming navigation into a 2-level system that actually made sense.

Solved impossibly complex booking logic Designed group appointment flows that handled multiple clients, multiple services, and multiple staff without making users' heads explode. Prioritized the majority use case (service → staff → time) based on how people actually think about haircuts, while building in flexibility for edge cases.

Connected features to match real operations Added walk-in client options for busy periods, quick-create flows from appointment scheduling, unified calendar views—small workflow connections that removed daily friction for barbershop staff.

Navigated constant technical pushback Engineering often said "we can't do that." I learned to propose solutions within the existing component system, making strategic tradeoffs between ideal and achievable without sacrificing usability.

The Result Platform went from "too complicated, I'll just use my appointment book" to 10+ barbershops running their entire business on it. That shift from resistance to daily operational use was the win.

What I Learned How to make strategic product decisions with limited user access, prioritize majority use cases over perfect solutions, and design complex system logic (permissions, multi-location, group bookings) that balances flexibility with simplicity.