|
5 | 5 | --- |
6 | 6 | # 3.3 - Needfinding and Requirements Gathering |
7 | 7 |
|
| 8 | +> Try to find out what the user really needs. |
| 9 | +
|
| 10 | +- defining questions about the user |
| 11 | +- generating answers about the user |
| 12 | +- formalizing models of the user |
| 13 | +- data inventory |
| 14 | + - who are the users? |
| 15 | + - where are the users? |
| 16 | + - what's the context of the task? |
| 17 | + - what are their goals? |
| 18 | + - what do they need? |
| 19 | + - what are their tasks? |
| 20 | + - what are their subtasks? |
| 21 | +- the problem space |
| 22 | +- user types |
| 23 | + - adults |
| 24 | + - professionals |
| 25 | + - hobbyists |
| 26 | + - gym rats |
| 27 | + |
| 28 | +## Avoiding Bias in Needfinding |
| 29 | + |
| 30 | +- confirmation bias |
| 31 | + - "We see what we want to see." |
| 32 | + - looking for signs that you're wrong |
| 33 | + - testing beliefs empirically |
| 34 | + - involve multiple people |
| 35 | +- observer bias |
| 36 | + - we might accidentally phrase questions in a way that elicits the responses we're hoping for |
| 37 | + - separate experimenters with motives from the participants |
| 38 | + - heavily script interactions with the users |
| 39 | + - have someone else review interview scripts and surveys for leading questions |
| 40 | +- social desirability bias |
| 41 | + - people tend to be nice, people want to help |
| 42 | + - hide what the socially desirable response is |
| 43 | +- voluntary response bias |
| 44 | + - people with strongest opinions are often the loudest responders |
| 45 | + - we risk oversampling extreme views |
| 46 | + - limit the amount of content available before they view the survey |
| 47 | + - confirm conclusions with other methods |
| 48 | +- recall bias |
| 49 | + - people aren't good at recalling what they did/felt |
| 50 | + - study tasks in context |
| 51 | + - conduct interviews during task itself |
| 52 | + |
| 53 | +## Observation |
| 54 | +### Naturalistic Observation |
| 55 | +> Observing people in their natural environment. |
| 56 | +
|
| 57 | +quick tips |
| 58 | +- take notes |
| 59 | +- start specific, then abstract |
| 60 | + - individual actions first |
| 61 | + - generalize later |
| 62 | +- spread out your sessions |
| 63 | + - shorter sessions are better |
| 64 | +- find a partner |
| 65 | +- look for questions |
| 66 | + |
| 67 | +### Participant Observation |
| 68 | +> Try putting yourself in the shoes of the user. |
| 69 | +
|
| 70 | +- you are not your user |
| 71 | +- don't overrepresent your own opinions and experiences |
| 72 | + |
| 73 | +### Hacks and Workarounds |
| 74 | +> look at the hacks that users presently employ |
| 75 | +
|
| 76 | +### Errors |
| 77 | +> We can use errors to learn about a users mental model. |
| 78 | +
|
| 79 | +Looking for mistakes made by the user can be useful. |
| 80 | + |
| 81 | +### Apprenticeship Approach |
| 82 | +> We might need to become experts ourselves in order to build prototypes. |
| 83 | +
|
| 84 | +- integrate yourself into the domain |
| 85 | +- train under your users |
| 86 | + |
| 87 | +### Interviews and Focus Groups |
| 88 | +> Asking your users for feedback directly. |
| 89 | +
|
| 90 | +- Focus on the 6 W's (who, what, when, where, why, how) |
| 91 | +- Be aware of bias. Don't predispose the user to say what you want them to say. |
| 92 | +- listen. Participant should do vast majority of the talking |
| 93 | +- organize the interview |
| 94 | + - introduction |
| 95 | + - ... |
| 96 | + - summary |
| 97 | +- practice |
| 98 | + - rehearse your questions |
| 99 | + |
| 100 | +### Think-Aloud |
| 101 | +- give interviewees voice recorders |
| 102 | +- this is significant observation, may affect user behavior |
| 103 | + |
| 104 | +### Surveys |
| 105 | +- larger, quicker responses |
| 106 | +- low cost |
| 107 | +- quick setup and turnaround |
| 108 | +- not as thorough as in-person interviews |
| 109 | +- tips |
| 110 | + - less is more (minimum number of questions. questions should be easy to respond to) |
| 111 | + - be aware of bias |
| 112 | + - tie questions to the data inventory |
| 113 | + - test out the survey |
| 114 | + - iterate |
| 115 | +- good questions |
| 116 | + - be clear |
| 117 | + - make sure user understands what you're asking |
| 118 | + - avoid overlapping ranges |
| 119 | + - provide extra detail when in doubt |
| 120 | + - timebox frequency-based questions |
| 121 | + - at odds with "be concise" |
| 122 | + - be concise |
| 123 | + - ask questions in plain language |
| 124 | + - at odds with "be clear" |
| 125 | + - be specific |
| 126 | + - avoid questions on super big ideas |
| 127 | + - avoid "double-barrel" questions (questions that can be rephrased as 2 questions) |
| 128 | + - avoid questions that allow internal conflict (questions that have nuanced answers should be broken up into smaller, more specific questions) |
| 129 | + - be expressive |
| 130 | + - emphasize the user's opinions |
| 131 | + - use ranges instead of yes/no questions |
| 132 | + - give levels of frequency or agreement |
| 133 | + - allow multiple selections when possible |
| 134 | + - allow users to add nominal categories |
| 135 | + - be unbiased |
| 136 | + - allow users to add nominal categories |
| 137 | + - see above for more tips on reducing bias |
| 138 | + - allow for open-ended responses |
| 139 | + - avoid leading questions |
| 140 | + - avoid loaded questions |
| 141 | + - be usable |
| 142 | + - provide a progress bar |
| 143 | + - don't make it too long |
| 144 | + - make your page lengths consistent |
| 145 | + - order questions logically |
| 146 | + - alert users about unanswered questions |
| 147 | + - don't force users to answer all questions |
| 148 | + - preview the survey yourself |
| 149 | + |
| 150 | +### Other Data Gathering Methods |
| 151 | +- critiquing existing interfaces |
| 152 | +- go look at product reviews |
| 153 | +- get some logs of user interaction that have already been aggregated |
| 154 | + |
| 155 | +## Iterative Needfinding |
| 156 | +![[Pasted image 20250515234341.png]] |
| 157 | + |
| 158 | +- Draw double-ended arrows between all pairs of nodes |
| 159 | + |
| 160 | +## Revisiting the Inventory |
| 161 | +- pay attention to places where the data seems to conflict |
| 162 | +- revisit these questions |
| 163 | + - who are the users? |
| 164 | + - where are the users? |
| 165 | + - what's the context of the task? |
| 166 | + - what are their goals? |
| 167 | + - what do they need? |
| 168 | + - what are their tasks? |
| 169 | + - what are their subtasks? |
| 170 | + |
| 171 | +## Represent the need |
| 172 | + |
| 173 | +![[Pasted image 20250515234612.png]] |
| 174 | + |
| 175 | +![[Pasted image 20250515234627.png]] |
| 176 | + |
| 177 | +## Define our Requirements |
| 178 | +- functionality |
| 179 | +- usability |
| 180 | +- learnability |
| 181 | +- accessibility |
| 182 | +- compatibility |
| 183 | +- compliance |
| 184 | +- cost |
| 185 | +- ... |
0 commit comments