overview
Turning a low-adoption seat booking tool into a daily workflow
This project is an internal hoteling platform for a large global law firm. I led UX direction (user flows, information architecture, MVP scope) and implemented core UI components on web; later I drove a mobile redesign focused on usability and maintainability.
I partnered with a visual/UI designer, but spearheaded overall UX strategy and decision-making. My role was to challenge requirements, question assumptions, and shape solutions that balanced user needs, technical feasibility, and organizational constraints.
Role
UX programmer • UX direction + front-end implementation
Platforms
Web (ASP.NET Core MVC) • Mobile (.NET MAUI) • Telerik UI
Impact
Adoption grew from 50% to ~90% (department-reported)
problem
The tool created friction, confusion, and scope creep
The original experience was a simple “map + dropdown” with limited booking rules and weak information scent. Product feedback was driven primarily by seniority rather than usage data, which inflated complexity and introduced dead-end navigation for many users.
Key UX failure mode
Navigation exposed features users could not access (e.g. “Share Your Office”), punishing exploration and training users to stop clicking altogether.
Later usage data and mobile analytics confirmed that these access-gated features were rarely used, reinforcing the need to prioritize visibility based on actual behavior rather than title-driven requests.
solution
MVP-first UX, cleaner information architecture, and reusable UI foundations
What I drove
• Established a clear MVP UX baseline before development to prevent
thrash and downstream rework
• Simplified page structure and reduced content density — lawyers want
signal, not noise
• Introduced role-based visibility (e.g. hiding “Share Your Office”
unless the user had access)
From an engineering perspective, I focused on reducing UI coupling and duplication by introducing reusable components and shared styling patterns. On mobile, I pushed to move logic out of tightly coupled view models, improve state management, and make components portable across screens to support future iteration.
Constraints
• Limited analytics tooling
• High security and approval friction
• Senior leadership sign-off culture
evidence
Outcome: adoption and praise, even with imperfect data
Formal UX analytics were limited, so I triangulated impact through informal user interviews, support tickets, leadership readouts, and selective mobile usage signals.
Adoption
Usage increased from under 50% to approximately 90%, as reported during department-wide all-hands.
Mobile redesign
The redesigned mobile experience was praised for clarity and usability, alongside a cleaner engineering foundation focused on reusability and maintainability.
private details
Want the full enterprise version?
Due to client confidentiality, detailed visuals, internal workflows, and implementation specifics are available in a private packet upon request.