If you’re working on an SAP Fiori initiative, this question almost always comes up sooner or later:
“Do we need a Fiori specialist, or do we need a UX designer?”
It sounds like a simple question. In reality, it’s one of the most misunderstood decisions in SAP programs, and getting it wrong often explains why Fiori projects look fine on paper but struggle in real life.
The Root of the Confusion
SAP Fiori is often described as a “UX transformation.” That framing leads many organisations to assume:
“If it’s about UX, then a UX designer should handle it.”
That assumption is only partially true.
Fiori is not just about how screens look. It’s about how SAP processes are exposed, simplified, governed, and executed within the constraints of SAP architecture.
That’s where the distinction matters.
SAP Fiori is frequently described as a UX transformation. That description is not wrong, but it’s incomplete.
When people hear “UX,” they naturally think about user journeys, clean screens, and intuitive flows.
So the assumption becomes:
“If this is about user experience, then a UX designer should own it.”
The problem is that SAP Fiori sits at the intersection of user experience and enterprise system reality. And SAP has rules, lots of them.
That’s where the difference between these two roles really starts to matter.
What a Fiori Specialist Really Does (Beyond the Job Title)
A Fiori specialist is someone who lives and breathes SAP reality. Their job is not just to make screens available in Fiori; it’s to ensure that SAP business processes are exposed in a way that is technically correct, supported by SAP, secure and role-based, and aligned with S/4HANA best practices.
In practice, a Fiori specialist spends a lot of time answering questions like:
- Which standard Fiori apps already exist for this process?
- Where should we configure instead of build?
- When do new Fiori elements make sense, and when do they not?
- How do roles, catalogues, spaces, and authorisations come together?
- How do we avoid rebuilding SAP GUI logic in a modern UI?
They constantly balance what users want with what SAP allows.
What a UX Designer Actually Brings
A UX designer comes from a very different angle. They are not thinking in terms of SAP transactions, CDS views, or authorisation objects. They are thinking about people.
A UX designer focuses on how users understand a task, where confusion or friction appears, how many steps feel unnecessary, how information is grouped and presented, and how an experience feels across screens and systems.
They ask questions like: Why does the user have to think so hard here? What is the real goal of this task?
UX designers are excellent at identifying cognitive overload, poor task flow, unnecessary repetition, and inconsistent behaviour across apps.
What they typically don’t own is SAP feasibility. They may design an ideal flow that makes perfect sense from a user perspective, but that doesn’t always translate cleanly into SAP’s transactional world.
Fiori Specialist vs UX Designer: A Side-by-Side Comparison
| Dimension | Fiori Specialist | UX Designer |
| Primary Focus | Making SAP processes work correctly in Fiori | Making experiences intuitive and easy for users |
| Core Question They Ask | “How should this be done in SAP?” | “How should this feel for the user?” |
| Domain Expertise | SAP S/4HANA, Fiori apps, UI5, security, roles, authorisations | User behaviour, usability, interaction design |
| System Knowledge | Deep knowledge of SAP backend logic and constraints | Platform-agnostic (SAP, non-SAP, web, mobile) |
| Typical Responsibilities | App selection, Fiori Elements vs freestyle decisions, role design, clean core alignment | User research, journey mapping, wireframes, interaction flows |
| Strengths | SAP feasibility, governance alignment, and long-term supportability | Adoption, usability, and reduced cognitive load |
| What They Protect | The SAP landscape and future maintainability | The user experience and day-to-day efficiency |
| Risk if Used Alone | Technically correct, but poor adoption | Beautiful designs that can’t be built or scaled in SAP |
| Best Time to Engage | Early—during architecture and process decisions | After SAP boundaries are clear, or when adoption is low |
| Common Misuse | Treating them as “just a UI developer” | Expecting them to solve SAP constraints |
| Success Looks Like | Secure, supported, SAP-aligned Fiori apps | Users complete tasks faster with less frustration |
A Fiori specialist protects the SAP system. A UX designer protects the user experience. They are solving different problems, and pretending one role can fully replace the other is where projects struggle.
Who You Need, and When You Need Them
You need a Fiori specialist when moving from SAP GUI to Fiori, implementing S/4HANA with a Fiori-first strategy, deciding between standard applications and custom development, and addressing security, roles, and governance.
In SAP-led programs, this role is non-negotiable. Without it, you risk building something that looks good but creates long-term technical debt.
UX designers are most effective when users are struggling despite Fiori being “live”, adoption is low, feedback is negative, processes span SAP and non-SAP systems, and you are designing highly customised or cross-role workflows.
They help refine how work gets done once the SAP boundaries are understood.
The Best Results Come From Collaboration
In the most successful Fiori programs, these roles don’t compete; they complement each other. The Fiori specialist defines what is feasible, supported, and sustainable, and the UX designer improves how users experience that reality.
If your biggest question right now is:
- “How do we do this properly in SAP?” → start with a Fiori specialist
- “Why are users still unhappy?” → bring in a UX designer
- “We need correctness and adoption” → use both, intentionally
Final Thought
Fiori transformation is not about choosing between SAP expertise and UX thinking. It’s about understanding which problem you’re solving at each stage. A Fiori specialist keeps SAP healthy. A UX designer keeps users engaged. When both roles are used thoughtfully and at the right time, Fiori starts delivering real business value.
If your organisation is preparing for Fiori activation, or if you’re unsure how to approach it strategically, early consultation with Fiori experts can avoid costly rework. They help you assess readiness, align Fiori with your SAP landscape, and define a rollout approach that fits your users and business priorities.
