You are able to break down a complicated issue into broader categories or more specific, focused categories. It can add structure to a large or complicated issue. It also allows for quick data analysis once the study is complete (see step 7). They can look at the physical diagram to see evolving trends, as well as individual pieces of data. There are many situations when an affinity diagram is an appropriate and useful analysis method: ■Īn affinity diagram is an excellent method for sharing the results of your study with stakeholders as the study progresses. Note that at this level, requirements can be a mix of interaction and functional requirements. To clarify with a small example from MUTTS and the Ticket Kiosk System, a WAAD note, say in node C19, that says “I am concerned about security and privacy of my transactions” can imply a design requirement (at a high level): “Shall protect security and privacy of ticket-buyer transactions.” In the design, this requirement might be at least partially met by a timeout feature to clear the screen between customers. The conclusion of this syllogism is a statement of user needs and requirements you deduce from the work activity note, something we capture in a “requirement statement.” The second “premise” is everything you know about UX and interaction design.

It is deductive because each work activity note in the WAAD is treated as the major premise in a logical syllogism. Pyla, in The UX Book, 2012 5.3.2 Switching from Inductive to Deductive ReasoningĮxtracting requirements from the WAAD calls for a deductive thinking process.

Extracting Interaction Design Requirements

Affinity diagrams