Shipping a foundational change by right-sizing design scope
Book4Time was the cloud leader in enterprise spa management, running on a twenty-year-old front end that still sliced images into parts. Design wanted to restructure it. I took the smallest of three options, because the real risk wasn’t the interface. It was retraining every Four Seasons and Hilton property mid-contract.
- Role and Team
- Daniel – Design and product leader
- Zamir Visram – Product designer
- Timeline
- 2019–2020
- Platform
- Staff-facing enterprise web app
The problem
Book4Time ran the spas at Four Seasons, Hilton, Marriott and Equinox. It was the cloud leader in a category whose competitors were still selling on-premises software. The application didn’t say any of that. It looked like the thing it had beaten, which undercut both the premium brands it served and the modern-cloud story sales told.
Underneath was twenty years of accretion on a fractured stack: a front end still assembling pages by slicing images into parts. Every view had drifted from every other, so moving between them meant relearning where things were, and icons and type had been sized for a screen nobody used any more.
Three options, and a decision we could point to
Leadership agreed on the direction, but it was fuzzy and undocumented: two founders with a lot on, who hadn’t examined the scope closely. Rather than proceed on assumed alignment, I put up three real options and their tradeoffs: restructure the primary flows to cut views; reorganize existing pages while keeping their content; or reskin, leaving every component in place.
The meeting sharpened it. We landed on the UI-level changes with the reasoning attached: the surface’s size, the team, and customers whose change-management processes governed rollout. “A coat of paint” became the shorthand Zamir, engineering and I used for what we were and weren’t touching.
Baseline
UI Refresh
UX Redesign
The constraint became the brief
With structure off the table, the visual pass had to carry the experience wins on its own. Consistency was the first: one treatment for the same control everywhere, so moving view to view stopped costing attention. Legibility was the second, and it wasn’t cosmetic. Front-desk staff working on tablets had been asking for bigger targets to check guests in and out.
The promise we made to customers in the release was the scope decision stated plainly: every screen, button and action stays in the same familiar place, and the color does the work of making them easier to find.
Before
After
A design language, not a coat of paint
What leadership had authorized as a reskin, we built as a system. The style guide standardized components across the core application and the new booking product together, so the two surfaces stopped diverging and engineering had one specification to implement against.
That was the part worth the most later. Consistency isn’t only a user-facing win; it’s what makes the next change cheap.
What shipped, and what it made possible
The refresh shipped in July 2020 across the whole surface, with advance notice at the support team’s request. The bar I’d set with the founders was simple: nobody should have to relearn the product. The release note could say so without hedging. Every screen, button and action stayed in the same familiar place.
The app finally read like the market position it held, and internally its appearance stopped coming up as a reason deals stalled. What outlasted it was the system underneath: one component specification spanning the core app and the new booking product, making the structural pass we deferred cheaper for whoever takes it.