Web platform — Planner and admin experience
Where the mobile app serves one employee doing one thing, the web platform serves the people who run the office: facility managers and executive assistants booking on behalf of others, and administrators configuring the system everyone else uses.
The product had grown service by service — rooms, catering, parking and visitors each with their own screens, controls and way of setting permissions. I redesigned the planner experience around the day a coordinator is assembling, and rebuilt the admin console so every resource type is managed through one consistent pattern.
A day, not a series of bookings. The planner brings rooms, bookings and catering into one view, so an assistant arranging a meeting with lunch and guests verifies the whole thing in one place instead of across four screens.
Delegated booking as the primary path. For an executive assistant this isn’t a variant of personal booking — it’s the only mode they use, so it was designed as the main flow rather than a checkbox on someone else’s.
One pattern, four resource types. Desks, rooms, parking bays and catering items differ in properties but share a structure. One create-and-manage pattern with type-specific fields, instead of four separate sections to learn.
Roles defined once, not per module. Permissions had been set inside each module separately. Consolidated so an admin defines a role once and sees everything it reaches.
Bulk setup as the default. Onboarding a customer means creating desks across multiple floors. The previous console created them one at a time.