For any consumer-facing product, there is always a need of UI / graphics/presentation to show its usage. As more and more such products/services are being web onboarded, the website becomes an integral part of their product purchase life cycle.
Similar to selling something physically where in one would describe the product and guide the probable consumer towards closing a sale, a website too should be capable enough to guide the user to consume what it is trying to convey. Here is where user stories become important. So first thing always is to see what we wish to convey and make a measure of the number of user interactions that would lead to achieving it.
Having said this, first and foremost emphasis comes on how long it takes to convey feedback/response to every interaction done by the user. It is like if you go to the shop and ask for something and the salesman responds with:-
- a nod,
- a yes sir or no sir,
- can I get more info etc .
Now imagine if it takes too much time to get the above responses, the user may try to browse away to another salesman a couple of times and if that is the general behavior he would exit out of the shop or in our case a website.
Now you see how important is response time during the digital journey. Many websites makes a list of past user interactions and keep the next available interactions at a low latency location, it can be gif/png in the browser cache, a browser script or …
To be continued
