Three Ways to Get your Organization Moving with SAP Fiori

[peterbrasket]

Wednesday, December 2, 2015

Three Ways to Get your Organization Moving with SAP Fiori

SAP Fiori is here to stay.  Even Gartner has observed that "Fiori UX is unlike any UX initiative undertaken by SAP".

So how do technology leaders begin socializing Fiori with business users, and prioritize adoption against everything else going on? Short of standing up Fiori and creating apps as an initial engagement, here are three easy ways we have seen clients ease into their Fiori journey: 

1) Host a Lunch & Learn around Fiori/UX:  this is the easiest way to get the discussion started.  A typical 45-minute agenda would include:

• Greetings by a senior sponsor
• Introduction to Mindset (if we're leading the L&L)
• Fiori Overview - why it matters, business value it drives
• Standing it Up (pre-determine if you will cover either ECC or HCP approach)
• Fiori/UX Decision tree (when to adopt Fiori vs. Personas or other...)
• Case Study & Impact (Mindset has several industry-level examples)
• Q&A

2) Pilot a Fiori Design Thinking Workshop: With the general tenets of Fiori understood, introducing a proven process to ensure great UX, better user adoption, and faster time-to-value is a natural next step. This approach also builds good credibility with business users given the empathy and sincerity inherent in the process.

Hosting a Design Thinking Workshop to migrate an app to Fiori is both a great POC and a very easy process:

• Pre-Workshop review of business issue and app(s) to be considered - usually takes 2-3 hours
• Design-Thinking Workshop (usually four hours for an application)  - includes design, ABAP, architecture, business users;
• Post-Workshop - high fidelity screens are delivered

3) Fiori Training & App Dev Program: We learn by doing. In fact we learn BEST by DOING (see i.e. Hackathorn, et al). When we deliver our hands-on, one-week training we not only dive deeply into Fiori readiness, processes, & skills...but we also create an app with the team as our learning artifact. We typically cover the following elements, but you can tweak the contents to match your readiness:

• Pre-Training review of business issue and app(s) to be considered, along with architecture and Fiori readiness (i.e ECC-based, HCP-based, etc).
• Design-Thinking Workshop (usually four hours for an application)
• App dev and training, including:
  • Fiori Platform
  • NetWeaver/Gateway Overview
  • WebIDE v. Eclipse Tools
  • Service Development Overview
  • Advanced OData Features
  • Service Generation
  • UI5 and UX
  • Security
  • Mobile Client Extensions
• Post-Training Support to help transport app to i.e. QA/Prod

We find that two strong Fiori SMEs can facilitate up to 12 attendees over a five-day core learning and dev session. Complementing the two leaders would be specialists for 2-3 hour mini breakouts - i.e. Designing, PM best practices, etc.  

And because you are creating a Fiori app, the deliverable is not just skill acquisition and process/template creation, but an actual app you can bring to production or leverage as a POC as appropriate.

Your Fiori/UX journey will reflect your organization's culture and priorities, but every journey begins with a single step; is one of these initiatives a good starting point for your constituents?