PUBLIC
User Experience Strategy Template
Date Description
September 29, 2021 New document - Initial version
TABLE OF CONTENTS
WHO WILL CHANGE – OUR USER EXPERIENCE(UX) ROADMAP.............................................................3
WHAT WILL CHANGE – HOW WE ENVISION THE FUTURE AND SELECT OUR UX.................................5
Guiding principles for selecting UX.............................................................................................................. 5
Process for selecting UX............................................................................................................................... 5
UX Value Goals............................................................................................................................................... 6
HOW WE WILL CHANGE – PRINCIPLES, PROCESSES, PEOPLE, TOOLS...............................................8
Guiding principles for realizing UX............................................................................................................... 8
Technical Considerations.............................................................................................................................. 8
Processes for realizing and supporting UX.................................................................................................9
General UX capabilities approved for use.................................................................................................. 10
Capabilities NOT approved for use............................................................................................................. 11
Tools approved for use................................................................................................................................ 11
Tools NOT approved for use:...................................................................................................................... 11
Role Owners: Final approvers for role changes........................................................................................ 12
DECISIONS MADE........................................................................................................................................ 13
OPEN ITEMS AND NEXT STEPS.................................................................................................................. 13
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.
WHO WILL CHANGE – OUR USER EXPERIENCE(UX) ROADMAP
<In this section you describe:
The high-level roadmap for change
How the roadmap aligns to business strategic/tactical outcomes
Who is responsible, accountable, consulted and informed in any decisions about the UX roadmap?
How you will get to know your users, i.e., what approaches will you use to confirm the current state
of these users, such as User Surveys, Site Visits, Usability Studies, Interviews with
Champion/Power users. For example, to discover/confirm:
o Casual vs expert usage of system
o Device types used and are devices self-owned or company provided
o Working context – e.g., office work, work from home, travels from site to site, factory worker,
etc.
o Work wear – especially helmets, gloves and other gear that may impede use of devices
o Main tasks and activities – on and off system, especially include off system tasks that slow
down or complicate tasks, e.g., having to go to a website to look up a reference number
o Current pain points, challenges, and desires for UX, for example “I like, I wish” – what works
that you don’t want to lose, what doesn’t
o Parallel/upcoming initiatives or other business circumstances that affect the timing of
introducing new change>
UX Roadmap summary:
3
UX Roadmap detail:
<EXAMPLE>
Wave Focus users for Primary UX Value Goals Alignment to Business
new UX Outcomes
1 Finance Be more INSIGHTFUL - provide real- Manage our costs better. Avoid
Specialist time insights and analytics expense leakage.
2 Retail Staff Be more MOBILE – provide standard Serve our customers better
Member and custom apps that can be used on
tablets and smartphones within our
stores
3 Procurement Be more PROACTIVE and REACT Minimize spend overruns and
Officer faster – use embedded machine reduce supplier shortfalls
learning and situation handling to
speed up response to supplier delivery
situations
4 Customer Call RESPOND faster – be able to react as Improve efficiency of the call
Center quickly as possible to customer center to serve our customers
queries better
5 TBC Look for other opportunities Review strategy needs with
COO/CIO
Link to RACI matrix of:
COO
CIO
Business Role Owners
Business Process Experts
Enterprise Architect / Technical Advisor
UX Architect/Advisor
UX/UI Development team
IT Administrator and Support
4
WHAT WILL CHANGE – HOW WE ENVISION THE FUTURE AND SELECT OUR UX
<In this section you describe:
The decision process for envisioning future UX changes
Persons responsible for and participants in deciding on potential changes
Guidelines and success criteria
Who is responsible, accountable, consulted and informed to review selected apps and features?
>
Guiding principles for selecting UX
The following guiding principles should be followed:
Principle 1: xxx
Principle 2: xxxx
Principle 3: xxx
xxxx
Process for selecting UX
<The overarching process is as follows:
Business process expert determines the roles/UX Value goals in scope in consultation with...
o Workshop held with business user representatives to discuss tasks, pragmatic day to day
Finalizing app selection
o UX Architect/Advisor and Business process expert review available apps and select suitable
apps for exploration
o IT team rapidly activate the related SAP business roles in sandbox for exploration
o UX Architect/Advisor and Business process expert explore apps for fit
Playback walkthrough with ...
After review
o Selected apps are flagged for inclusion in custom role
o WRICEFs created for any apps that require enhancements
o Any proposed custom apps are submitted for approval
Design your launchpad layout workshop scheduled with business users
o Prototype provided
Move to realization
>
5
UX Value Goals
6
7
HOW WE WILL CHANGE – PRINCIPLES, PROCESSES, PEOPLE, TOOLS
<In this section you describe:
Processes, persons involved, and tools used to realize changes
Guiding principles for realizing changes
Cross References to technical documents and resources needed
General UX capabilities approved/not approved for use
Tools approved/not approved for use
>
Guiding principles for realizing UX
The following guiding principles should be followed:
Xxx
Xxxx
xxxx
Technical Considerations
The following access channels are supported:
User access channel Purpose Technical Comments
Contacts
Entry via SAP Fiori General use on desktop and xxx No restrictions
8
launchpad on web mobile devices
browser
Entry via SAP Fiori + GUI for Windows xxx Permitted by exception:
Business Client Heavy data entry users
Launchpad only or for users using
Connection transactions with
Windows Graphical
Editors where there is
no Fiori equivalent
SAP GUI for Windows GUI only xxxx Permitted for users who
do not have any SAP
Fiori apps yet
Where apps are to be used on mobile devices, consult our Mobility Strategy.
For any developer extensions or custom-build of new apps, consult our UI Design and Development Strategy
and Development Guidelines.
Processes for realizing and supporting UX
The following processes for realizing UX are supported:
Process Purpose Process Comments
Contacts
Activating SAP Review as-delivered role for fit- <Contact Use rapid activation
Business Roles to-standard exploration Name/Team> approach in Sandbox
only.
Create/maintain Add selected apps and UIs to <Contact Use content activation
custom business custom business roles for Name/Team> task list in Development
roles (including app transport
to app navigation)
Create/maintain Create or adjust the launchpad <Contact Done in development
launchpad layouts for space for a role, e.g. add new Name/Team> using SAP Fiori apps
roles page, change sections or tiles
assigned
Activate launchpad Enable/disable cross-functional <Contact Check first for
features features or behaviors Name/Team> Launchpad
Configuration
Parameters
Adapt apps (in-app Make common changes within <Contact To be executed in
extensions) SAP Fiori, such as Adapt UI. Name/Team> development, tested in
Refer to our SAP Fiori QA before transport to
Adaptation Guide production
Extend apps Refer to our UI Design and <Contact Requires approval
(developer Development Strategy Name/Team>
extensions)
Custom build of new Refer to our UI Design and <Contact Requires approval
apps Development Strategy Name/Team>
Patching of SAPUI5 <Contact
version Name/Team>
Patching of Kernel <Contact
version Name/Team>
Patching of Unified <Contact
Rendering release Name/Team>
Adding FLP plug-ins <Contact Requires approval
Name/Team> except for these plug-
ins:
App Support
User
Assisstance
Changing FLP <Contact
9
configuration Name/Team>
parameters
General UX capabilities approved for use
The following UX capabilities may be used:
Tool Purpose Support Comments
Contacts
Search on Apps Search for apps, transactions, xxx No restrictions
etc.
Search on business Search across business objects xxx Look to limit the search
objects objects assigned to a
user via authorizations
- aim for approx. 10
main objects per usre
Notifications in the Notifications generally No restrictions
Launchpad supported for processes,
workflow, situations, KPIs
Notifications via email User can opt to receive No automatic send to
notifications via email in User email
Actions > Settings NOTE: Email address
must be stored in the
user master
App Finder Find all your apps No restrictions
User Menu/SAP Menu Find GUI transactions via SAP Supported for expert
Menu users and
administrators. Not to
be given to casual
users.
User Assistance Help on apps Standard delivered help
only
Spaces and Pages Organize launchpad layout of No restriction on usage.
most important/most frequent Refer to
apps recommendations re
launchpad layout when
creating new
spaces/pages
App to App Navigate between apps and No restrictions.
Navigation UIs Additional navigations
can be added by
launchpad content
administrator and
require authorizations
to be assigned
Integration of SAP Launch directly to SAC story No restrictions
Analytics Cloud
Stories
Tiles/links to URL E.g. to approved Cloud apps, No restrictions
sites internal policy sites, etc.
App Support For diagnosing issues in the No restrictions
FLP
10
Capabilities NOT approved for use
The following capabilities are known but NOT supported.
These may be considered for future waves pending a decision review
UX capability Purpose Decision Comments
contacts
Notifications via User can opt to receive Requires email
email notifications via email in address to be
User Actions > Settings maintained in user
master
Push notifications Receive push notifications Requires additional
on mobile devices on device subscription in SAP
BTP – currently
under consideration
Groups Organize tiles/links by tabs To be deprecated in
future releases. No
custom group are to
be created.
Any changes must be notified to the responsible person for the following:
<List any cross references that need to be kept in sync, e.g.
User Master data and Identity Authentication strategy – Email requirements, Access channel requirements
Security Roles Strategy>
Tools approved for use
The following tools may be used:
Tool Purpose Support Contacts Comments
Rapid Activation task
list
Content Activation
task list
Launchpad Content
Manager
Launchpad App
Manager
SAP Fiori apps
Manage Launchpad
Spaces and Manage
Launchpad Pages
ABAP SAPUI5 upload For patching
patch program
Tools NOT approved for use:
The following tools must NOT be used:
Tool Purpose Tool Support Comments
Contacts
Launchpad Maintain catalogs To be deprecated.
Designer and groups Instead use
Launchpad content
manager, launchpad
app manager, or SAP
Fiori apps Manage
Launchpad Spaces
and Manage
Launchpad Pages
LPD_CUST Create URL links Deprecated
11
Refer to blog post: SAP Fiori for SAP S/4HANA – Overview of tools for maintaining custom launchpad
content and layout
Role Owners: Final approvers for role changes
Role Owner who approves any changes specific to the business role.
<This can also be held as a separate linked matrix e.g., if there are a large number of roles>
Role Name ID Role Owner Comments
Analytics Specialist
General Ledger
Accountant
Purchase
Sales Manager
12
DECISIONS MADE
<In this section you record any decisions made
>
Decision on Decision Date Yes/No/Yes with Changes/Comments Next review
Changes criteria
OPEN ITEMS AND NEXT STEPS
<In this section you record any open items and next step actions
>
Decision on Decision Date Yes/No/Yes with Changes/Comments Next review
Changes criteria
13
