personas,-scenarios,-and-use-cases.html (7114B)
1 <html> 2 <head> 3 <script src="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.15.6/highlight.min.js"></script> 4 <script type="text/javascript" async src="https://cdn.jsdelivr.net/gh/mathjax/MathJax@2.7.5/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script> 5 <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.15.6/styles/default.min.css"> 6 <link rel="Stylesheet" type="text/css" href="style.css" /> 7 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 8 <script> 9 document.addEventListener('DOMContentLoaded', function() { 10 document.querySelectorAll('pre.code').forEach(function(item) { 11 hljs.highlightBlock(item) 12 }) 13 }); 14 </script> 15 <title>personas,-scenarios,-and-use-cases</title> 16 </head> 17 <body> 18 <style type="text/css"> 19 nav a { 20 text-align: left; 21 } 22 nav #name { 23 text-align: right; 24 float: right; 25 font-style: italic; 26 } 27 </style> 28 <nav> 29 <a href="index.html">Index</a> 30 <span id="name">Alex Balgavy</span> 31 </nav> 32 <hr> 33 <div class="content"> 34 35 <div id="Personas, Scenarios, and use cases"><h2 id="Personas, Scenarios, and use cases" class="header"><a href="#Personas, Scenarios, and use cases">Personas, Scenarios, and use cases</a></h2></div> 36 <div id="Personas, Scenarios, and use cases-Goal directed design"><h3 id="Goal directed design" class="header"><a href="#Personas, Scenarios, and use cases-Goal directed design">Goal directed design</a></h3></div> 37 <p> 38 Design activity that links requirements to implementation (what do you need, why? what are you solving?) 39 </p> 40 41 <p> 42 Generally, you have marketers, decision makers, and developers making decisions, and the result is shit. 43 What's missing is the user's perspective: goals, actions, motivations, responses, and the context (how it fits into the user's wider activities) 44 </p> 45 46 <p> 47 Design interactions - mental models 48 The user's mental model is not the implementation model, the user has to adapt to understand the implementation. 49 It's better if design model is good fit for user model (unless it hides important features) 50 </p> 51 52 <p> 53 Steps in design process: 54 </p> 55 <ul> 56 <li> 57 Research users: observation, interview, etc 58 59 <li> 60 Discover non-user goals (business, technical, whatever else) 61 62 <li> 63 Develop personas 64 65 <li> 66 Use personas in scenarios to establish design requirements 67 68 <li> 69 Find the functional requirements - use cases 70 71 </ul> 72 73 <p> 74 Users react to a product on 3 levels: 75 </p> 76 <ul> 77 <li> 78 Visceral - the user's <em>immediate</em> reaction before even using the product, should trigger emotional responses that are appropriate 79 80 <li> 81 Behavioural - we need design that fits where the user currently is with knowledge, assumptions, and mental models 82 83 <li> 84 Reflective - integrating product and its values into wider life, and if done well, you get brand loyalty 85 86 </ul> 87 88 <p> 89 User goals: 90 </p> 91 <ul> 92 <li> 93 Experience: how the user wants to feel (visceral) 94 95 <li> 96 End goals: what the user wants to do 97 98 <li> 99 Life goals: who the user wants to be 100 101 </ul> 102 103 <p> 104 Non-user goals: 105 </p> 106 <ul> 107 <li> 108 Customer goals (the customer is <em>not</em> the user, like corporate IT buyers) 109 110 <li> 111 Business/organisational goals (increasing profit, market share, reducing costs, increase QOS) 112 113 <li> 114 Technical goals (maintaining security, cross-platformness, backwards compatibility) 115 116 </ul> 117 118 <p> 119 User stories & goals: 120 </p> 121 <ul> 122 <li> 123 As a <type of user> I want <some goal> so that <some reason> 124 125 <li> 126 As a <persona> I want <action> so that <expected outcome> 127 128 <li> 129 When <situation> I want to <motivation> so I can <expected outcome> 130 131 </ul> 132 133 <div id="Personas, Scenarios, and use cases-Personas - archetypal users"><h3 id="Personas - archetypal users" class="header"><a href="#Personas, Scenarios, and use cases-Personas - archetypal users">Personas - archetypal users</a></h3></div> 134 <p> 135 Modelling users: identify major goals and behaviours, then build models of idealised users ("personas") 136 </p> 137 138 <p> 139 There isn't an 'average user', you use personas that capture important characteristics of users. 140 </p> 141 142 <p> 143 Persona: 144 </p> 145 <ul> 146 <li> 147 Demographic details: name, occupation, age 148 149 <li> 150 Personal details: short biographical summary 151 152 <li> 153 Attitudinal details: mental model, pain points, feelings about stuff that has to be done 154 155 <li> 156 Goals and motivations: for using the product (maybe for life in general™) 157 158 <li> 159 Behavioural details: how they act when using the product 160 161 <li> 162 generally about half a page in length 163 164 </ul> 165 166 <p> 167 Why? 168 </p> 169 <ul> 170 <li> 171 Coordination, getting a shared vision of the users and market 172 173 <li> 174 Communication between devs, designers, marketers, other stakeholders 175 176 <li> 177 Determining functionality and behaviour o product 178 179 <li> 180 Help design decisions without testing on users 181 182 <li> 183 they work. you don't focus on edge cases but on normal use, avoids the self-referential user (developers thinking users are like them), and avoids the elastic user (cuz users won't bend to your will, they don't give a shit) 184 185 </ul> 186 187 <div id="Personas, Scenarios, and use cases-Scenarios"><h3 id="Scenarios" class="header"><a href="#Personas, Scenarios, and use cases-Scenarios">Scenarios</a></h3></div> 188 <p> 189 Informal narrative descriptions: 190 </p> 191 <ul> 192 <li> 193 describe human activities in short stories 194 195 <li> 196 You can explore needs, requirements, contexts 197 198 <li> 199 Don't explicitly mention tech 200 201 <li> 202 Are written in the users' language (well, english in our case) 203 204 <li> 205 Have varying levels of detail 206 207 <li> 208 You focus on the user's perspective 209 210 </ul> 211 212 <div id="Personas, Scenarios, and use cases-Design Requirements & principles"><h3 id="Design Requirements & principles" class="header"><a href="#Personas, Scenarios, and use cases-Design Requirements & principles">Design Requirements & principles</a></h3></div> 213 <ol> 214 <li> 215 Establish needs & goals 216 217 <ul> 218 <li> 219 what info do users need? 220 221 <li> 222 what capabilities? 223 224 <li> 225 what goals must be achieved (business, technical)? 226 227 </ul> 228 <li> 229 Brainstorm 230 231 <ul> 232 <li> 233 time-limited, like half an hour 234 235 <li> 236 write them <em>all</em> down 237 238 <li> 239 no criticism allowed 240 241 <li> 242 ideas are culled and refined later 243 244 </ul> 245 </ol> 246 247 <p> 248 Don't make the user feel stupid. 249 Define what the product will do before designing how. 250 </p> 251 252 <div id="Personas, Scenarios, and use cases-Use Case"><h3 id="Use Case" class="header"><a href="#Personas, Scenarios, and use cases-Use Case">Use Case</a></h3></div> 253 <p> 254 Focus on user-system interaction instead of user's task itself. 255 Describe processes as text or use case diagram 256 </p> 257 258 <p> 259 structure: 260 </p> 261 <ul> 262 <li> 263 users are actors - user types or categories 264 265 <li> 266 use case consists of: 267 268 <ul> 269 <li> 270 header: 271 272 <ul> 273 <li> 274 name of use case 275 276 <li> 277 goal of use case 278 279 <li> 280 scope and level use case is covering 281 282 <li> 283 preconditions 284 285 <li> 286 success/failure conditions 287 288 <li> 289 trigger that starts use case 290 291 <li> 292 notes on performance, frequency, etc. 293 294 </ul> 295 <li> 296 steps (each assumed to be successful): 297 298 <ul> 299 <li> 300 description narrative 301 302 <li> 303 variations 304 305 <li> 306 notes 307 308 </ul> 309 <li> 310 exceptions 311 312 <ul> 313 <li> 314 notation is per step 315 316 </ul> 317 </ul> 318 </ul> 319 320 </div> 321 </body> 322 </html>