SAP Fiori
An enterprise user experience layer launched by SAP in 2013. Its role-based tile launchpad replaces the traditional SAP GUI transaction code interface, is driven at its base by OData services, and supports mobile and desktop clients.
Timeline (last 90 days)
SAP Fiori is SAP's next-generation user experience layer launched in 2013, replacing the traditional SAP GUI transaction code interface with a role-based tile-style launchpad, driven at the underlying level by OData services, with native support for mobile and desktop multi-device.
The core contradiction of enterprise UX lies not in talent or technology, but in misaligned incentives—buyers (CIOs, project managers) and users (warehouse operators) almost never meet in the same scenario, and there is a natural disconnect between procurement decisions and daily use experience.
Enterprise Fiori implementations have only UAT sign-off documents, go-live readiness checklists, and a hypercare period that ends 30 days after launch, lacking corrective feedback mechanisms like those of consumer-grade applications, such as crash reports, funnel analysis, session recording, and NPS.
In enterprise implementations there are too many stakeholders with design veto power (IT security, business processes, finance, operations, Basis), resulting in a launchpad that satisfies every item on the checklist yet is unusable for everyone.
Role-based application delivery is Fiori's most genuine capability: by designing dedicated launchpads for different warehouse roles (receiving, picking, returns processing) and having tiles named with verbs, the post-launch productivity collapse can be avoided.
Hardware-first testing pattern: test on real hardware (1024×768 warehouse terminals, shared tablets with cracked-screen protectors, industrial touchscreens with 40ms input latency, warehouse on-site networks) before UAT rather than after.
Task-based launchpad design pattern: interview three users per role, have them describe a day's work in chronological order, map the launchpad to that narrative, and name apps with verbs rather than nouns (e.g., Check Expected Deliveries rather than VL06I - Inbound Delivery Monitor).
The author proposes a two-minute test: whether a non-SAP user can, on real hardware, without help, on the first attempt, complete the most common daily task within two minutes; accompanying checks include cold-start task completion, all tile names using verbs, and at least three real end users having tested on production hardware before UAT sign-off.
All Facts (8)
SAP Fiori is SAP's next-generation user experience layer launched in 2013, replacing the traditional SAP GUI transaction code interface with a role-based tile-style launchpad, driven at the underlying level by OData services, with native support for mobile and desktop multi-device.
50%UnverifiedThe core contradiction of enterprise UX lies not in talent or technology, but in misaligned incentives—buyers (CIOs, project managers) and users (warehouse operators) almost never meet in the same scenario, and there is a natural disconnect between procurement decisions and daily use experience.
50%UnverifiedEnterprise Fiori implementations have only UAT sign-off documents, go-live readiness checklists, and a hypercare period that ends 30 days after launch, lacking corrective feedback mechanisms like those of consumer-grade applications, such as crash reports, funnel analysis, session recording, and NPS.
50%UnverifiedIn enterprise implementations there are too many stakeholders with design veto power (IT security, business processes, finance, operations, Basis), resulting in a launchpad that satisfies every item on the checklist yet is unusable for everyone.
50%UnverifiedRole-based application delivery is Fiori's most genuine capability: by designing dedicated launchpads for different warehouse roles (receiving, picking, returns processing) and having tiles named with verbs, the post-launch productivity collapse can be avoided.
50%UnverifiedHardware-first testing pattern: test on real hardware (1024×768 warehouse terminals, shared tablets with cracked-screen protectors, industrial touchscreens with 40ms input latency, warehouse on-site networks) before UAT rather than after.
50%UnverifiedTask-based launchpad design pattern: interview three users per role, have them describe a day's work in chronological order, map the launchpad to that narrative, and name apps with verbs rather than nouns (e.g., Check Expected Deliveries rather than VL06I - Inbound Delivery Monitor).
50%UnverifiedThe author proposes a two-minute test: whether a non-SAP user can, on real hardware, without help, on the first attempt, complete the most common daily task within two minutes; accompanying checks include cold-start task completion, all tile names using verbs, and at least three real end users having tested on production hardware before UAT sign-off.
50%