SAUG Melbourne Conference, Nov 2015
"A person's perceptions and responses that result from the use or anticipated use of a product, system or service"
Ergonomics of human system interaction, ISO 9241-210
"In the enterprise world, 70% of apps that are deployed are not adopted (per Forrester research) as they are difficult to use. "
"Forrester research states that 93% of Line of Business and IT Executives rate user experience as a top strategic priority. "
But navigating your SAP UX options is NOT easy
... or simple
Understanding the geological layers of SAP's UX history
Note: Here we refer to the current era as the 'Fiori Era' rather than the 'HANA Era' because this is after all a presentation about UX. ☺
Over two decades SAP has introduced progressive evolutions in design concepts and tools to enrich the UX
ALL these design concepts and tools can co-exist as layers in a modern SAP system
So what's the problem?
PROBLEM #1: Many people continue to implement SAP at the oldest layer, because that's what they are familiar with
PROBLEM #2: Any one of those layers could be described as 'Standard SAP'
And quoted as 'Best Practice'
PROBLEM #3: Skills and knowledge inertia inhibit adoption of modern SAP technologies to enrich UX
Who knows what Web Dynpro era apps are available? Who knows what standard Fiori apps are available? Who's going to design my custom Fiori app? And who's going to build it?
PROBLEM #4: So consultants defer to their old tried and tested UX options (eg. 1990s SAP GUI) because it's easier for them to implement ... but not necessarily for the end user to use
PROBLEM #5: Users don't realise what layer they are getting. Until it's too late.
Welcome to SAP GUI
Nearly 90% reported using SAP GUI as the primary means to access SAP
But when asked what they'll use in the next two years ...
Nearly 64% said Fiori Launchpad
We are in the midst of potentially tectonic shifts in the way we deliver UX to SAP users.
But firstly, let us better understand the more important user interface (UI) technologies ...
UI technologies guidance: SAP CLASSIC DYNPRO
R/3 Era - 1990s SAP GUI
UI technologies guidance: SAP WEB DYNPRO
(WDA / FPM / POWL)
NetWeaver Era - 2000s
UI technologies guidance: SAP SCREEN PERSONAS
Modern Era - 2010s
UI technologies guidance: SAPUI5 (basis for Fiori Apps)
Modern Era - 2010s
Each UI technology can be surfaced via one or more access points
*Important: Even though an access point can support multiple device types, the underlying UI technology might not. Eg. SAP does not support SAP Web Dynpro surfaced via the Fiori Launchpad access point when accessed via a mobile device.
Sample Combination A:
Sample Combination B:
... and many more combinations are possible.
Although our interpretation of SAP's current strategy is that the long term architecture should look something like this ...
Enough about technologies and toolsets.
What can we do better?
RECOMMENDATION: Adopt a 'Next Generation First' methodology to choosing your UX layer per app, not a 'SAP GUI Only' approach.
Apply pragmatism to your approach.
A COMMONLY USED EXCUSE not to apply this methodology:
"But our access point to SAP is SAP GUI, so everything needs to be built as SAP GUI transactions"
Hence the need for an 'access point enabler' that supports multiple layers of technological evolution simultaneously, such as SAP Business Client (formerly NWBC).
NWBC can support Fiori launchpad, along with Web Dynpro applications and older native SAP GUI dynpro applications
RECOMMENDATION: Formulate a UX strategy that makes sense for your users and your technology preferences
Include some allowance for bespoke custom development or 'best of breed' solutions for high value or key scenarios
RECOMMENDATION: Like SAP itself, embrace the principles behind
Image courtesy of createdu.org
Incorporate some allowance for specialist UX design into your methodology rather than relying on developers
Ratio of DESIGNERS to DEVELOPERS:
|Software industry 'ideal' *||1:10|
|Typical customer ratio||0:N|
* Source: SAP TechED Las Vegas, UX160
Listen to users. Embrace 'empathy'.
SAP consultants have worked with SAP GUI screens for decades and know them intimately. But users may not. See the world through your users' lens.
We need to rewire our Mindset
Think about the Next Generation of users - the 'Millennials'
Do we seriously expect them to remember transaction codes?
To be taken to this ...
Instead, let us aspire to provide them this ...
RECOMMENDATION: Methodologies and toolsets help, but mindset matters most. Assemble a Next Generation team with the right mindset and skills.
In this modern era, we need to elevate UX to the forefront of what we do in our design and delivery of SAP solutions
SAP implementions or IT support organisations should strive to deliver a NEXT GENERATION SAP solution
... not a 1990s solution based on old practices, methodologies and mindsets
lifeSAP, Jim but not as we know it."
Find this presentation at
+61 403 197727