Sunday, April 5, 2015

Blog #7 - Dilbert on Usability & Awesome paper prototype Video

This week, we will share a lighthearted take on how requirements gathering and paper prototyping are important to usability.

Dilbert always has a way of showcasing issues in an easy to understand format, through comic strips. In the following one, he is faced with an over-enthusiastic user who does not seem to know what he is doing.




User requirements gathering is an important part before embarking on process of designing. It allows the designer to understand the users, task and context.

However, this is not always easy as users may not be able to articulate their requirements clearly, if at all, as seen in the comic. It is of no use to the designer if there is a mega list of “four hundred features”. This does not help the designer to prioritise the features and even if he managed to fit everything into the design, it will not be meaningful. As mentioned by Dilbert in the comic, “no human would be able to use a product with that level of complexity”.

Sometimes, even if users managed to list out their requirements, they may not have thought through them in detail. Often, it is a case of “copy and paste”, referencing another product that might not reflect their actual needs. The requirements may also be ambiguous and contradictory - like “easy to use” - and does not serve to inform the design. How can four hundred features be any easy to use?
Ideally, requirements should state what the intended product should do in a specific and clear manner. It should also elaborate on the users, tasks to be performed, needs and goals, the functionalities and limitations of the system, and the context of use. Stakeholders should also be identified and involved in the requirements gathering process. A series of data gathering activities can be conducted. This is usually an iterative process. Interviews, Focus Groups, Questionnaires, Direct/Indirect Observation and Studying Documentation are some of the activities that can be carried out to collect relevant and appropriate data.

After gathering user requirements, one of the process of designing involves representing the ideas through paper prototyping, as seen in the following video.



This simple and cheap process allows designers to test out ideas to share with team members and stakeholders quickly. In the early stage of development, the more visual and hands-on approach allows them to see, hold, interact with the paper prototype as compared to just presenting the idea on screen or through a document. Some concepts may be better seen and experienced through paper prototypes, like how the user moves, collects and avoids items in the game, as seen below.


This is useful for communication, and encourages questions and reflection, which is important in design. It helps designers to explore alternatives and their suitability, and may even allow them to incorporate modifications on the spot.


Although tedious at times due to their iterative nature, user requirements gathering and paper prototyping are important in the design process involving usability. Getting the foundation right in the early stages by involving stakeholders and users would mean lesser cost incurred at later stages of development.