No Status Indicator Project Case Study - Azure Arc
Azure Machine Configuration
Case Study Cover

SAP Fiori Design System

My Role UX Designer
Timeline 12 Months
Team 2 Eng 1 Researcher
Status
Shipped
The Overview

A dedicated mobile platform designed to streamline the recruitment lifecycle. We focused on bridging the gap between passive browsing and active application through a "mobile-first" experience.

The Challenge

Application Fatigue." User research indicated that candidates often abandon applications due to repetitive data entry and opaque status updates. The challenge was to reduce friction and make the applying process as simple as a single tap.

Impact
23+
Apps Adoption
Active adoption across the entire product ecosystem.
32 / 12
Components & Patterns
Core system elements defined and shipped.

02 Problem & Strategy

Solving "Inconsistency" at Scale

The Pain Point: "Fragmented Experience, High Friction"

Our audit revealed that users faced disjointed workflows across the product suite, leading to high drop-off rates during critical tasks like job application and profile management. Developers were also slowing down by "reinventing the wheel" for every new feature.

User Impact
High Drop-off Rates

Users abandoned critical flows due to inconsistent patterns and repetitive data entry friction.

Dev Impact
Redundant Work

Engineering velocity slowed as teams constantly rebuilt similar UI elements from scratch.

The Strategy: Modular & Reusable Patterns

Instead of designing screens in isolation, I adopted a System-First Approach . This shift moved us from one-off page design to creating a language of reusable components.

Standardized Flows

Unified

Created a unified "One-Click Apply" pattern to remove friction and standardize the application process.

Component Library

32 Items

Built 32 reusable components (Cards, Lists, Inputs) to ensure visual consistency and accelerate engineering velocity.

03 System Implementation (Showcase)

"Powered by the SAP Design System Tool Kit." The screens above demonstrate how we applied the standardized design language to a real-world product. By leveraging atomic components from our central library, we ensured a consistent and accessible experience across the entire candidate journey.

👉 Note: To view the comprehensive component library and guidelines, please refer to the separate "SAP Design System Tool Kit" in figma.
Referral Flow Design

Reach Out for the Full Design Walkthrough.

04 Impact & Learnings

Creativity through Constraint

We proved that a strong design system doesn't limit creativity—it frees up designers to focus on unique business problems rather than basic plumbing.

Infrastructure is the silent accelerator.

By solving the universal pain points (like Activation & Login ) just once, we stopped teams from "reinventing the wheel." Infrastructure doesn't just standardize UI—it standardizes excellence across the ecosystem.

23+
Apps Adopting
Powered the entire mobile ecosystem, ensuring consistent behavior across all touchpoints.
32+
Global Components
Standardized patterns shipped and documented, reducing development time for new features.