CONTENT

Intro

Highlight

Discovery

User Flow

Usability Testing

Back

Designing for Operational Confidence in High-Pressure Pet Care Environments

Time: 2024

Duration: 3 months

My role:

I worked as a Product Designer, leading the redesign of the booking and service workflow to improve operational efficiency and reduce staff errors during peak hours.

Responsibility:

I redesigned booking and checkout workflows, improved customer and pet data structure, collaborated with engineers on scalable solutions, and iterated based on staff feedback.

Time & Status:

Feb 2024 - May 2024




HIGHLIGHT

From Chaos to Operational Clarity

Performance Dashboard

Monitor revenue, bookings, and staff activity at a glance.

Appointment Management

Track appointments and service progress without context switching.

Efficient Checkout Experience

Simplify payments with clear status and feedback.

Centralized Scheduling

A unified calendar to manage bookings across their full lifecycle.

Discovery

Problem Framing

Stakeholder Interview

Why Layout Matters Less Than Operational Rhythm

When this project began, I initially viewed the complexity as a visual clutter problem, but the Kickoff meeting quickly corrected that assumption. Listening to the team discuss granular details—like handling member queries while a line forms at the register—made me realize that a "clean" UI would fail if it ignored the physical chaos of a pet center. I shifted my focus from interface design to system structure, realizing that the real friction stemmed from fragmented information that disrupted the staff's natural workflow. By reframing the challenge around reducing cognitive load rather than just moving pixels, I began to design for the "time and tempo" of a high-pressure environment.

When this project began, I initially viewed the complexity as a visual clutter problem, but the Kickoff meeting quickly corrected that assumption. Listening to the team discuss granular details—like handling member queries while a line forms at the register—made me realize that a "clean" UI would fail if it ignored the physical chaos of a pet center. I shifted my focus from interface design to system structure, realizing that the real friction stemmed from fragmented information that disrupted the staff's natural workflow. By reframing the challenge around reducing cognitive load rather than just moving pixels, I began to design for the "time and tempo" of a high-pressure environment.

Information Architecture

User Flow

User Journey Map

What Looks Like Complexity Is Often Lack of Certainty

As discovery progressed, I noticed staff frequently paused or repeated steps, not because they were untrained, but because the system provided no sense of confidence. I chose to restructure the core user flow, consolidating payment confirmation, change prompts, and transaction status into a single, unified visual area to prevent operational interruptions.

As discovery progressed, I noticed staff frequently paused or repeated steps, not because they were untrained, but because the system provided no sense of confidence. I chose to restructure the core user flow, consolidating payment confirmation, change prompts, and transaction status into a single, unified visual area to prevent operational interruptions.

This design decision removed the need for staff to jump between screens to verify a single order's progress during peak hours. Through this consolidation, I realized that "simplicity" in a B2B context is actually the presence of certainty, when the system gives the user total control over the next move.

This design decision removed the need for staff to jump between screens to verify a single order's progress during peak hours. Through this consolidation, I realized that "simplicity" in a B2B context is actually the presence of certainty, when the system gives the user total control over the next move.

Feasibility Assessment

Dev Trade-off Negotiation

Usability Testing

Holding the Line Between Ideal UX and Technical Reality

Once the final constraints became clear, I faced the difficult task of stripping back specific design details to ensure the project could actually launch. Initially, I was reluctant to cut interactions, fearing the experience would be diluted, but discussions with the engineering team about system performance changed my perspective. I learned to balance high-fidelity aspirations with the reality of on-site pressure, prioritizing robust, reliable status tracking over complex animations. What mattered most was not shipping a "perfect" prototype, but delivering a tool that stayed stable and responsive when the store was at its most chaotic.

Once the final constraints became clear, I faced the difficult task of stripping back specific design details to ensure the project could actually launch. Initially, I was reluctant to cut interactions, fearing the experience would be diluted, but discussions with the engineering team about system performance changed my perspective. I learned to balance high-fidelity aspirations with the reality of on-site pressure, prioritizing robust, reliable status tracking over complex animations. What mattered most was not shipping a "perfect" prototype, but delivering a tool that stayed stable and responsive when the store was at its most chaotic.
Next project:
Next project:

HackQuest

Web3
Learning Platform

Redesign the Web3 learning interface to make it more accessible for new developers

© Jinlan Huang 2026