UI / UX Design

Consolidating Time Off

Led the end-to-end mobile experience design for displaying employee Time Off within Workday Scheduling’s mobile application

Role :

Lead Product Designer – Mobile UX (iOS + Android)

Tools :

Figma, Design System Components, Platform Guidelines (iOS & Android)

Team :

PM, iOS Engineer, Android Engineer, QA

Methods :

Cross-functional Workshops, System Audit, Competitive Research, Mobile Prototyping, Iteration with Engineering, Validation through stakeholder reviews

Featured Project Cover Image
Featured Project Cover Image
Featured Project Cover Image

📌 Project Overview :

The goal of this initiative was to surface worker time off information directly inside the ESS (Employee Self-Service) Scheduling mobile app, eliminating the need for employees to switch between Workday Time Tracking and Scheduling. The feature needed to support iOS and Android while scaling globally across industries and regulatory environments beyond North America.

Workers had to leave the Scheduling app to view time off requests and statuses, creating friction and fragmented workflows. Time off data (PTO, Leave of Absence, partial-day leave, status variations) also required accurate business process alignment across systems.

Project Details

Product: Employee Self Service (ESS) Scheduling
Scope: Consolidation of time-off visibility, request flows, and balance tracking into a unified ESS experience
Methods: End-to-end journey mapping, IA restructuring, interaction simplification, validation testing
Platforms: Web (Desktop + Responsive ESS)

💻 Final Design :

The final solution delivers a fully integrated Time Off experience within the ESS Scheduling mobile app, eliminating the need for workers to toggle between modules. The design balances enterprise data integrity with frontline usability, ensuring workers can quickly scan, interpret, and trust the information presented.

Rather than overloading the interface, we focused on structured clarity. The solution includes:

  • Clear status indicators aligned with business process states (Submitted, Approved, Denied)

  • Visual differentiation between PTO and Leave of Absence

  • Explicit duration display for full-day, hourly, and range-based time off

  • Automatic transition of approved requests into completed schedule blocks

  • Dedicated loading, offline, and server error states

  • Platform-native UI patterns for both iOS and Android

On iOS, the interface uses subtle status integration within list hierarchy, leveraging native spacing and typography to maintain clarity without visual noise. On Android, Material-based components and stronger visual affordances enhance scannability in fast-paced frontline environments.

Importantly, the solution does not just display information — it reinforces scheduling confidence for both workers and operations managers. Every state change is intentional, traceable to backend logic, and visually consistent across platforms.

This implementation strengthened ESS Scheduling as a true self-service hub, not just a schedule viewer, while supporting global scalability and enterprise-grade reliability.

🔍 Exploration & Discovery :

Bringing Time Off into ESS Scheduling was not simply a UI enhancement — it required alignment across business processes, backend data integrity, and global workforce requirements. Given Workday Scheduling is sold to operations leaders responsible for optimizing frontline labor, any new feature had to preserve scheduling accuracy while reducing worker friction.

We began with cross-functional alignment workshops and system audits to understand how Time Off data flows across Workday modules and how that data would surface in a mobile scheduling context.

Through discovery, we identified several critical design constraints and insights:

  • Status must mirror business process logic — Submitted, Approved, Denied, and Completed states needed to reflect real-time backend workflows.

  • Approved time off must translate visually into completed schedule blocks, not just a labeled entry.

  • Leave of Absence requires differentiated treatment from standard PTO to prevent scheduling ambiguity.

  • Partial-day vs. full-day requests needed immediate scannability in a mobile list view.

  • The solution had to scale across industries and international markets (UK, Europe, North America), where labor regulations and leave structures vary.

We also evaluated platform expectations for both iOS and Android to ensure the experience felt native rather than templated. Rather than designing one universal UI, we established a shared logic system with platform-specific presentation.

This discovery phase clarified that the challenge was not “how to show time off,” but how to:

  • Reduce app switching

  • Maintain operational clarity

  • Preserve system integrity

  • Support scalability at enterprise scale

That clarity directly shaped our design framework.

✏️ Design Process :

Information Architecture & Status Framework

We first defined a clear status framework:

  • Submitted (Pending)

  • Approved (Completed in schedule)

  • Denied

  • Error / Sync Issue

Each state required:

  • Visual differentiation

  • Clear text reinforcement

  • Accessibility compliance

We explored multiple badge treatments before aligning on a consistent system that worked across both platforms.

Early Wireframes & Failed Direction

Our initial approach attempted to:

  • Embed time off directly into the schedule list with minimal visual distinction.

What failed:
Testing with stakeholders showed confusion between:

  • Leave of absence vs PTO

  • Partial-day vs full-day

  • Approved vs pending

Workers could not easily scan and differentiate.

Iteration:
We introduced:

  • Clear status chips

  • Date hierarchy adjustments

  • Differentiated iconography

  • Stronger visual grouping

