Role

Lead Product Designer

SCOPE

Design system

Mobile and web features

Platform-wide UI refresh

Platforms

Web

Mobile Web

iOS and Android

Overview

Context

Quore is a multi-product operational platform used daily by hotel teams across housekeeping, engineering, and management. The product supports time-sensitive tasks such as inspections, maintenance, approvals, and room operations, often performed on the go.

As the platform expanded, maintaining clarity, speed, and consistency across products became increasingly challenging. This work focused on improving how the platform scaled while continuing to support the realities of day-to-day hotel operations.

Goals

The goal of this work was to establish a more scalable and cohesive product foundation across Quore’s ecosystem. This included improving usability in mobile, real-time contexts, aligning UI and interaction patterns across products, and ensuring the platform could evolve without introducing unnecessary complexity.

Platform Consistency

Quore’s apps had evolved independently over time, resulting in inconsistent UI patterns and behaviors. This work aligned core components, interactions, and visual language to create a more predictable and unified experience across products.

Mobile First Flows

Many operational tasks were originally designed for desktop use and became inefficient in mobile, time-sensitive scenarios. Redesigning these workflows prioritized speed, clarity, and ease of use for teams working on the floor.

Scalable Foundation

Beyond individual features, this work laid the groundwork for future growth. By strengthening the design system and shared patterns, new functionality could be introduced more efficiently while maintaining consistency across the platform.

Original Designs

Design System: Building the Foundation

Problem

As Quore evolved into a multi-product operational platform, inconsistencies in UI, interaction patterns, and visual language reduced clarity and predictability.

Desktop-first workflows struggled in mobile, time-sensitive contexts, and the interface no longer reflected the product’s scale or maturity, making it harder to evolve the platform without adding complexity.

Approach

An audit of existing patterns across the platform informed the creation and refinement of a shared design system focused on:

  • Reusable, clearly defined components

  • Consistent interaction patterns across apps

  • Mobile-first behavior and responsiveness

  • Scalability across multiple products and teams

Rather than a full redesign, the system was applied incrementally, supporting both new feature development and gradual improvement of existing experiences.

Outcome

  • Improved visual and behavioral consistency across the platform

  • Faster design and development cycles

  • A shared foundation that reduced fragmentation over time

Key Product Work

CapEx Mobile Web: Approval Flow Improvements

Problem

CapEx approval emails included links for managers to review and approve requests. When opened on mobile devices, those links led to a broken page. There was no native mobile CapEx app, yet approvals were time-sensitive and frequently handled on the go.

Goal

Enable approvers to open a link from an email, authenticate if needed, review all relevant information, and take action quickly, all from their mobile.

Solution

A responsive, standalone mobile web approval experience was designed to:

  • Require authentication before displaying sensitive data

  • Redirect users back to the approval request after login

  • Present all CapEx details in a mobile-optimized format

  • Prioritize clear actions for approving, submitting, or rejecting

The experience assumed a focused use case: making a decision quickly with minimal friction.

Outcome

  • Mobile approvals no longer led to dead ends

  • Reduced friction for executives and managers

  • Faster turnaround on CapEx decisions

QR Code Scanning: Connecting Physical Spaces to Digital Actions

Problem

Hotel teams move constantly through physical spaces like guestrooms, meeting rooms, and shared areas. Accessing the right task or action often required manual navigation through the app, slowing down work on the floor.

Goal

Allow users to scan a QR code tied to a physical area and immediately see relevant context and actions.

Solution

An MVP QR code scanning experience was introduced within the mobile app. A single scan:

  • Identifies the associated area

  • Surfaces open items such as work orders or requests

  • Presents relevant actions based on user role and context

Actions were grouped into clear categories, including maintenance, inspections, housekeeping, and requests, to avoid overwhelming users.

Outcome

  • Faster access to area-specific tasks

  • Reduced navigation and setup time

  • A flexible system capable of scaling across departments and workflows

Platform-wide UI Refresh & Feature Enhancements

In parallel with feature development, usability and consistency were improved across Quore’s core apps and experiences, including:

and other supporting apps, as well as Native mobile shell (login, navigation, settings) and Product tours, banners, and motion-based guidance.

The focus was on improving clarity, reducing visual noise, and creating a more cohesive experience across the platform.

Impact

This work contributed to meaningful improvements across Quore’s platform by addressing both immediate workflow friction and long-term scalability.

  • Faster execution of time-sensitive tasks in mobile and on-the-floor contexts

  • Reduced friction in approval, inspection, and maintenance workflows

  • Improved visual and behavioral consistency across multiple products

  • A shared design foundation that enabled new features to ship with less overhead and greater predictability

Together, these improvements supported a platform that could scale while remaining reliable for teams performing critical, real-time operations.

Reflection

This work reinforced the importance of designing at the system level rather than optimizing individual screens. Focusing on shared patterns, clear constraints, and real operational use cases made it possible to improve speed and consistency across multiple products without disrupting existing workflows.

The result was a platform that could evolve more predictably, support new features with less overhead, and better reflect how teams actually work on the floor.