Tempahly

The Real Problem

Every salon on Tempahly ran its day the same way: a WhatsApp thread full of booking requests, and a paper diary at the front desk that was the real source of truth. When the two disagreed — and every weekend, they did — two customers arrived for one chair. Double-bookings weren't a bug; they were a Saturday tradition.

Deposits were the quieter problem. Asking a customer for money mid-chat felt rude, so most owners simply didn't. No deposit meant no commitment, and the no-show column in the diary kept growing.

The software already existed — the salons had accounts. They just didn't use them, because the booking calendar was organised like a database and the diary was organised like a salon.

Finding the Fix

I sat with owners and stylists to watch how a booking actually happens, and the pattern was consistent: nobody thinks in time slots. Everyone thinks in stylists. "Is my usual stylist free at three?" The paper diary had a column per stylist for a reason.

So the redesign followed the diary, not the org chart: a calendar rebuilt around stylist columns, and deposit links folded into the booking confirmation flow — so the system asks for the money, and the owner never has to.

What Actually Happened

The first calendar I proposed looked cleaner than the paper diary — and tested worse. The diary was trusted; a fresh grid was not. So we imported the diary's look almost literally, columns and all, and the fear of migrating melted away.

Stylists supplied the second correction: mid-blow-dry, nobody reads a paragraph. Every screen got cut down to what you can absorb in a glance — who's next, when, paid or not. Anything longer than that went.

What Changed

No-shows fell 62% once a deposit became a link instead of an awkward conversation. Double-bookings dropped to basically zero. But the signal I trust most isn't a number: owners started showing the calendar to other salon owners, unprompted.

What I Had to Work With

Fourteen weeks, three engineers, one PM — and two hard human constraints. Stylists who physically cannot read long screens mid-blow-dry, which made "glanceable" a requirement rather than a preference. And owners whose trust lived in a paper book, which made the diary the design brief, not the competition.

What I'd Do Differently

Start at the front desk sooner. We spent early weeks polishing flows before I properly understood the diary's column-per-stylist logic — one afternoon of watching would have got us there faster. And I'd bring stylists into testing from day one, not just owners; they caught entirely different problems.

What I Learned

Adoption is a design problem, not a training problem. These salons never needed a tutorial — they needed software shaped like the tool they already trusted. When the new thing looks like the old thing and quietly does more, nobody has to be convinced.

This is sample content for portfolio purposes — the projects on this page are fictional placeholders.