Modernizing a Mission-Critical Enterprise Ecosystem Without Disrupting Business Operations
In large global organizations, systems such as SAP Product Lifecycle Management (PLM) sit at the center of product innovation, regulatory compliance, approvals, and operational coordination. Failure is not an option. Stability, governance, and continuity take precedence over experimentation.
This engagement focused on helping a leading global FMCG organization modernize a complex SAP PLM ecosystem whose user experience had gradually deteriorated over time despite remaining operationally robust.
The challenge was not redesigning a single application. It was improving the experience across more than 25 interconnected applications while preserving business continuity, compliance, and existing workflows.
Executive Context
The SAP PLM landscape supported critical business activities across global teams. Over the years, the application suite had evolved across multiple generations of SAP technologies. Some applications predated SAP Fiori/UI5, while others incorporated elements of newer frameworks.
The result was an ecosystem of 25+ complex and interdependent applicationsthat lacked consistency in navigation, interaction patterns, and Users faced:
Inconsistent navigation models
Different interaction patterns across applications
Dense information-heavy screens
Limited visual hierarchy
Increasing cognitive effort to complete common tasks
While the underlying platform remained business critical, the growing gap between user expectations and system behavior was beginning to affect productivity, consistency, and satisfaction.
I was engaged, working alongside a leading SAP partner, to help modernize this legacy environment through a design-led transformation, without disrupting business continuity.
Key Challenges
The organization recognized the need for modernization but required evidence before committing to a large-scale transformation. Any proposed solution needed to operate within several non-negotiable constraints:
Existing workflows and approval processes had to remain intact
Compliance requirements could not be compromised
SAP Fiori/UI5 architectural standards had to be respected
Global rollout implications needed to be considered from the outset
Changes could not negatively impact performance or operational efficiency
This made the initiative as much a governance and change-management challenge as it was a design problem.
Design Framing
Default Approach
How do we redesign 25 applications?
Suggested Approach
Can a design-led approach improve usability and consistency without disrupting proven business processes?
The Approach
01. Proof Before Scale
To reduce risk, the transformation began with a carefully selected proof-of-concept application. The application was chosen because it represented:
Core PLM workflows
High task complexity
Common interaction patterns reused across the aross the broader ecosystem
This allowed business stakeholders to evaluate the value of a design-led approach before committing to wider transformation efforts.
02. Designing Within Constraints
The objective was never to introduce radical change. Instead, the focus was on reducing friction while preserving operational integrity. Several design principles guided the work:
Preserve Workflow Continuity: Existing workflows were respected unless a superior alternative could be clearly justified.
Maintain Efficiency: Task flows could not become longer. A working constraint was maintaining a maximum of three steps per task, ensuring improvements did not come at the expense of productivity.
Improve Information Hierarchy: Information-dense screens were reorganized to help users locate, interpret, and act on critical information more confidently while avoiding horizontal scrolling and unnecessary interface complexity.
Leverage Platform Standards: Rather than fighting SAP Fiori/UI5 limitations, the design approach used those constraints as opportunities to establish consistency and predictability across the ecosystem.
Rather than fighting SAP Fiori/UI5 constraints, the design leveraged them intelligently turning limitations into consistency patterns.
03. From Individual Screens to System Thinking
As redesign patterns emerged, it became clear that many usability challenges were not isolated to specific applications. A significant portion of the friction came from inconsistent behaviors, navigation structures, and interaction models across the suite. To address this, successful patterns were abstracted into a reusable design system that established:
Consistent interaction models
Shared visual language
Reusable interface patterns
Scalable implementation standards
The initiative evolved from a redesign effort into a long-term modernization framework capable of supporting future transformation across the SAP PLM landscape.
04. Remote, Multi-Stakeholder Delivery at Scale
The program was delivered over approximately two years in a fully remote operating model. Success required continuous collaboration between:
Business stakeholders
SAP functional teams
Engineering partners
UX practitioners
Design leadership
Regular review and validation cycles ensured that usability improvements aligned with technical feasibility, business objectives, and enterprise governance requirements before broader implementation.
Solution & Outcome
The engagement resulted in a scalable UX transformation framework for more than 25 SAP PLM applications. The organization gained:
A validated proof-of-concept for modernization
A reusable enterprise UX design system
Greater consistency across the application ecosystem
A structured roadmap for future SAP modernization initiatives
Improved usability and user confidence across critical workflows
Most importantly, the transformation demonstrated that meaningful modernization can be achieved in highly constrained enterprise environments without disrupting business-critical operations.
Key Takeaway
The project was not about making SAP look modern.
It was about creating a sustainable path toward enterprise-wide consistency, usability, and scalability while respecting the realities of governance, compliance, and operational continuity. In environments where change carries significant business risk, design succeeds not by replacing existing systems, but by helping them evolve with confidence.
