Prioritization

In college, we are learning OOUX. System mapping comes first. How to start identifying objects in a system is the first question which I have in my mind. Infact, where to start. Why is system design done and getting executed? Very simple, just to hide the complexities of the processes and make users seamlessly glide through the entire flow efficiently. What to show, how to show, when to show the users is the real game.

Mapping down the entire system is important for us to not miss out on information, then playing around the piece of information is relatively easier than doing the other way round. A good life design has very nice systems in which every stakeholder is very much aware about how the system functions. Actors perform different actions when different objects trigger those actions. More cross-mappings(likings) are going to help improve accessibility and adaptability. Based on this likert scale, people prioritize what they want to do first. How to make this prioritization more wiser? By reducing the gap between different action’s likert values. Once we get the hang of our likings, we’ll eventually get the hang of our priorities, then it's just a trade between those priorities based on the goals. By this form of evaluation, we not end up taking subjective decisions while prioritizing, everything is objective with good emotional values attached to each of them.

Veekay