This improved scannability dramatically.

Display Variations Design

We created display variations for:

  • Submitted & Approved

  • Submitted & Not Approved

  • Partially Approved

  • Leave of Absence (long-term absence)

  • Full day vs hourly time off

  • Range-based time off

  • Loading states

  • Offline states

  • Sync error states

Each scenario required a separate UI logic model.

This phase ensured enterprise reliability and reduced ambiguity in real workforce contexts.

Platform-Specific Execution

iOS

  • Clean status indicators integrated within list hierarchy

  • Native typography and spacing

  • Subtle but clear error states

  • Completed time off visually reflected within schedule timeline

Android

  • Clear Material-based status indicators

  • Structured list treatment

  • Stronger emphasis on color-coded status cues

  • Dedicated loading and server error patterns

We ensured consistency in logic, but native presentation in execution.

Engineering Collaboration

Close collaboration with:

  • iOS Engineer

  • Android Engineer

Key challenges:

  • Aligning real-time status updates with backend sync

  • Handling offline behavior

  • Ensuring performance at enterprise scale

We validated edge cases continuously to prevent regression in scheduling accuracy.

📈 Impact :

  • Eliminated cross-app switching between Scheduling and Time Tracking

  • Reduced workflow friction for frontline workers

  • Improved clarity of time off status interpretation

  • Strengthened alignment between scheduling engine and mobile UX

  • Increased mobile engagement within ESS Scheduling

  • Established scalable status pattern framework for future workforce features

  • Delivered consistent iOS and Android experiences globally (UK, Europe, North America)

More Projects

UI / UX Design

Consolidating Time Off

Led the end-to-end mobile experience design for displaying employee Time Off within Workday Scheduling’s mobile application

Role :

Lead Product Designer – Mobile UX (iOS + Android)

Tools :

Figma, Design System Components, Platform Guidelines (iOS & Android)

Team :

PM, iOS Engineer, Android Engineer, QA

Methods :

Cross-functional Workshops, System Audit, Competitive Research, Mobile Prototyping, Iteration with Engineering, Validation through stakeholder reviews

Featured Project Cover Image
Featured Project Cover Image
Featured Project Cover Image

📌 Project Overview :

The goal of this initiative was to surface worker time off information directly inside the ESS (Employee Self-Service) Scheduling mobile app, eliminating the need for employees to switch between Workday Time Tracking and Scheduling. The feature needed to support iOS and Android while scaling globally across industries and regulatory environments beyond North America.

Workers had to leave the Scheduling app to view time off requests and statuses, creating friction and fragmented workflows. Time off data (PTO, Leave of Absence, partial-day leave, status variations) also required accurate business process alignment across systems.

Project Details

Product: Employee Self Service (ESS) Scheduling
Scope: Consolidation of time-off visibility, request flows, and balance tracking into a unified ESS experience
Methods: End-to-end journey mapping, IA restructuring, interaction simplification, validation testing
Platforms: Web (Desktop + Responsive ESS)

💻 Final Design :

The final solution delivers a fully integrated Time Off experience within the ESS Scheduling mobile app, eliminating the need for workers to toggle between modules. The design balances enterprise data integrity with frontline usability, ensuring workers can quickly scan, interpret, and trust the information presented.

Rather than overloading the interface, we focused on structured clarity. The solution includes:

  • Clear status indicators aligned with business process states (Submitted, Approved, Denied)

  • Visual differentiation between PTO and Leave of Absence

  • Explicit duration display for full-day, hourly, and range-based time off

  • Automatic transition of approved requests into completed schedule blocks

  • Dedicated loading, offline, and server error states

  • Platform-native UI patterns for both iOS and Android

On iOS, the interface uses subtle status integration within list hierarchy, leveraging native spacing and typography to maintain clarity without visual noise. On Android, Material-based components and stronger visual affordances enhance scannability in fast-paced frontline environments.

Importantly, the solution does not just display information — it reinforces scheduling confidence for both workers and operations managers. Every state change is intentional, traceable to backend logic, and visually consistent across platforms.

This implementation strengthened ESS Scheduling as a true self-service hub, not just a schedule viewer, while supporting global scalability and enterprise-grade reliability.

🔍 Exploration & Discovery :

Bringing Time Off into ESS Scheduling was not simply a UI enhancement — it required alignment across business processes, backend data integrity, and global workforce requirements. Given Workday Scheduling is sold to operations leaders responsible for optimizing frontline labor, any new feature had to preserve scheduling accuracy while reducing worker friction.

We began with cross-functional alignment workshops and system audits to understand how Time Off data flows across Workday modules and how that data would surface in a mobile scheduling context.

