As one of the few SAP UX consultants working for the only SAP UX specialist consulting company (at least that I know of - if you work for one message me I would love to here from you), I have heard a lot about UX from SAP during the course of TechEd this year. However no one has yet to go into the real nuts and bolts or practical applications...how can I implement "design thinking" / ux process in my organzation? Seeing this need I have decided to write a blog series about real life SAP UX process and how we at User Euphoria work. This will include the process we follow, the tools we use, the user experience "laws" we follow (yes they are "laws"... well, really some basic observation of human behaviors) and finally some documents that you can use as templates to help get the UX process off the ground .
Here is a quick preview of some of the content I will be sharing:
Hicks Law
What is it?
The more choices we have the harder it is to make a decision
How this applies to UI design?
The more features we pack into a single screen the harder it is for a user to understand what the screen is for and where and how to take on that screen. To increase usability we need to reduce the cognitive load on the user, don't make them think hard.
Everyday application
Re-examine what fields are actually needed on your forms. Look at your interface are there particular pages with tons of links Show the screen to someone new who has not used it and ask the what it does can they tell what it is used for? Or is it cluttered with too much information to denote what the purpose of the page is
Further Reading?
http://en.wikipedia.org/wiki/Hick's_law
http://www.usabilityfirst.com/glossary/hicks-law/
http://uxdesign.smashingmagazine.com/2012/02/23/redefining-hicks-law/
Stay tuned for Part 2
