Background
Oracle HCM Cloud was built for desktop workflows at a time when enterprise usage patterns were rapidly shifting to mobile. As competitors like Workday and SAP advanced mobile experiences, Oracle faced a structural risk: incremental UI updates would not be sufficient to sustain long-term leadership.
This initiative was not a redesign—it required a fundamental rearchitecture of how HCM workflows, patterns, and performance operated across devices and business domains.
Outcome & Impact
Outcome
Delivered a comprehensive mobile-first rearchitecture across 100+ product areas and dozens of business domains
Established a new cross-HCM interaction model and UX pattern library
Launched globally in 2018
Impact
~$775M in new revenue within six months (+22.5% YoY)
~27M net user growth (Gartner 2019)
Oracle advanced to #1 global HCM cloud leader post-launch and retained leadership through 2025 (Gartner)
My Role & Leadership Scope
Role
Senior UX Lead, Oracle HCM Cloud
Leadership Scope
Led mobile-first UX strategy across hundreds of product surfaces
Defined core interaction models and scalable UX patterns
Drove cross-team alignment across design, product, engineering, and central research
Balanced system performance, usability, and enterprise constraints at scale
Strategic Problem
How do you rearchitect a desktop-centric enterprise platform for mobile responsiveness—while preserving system integrity across hundreds of interconnected workflows?
Why This Was Hard
HCM workflows are long, stateful, and cross-module.
Legacy interaction models (e.g., train-stop flows) fundamentally broke on mobile constraints.
Any solution had to scale globally across products, teams, and devices.
Key Design Decisions
Decision 1 — Replacing Desktop Interaction Models with Mobile-Responsive Patterns
Desktop patterns such as horizontal train-stop workflows fundamentally broke on mobile. Instead of adapting them incrementally, I led the decision to replace them with Compact Guided Processes (CGP)—a vertically progressive, task-completion-driven model designed for mobile constraints.
Outcome: Enabled complex enterprise workflows to scale gracefully across mobile form factors.
Decision 2 — Designing for Scale, Not Individual Screens
Mobile-first was not about shrinking screens—it required redefining layout density, edit/read modes, and content prioritization across varying device sizes.
Rather than designing per-screen solutions, we established system-level layout rules that could adapt across mobile, tablet, and desktop.
Before Mobile UX
After Mobile UX
Outcome: Achieved consistent usability and performance across devices without duplicating logic.
Decision 3 — Pattern-First Systemization Across HCM
To enable mobile-responsive scale across Oracle HCM Cloud, we restructured the design process from page-based execution to pattern-based system thinking. Rather than adapting individual screens, we deconstructed existing experiences, reconstructed core interaction patterns, and reassembled them into reusable task flows that could scale consistently across products, devices, and business domains.
Outcome: Enabled rapid, consistent delivery across dozens of products and teams.
Evidence of Excution
Core Mobile Flows
Add Absence · Change Personal Details · Change Contact Information · Promote
Representative mobile-first workflows demonstrating pattern scalability across HCM domains
Usability & Performance Validation
Central UX Research validated task efficiency and completion accuracy
80% of users completed the Promote flow in under 2 minutes, compared to ~5 minutes pre-launch
Mobile usability improvements directly correlated with adoption growth
Scaling Impact - Recruiting & ICE
After establishing the mobile -first system, I returned to lead recruiting workflows and scaled the system across recruiting and candidate experience domains
Representative examples:
ICE Landing Page
Job Search (Card View)
End-to-end Candidate Experience
Screenshots 3-4
Final Reflection
This transformation was not about mobile UI—it was about resetting Oracle HCM’s interaction foundation for the next decade. By shifting from page-based design to pattern-driven systems, Oracle regained mobile competitiveness while preserving enterprise-grade scale and performance.