Through discovery, we identified several critical design constraints and insights:

  • Status must mirror business process logic — Submitted, Approved, Denied, and Completed states needed to reflect real-time backend workflows.

  • Approved time off must translate visually into completed schedule blocks, not just a labeled entry.

  • Leave of Absence requires differentiated treatment from standard PTO to prevent scheduling ambiguity.

  • Partial-day vs. full-day requests needed immediate scannability in a mobile list view.

  • The solution had to scale across industries and international markets (UK, Europe, North America), where labor regulations and leave structures vary.

We also evaluated platform expectations for both iOS and Android to ensure the experience felt native rather than templated. Rather than designing one universal UI, we established a shared logic system with platform-specific presentation.

This discovery phase clarified that the challenge was not “how to show time off,” but how to:

  • Reduce app switching

  • Maintain operational clarity

  • Preserve system integrity

  • Support scalability at enterprise scale

That clarity directly shaped our design framework.

✏️ Design Process :

Information Architecture & Status Framework

We first defined a clear status framework:

  • Submitted (Pending)

  • Approved (Completed in schedule)

  • Denied

  • Error / Sync Issue

Each state required:

  • Visual differentiation

  • Clear text reinforcement

  • Accessibility compliance

We explored multiple badge treatments before aligning on a consistent system that worked across both platforms.

Early Wireframes & Failed Direction

Our initial approach attempted to:

  • Embed time off directly into the schedule list with minimal visual distinction.

What failed:
Testing with stakeholders showed confusion between:

  • Leave of absence vs PTO

  • Partial-day vs full-day

  • Approved vs pending

Workers could not easily scan and differentiate.

Iteration:
We introduced:

  • Clear status chips

  • Date hierarchy adjustments

  • Differentiated iconography

  • Stronger visual grouping

This improved scannability dramatically.

Display Variations Design

We created display variations for:

  • Submitted & Approved

  • Submitted & Not Approved

  • Partially Approved

  • Leave of Absence (long-term absence)

  • Full day vs hourly time off

  • Range-based time off

  • Loading states

  • Offline states

  • Sync error states

Each scenario required a separate UI logic model.

This phase ensured enterprise reliability and reduced ambiguity in real workforce contexts.

Platform-Specific Execution

iOS

  • Clean status indicators integrated within list hierarchy

  • Native typography and spacing

  • Subtle but clear error states

  • Completed time off visually reflected within schedule timeline

Android

  • Clear Material-based status indicators

  • Structured list treatment

  • Stronger emphasis on color-coded status cues

  • Dedicated loading and server error patterns

We ensured consistency in logic, but native presentation in execution.

Engineering Collaboration

Close collaboration with:

  • iOS Engineer

  • Android Engineer

Key challenges:

  • Aligning real-time status updates with backend sync

  • Handling offline behavior

  • Ensuring performance at enterprise scale

We validated edge cases continuously to prevent regression in scheduling accuracy.

📈 Impact :

  • Eliminated cross-app switching between Scheduling and Time Tracking

  • Reduced workflow friction for frontline workers

  • Improved clarity of time off status interpretation

  • Strengthened alignment between scheduling engine and mobile UX

  • Increased mobile engagement within ESS Scheduling

  • Established scalable status pattern framework for future workforce features

  • Delivered consistent iOS and Android experiences globally (UK, Europe, North America)

More Projects

UI / UX Design

Consolidating Time Off

Led the end-to-end mobile experience design for displaying employee Time Off within Workday Scheduling’s mobile application

Role :

Lead Product Designer – Mobile UX (iOS + Android)

Tools :

Figma, Design System Components, Platform Guidelines (iOS & Android)

Team :

PM, iOS Engineer, Android Engineer, QA

Methods :

Cross-functional Workshops, System Audit, Competitive Research, Mobile Prototyping, Iteration with Engineering, Validation through stakeholder reviews

Featured Project Cover Image
Featured Project Cover Image
Featured Project Cover Image

📌 Project Overview :

The goal of this initiative was to surface worker time off information directly inside the ESS (Employee Self-Service) Scheduling mobile app, eliminating the need for employees to switch between Workday Time Tracking and Scheduling. The feature needed to support iOS and Android while scaling globally across industries and regulatory environments beyond North America.

Workers had to leave the Scheduling app to view time off requests and statuses, creating friction and fragmented workflows. Time off data (PTO, Leave of Absence, partial-day leave, status variations) also required accurate business process alignment across systems.

Project Details

Product: Employee Self Service (ESS) Scheduling
Scope: Consolidation of time-off visibility, request flows, and balance tracking into a unified ESS experience
Methods: End-to-end journey mapping, IA restructuring, interaction simplification, validation testing
Platforms: Web (Desktop + Responsive ESS)

💻 Final Design :

The final solution delivers a fully integrated Time Off experience within the ESS Scheduling mobile app, eliminating the need for workers to toggle between modules. The design balances enterprise data integrity with frontline usability, ensuring workers can quickly scan, interpret, and trust the information presented.

