SAP Screen Personas: Myth vs. Truth – Part 1
This is part of a multi-part series addressing myths about SAP Screen Personas.
This myth probably originated with customers that were looking for a silver bullet to solve all of their SAP usability issues. It might have been fueled by someone that was very eager to please their stakeholders that have been complaining about the SAP user experience. The reality is that Personas is only one part of overall SAP UX (user experience) solution, albeit a major part.
Personas works only on Dynpro screens. This is the rendering technology used for the majority of SAP’s ERP (enterprise resource planning) screens. This means that Personas does not work on SAP SRM (supplier resource management), which relies on Web Dynpro, a different and newer screen rendering technology. It also does not work on SAP CRM (customer relationship management), which relies a third type of rendering technology. There are also several other rendering technologies that SAP has used over the years. But, the majority of user interactions with SAP rely on Dynpro screens. So, Dynpro screens play a major role in shaping user perception about the usability of SAP.
The Dynpro “limitation” still means that Personas works on over 10,000 distinct transactions that customers rely on to run their businesses. These screens appear across both industry and line of business solutions.
Many business users only access a few routine transactions such as requesting vacation or other leave, entering time sheets, submitting expense reports, or checking their paystub. Their needs are relatively modest and they may not need the full power of Personas. For them. SAP Fiori may be a better option.
So, will Personas solve all your user experience needs? Maybe; it depends on your needs.
In the next post, we will explore myth 2, about Personas performance.
Read the entire SAP Screen Personas Myth vs. Truth series
Myth 1 (this post)