Time is "RIPE" for a new way of designing 'Smart' user interface
This blog is in the series of blogs around the "Smart" user interface and how the expectations from the users have been maturing over time.
I firmly believe that the Maslow's hierarchy of needs is very much applicable in the world of IT and software solutions as well. The only difference is that we are talking about "user needs" from "IT" perspective instead of "psychological" as proposed by the theory. The users till date have been able to meet their Physiological, Safety, Love/Belonging and Esteem needs. What they need now is the movement to the next level of "Self-Actualization" (and i can assure you this is level which beats itself as a certain level is achieved and we start looking at the next best).
I talked about some of the users' comments in my last blog and earlier on how it all started here. Having highlighted the need, the next step is to share the framework that we have developed to help our clients "extend" the current application features (till they become features of the product themselves) on a case-to-case basis.
Each of the "dimensions" which define the need for a "sensitive" response in the user interface are inter-related though not-necessary related in a hierarchy though they may look like at the onset (more details on it later, not covering that in this blog to avoid diversion from the main thoughts).
The RIPE Framework
This framework is nicknamed "RIPE" and you will soon see why! We have broken down the "Sensitive" paradigm of any User Interface into 4 parts based on the activity for which a user interface is needed -
The figure below explain the 4 components of RIPE by taking a simple example of a "Financial Journal Posting" process which a typical accountant will do for any kind of financial transactions. For e.g. - the user in a particular department may have bought some stationary for official work for 200 USD; the same has to be entered in the right category and the expenditure attributed to the right department. The diagram explains what the user interface can give at various stages/states and at various times of execution of the same cycle.
The figure is self-explanatory. It shows the same transaction happening across 2 different roles (accountant and approver) at 2 different times - one during the normal business cycle and one during the month-end closing process. The process steps maybe are same, but the treatment of states and the needs from the user interface are different as shown in the figure. This example was just to simply explain how powerful this framework can be in terms of its utility and can be applied to any role, process, stage, state or time. We have lot of exciting cases where we have used this in real-life scenarios. Please do contact me in case you need more information around this.
Long live "sensitive" user interface!
This blog is part of a 3 blog series around the "Sensitive" user interface. You can read the other 2 blogs here -
Part 1: When will my ERP experience be 'smarter'... the Time Sensitive Paradigm!
Part 2: Taking ahead the thought of "Sensitivity of User Interface " in packages