Rather than overloading the interface, we focused on structured clarity. The solution includes:

  • Clear status indicators aligned with business process states (Submitted, Approved, Denied)

  • Visual differentiation between PTO and Leave of Absence

  • Explicit duration display for full-day, hourly, and range-based time off

  • Automatic transition of approved requests into completed schedule blocks

  • Dedicated loading, offline, and server error states

  • Platform-native UI patterns for both iOS and Android

On iOS, the interface uses subtle status integration within list hierarchy, leveraging native spacing and typography to maintain clarity without visual noise. On Android, Material-based components and stronger visual affordances enhance scannability in fast-paced frontline environments.

Importantly, the solution does not just display information — it reinforces scheduling confidence for both workers and operations managers. Every state change is intentional, traceable to backend logic, and visually consistent across platforms.

This implementation strengthened ESS Scheduling as a true self-service hub, not just a schedule viewer, while supporting global scalability and enterprise-grade reliability.

🔍 Exploration & Discovery :

Bringing Time Off into ESS Scheduling was not simply a UI enhancement — it required alignment across business processes, backend data integrity, and global workforce requirements. Given Workday Scheduling is sold to operations leaders responsible for optimizing frontline labor, any new feature had to preserve scheduling accuracy while reducing worker friction.

We began with cross-functional alignment workshops and system audits to understand how Time Off data flows across Workday modules and how that data would surface in a mobile scheduling context.

Through discovery, we identified several critical design constraints and insights:

  • Status must mirror business process logic — Submitted, Approved, Denied, and Completed states needed to reflect real-time backend workflows.

  • Approved time off must translate visually into completed schedule blocks, not just a labeled entry.

  • Leave of Absence requires differentiated treatment from standard PTO to prevent scheduling ambiguity.

  • Partial-day vs. full-day requests needed immediate scannability in a mobile list view.

  • The solution had to scale across industries and international markets (UK, Europe, North America), where labor regulations and leave structures vary.

We also evaluated platform expectations for both iOS and Android to ensure the experience felt native rather than templated. Rather than designing one universal UI, we established a shared logic system with platform-specific presentation.

This discovery phase clarified that the challenge was not “how to show time off,” but how to:

  • Reduce app switching

  • Maintain operational clarity

  • Preserve system integrity

  • Support scalability at enterprise scale

That clarity directly shaped our design framework.

✏️ Design Process :

Information Architecture & Status Framework

We first defined a clear status framework:

  • Submitted (Pending)

  • Approved (Completed in schedule)

  • Denied

  • Error / Sync Issue

Each state required:

  • Visual differentiation

  • Clear text reinforcement

  • Accessibility compliance

We explored multiple badge treatments before aligning on a consistent system that worked across both platforms.

Early Wireframes & Failed Direction

Our initial approach attempted to:

  • Embed time off directly into the schedule list with minimal visual distinction.

What failed:
Testing with stakeholders showed confusion between:

  • Leave of absence vs PTO

  • Partial-day vs full-day

  • Approved vs pending

Workers could not easily scan and differentiate.

Iteration:
We introduced:

  • Clear status chips

  • Date hierarchy adjustments

  • Differentiated iconography

  • Stronger visual grouping

This improved scannability dramatically.

Display Variations Design

We created display variations for:

  • Submitted & Approved

  • Submitted & Not Approved

  • Partially Approved

  • Leave of Absence (long-term absence)

  • Full day vs hourly time off

  • Range-based time off

  • Loading states

  • Offline states

  • Sync error states

Each scenario required a separate UI logic model.

This phase ensured enterprise reliability and reduced ambiguity in real workforce contexts.

Platform-Specific Execution

iOS

  • Clean status indicators integrated within list hierarchy

  • Native typography and spacing

  • Subtle but clear error states

  • Completed time off visually reflected within schedule timeline

Android

  • Clear Material-based status indicators

  • Structured list treatment

  • Stronger emphasis on color-coded status cues

  • Dedicated loading and server error patterns

We ensured consistency in logic, but native presentation in execution.

Engineering Collaboration

Close collaboration with:

  • iOS Engineer

  • Android Engineer

Key challenges:

  • Aligning real-time status updates with backend sync

  • Handling offline behavior

  • Ensuring performance at enterprise scale

We validated edge cases continuously to prevent regression in scheduling accuracy.

📈 Impact :

  • Eliminated cross-app switching between Scheduling and Time Tracking

  • Reduced workflow friction for frontline workers

  • Improved clarity of time off status interpretation

  • Strengthened alignment between scheduling engine and mobile UX

  • Increased mobile engagement within ESS Scheduling

  • Established scalable status pattern framework for future workforce features

  • Delivered consistent iOS and Android experiences globally (UK, Europe, North America)

More Projects