Lean and UX

819 views

Published on

Presentation from a talk I gave at UX Brighton. There were a bunch of other folks talking on the same night about other aspects of meshing / mashing UX into Agile projects, so this one focusses a bit more on how you can do Lean UX (a little).

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
819
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Lean and UX

  1. 1. lean uxwhat that means for us…for UX Brighton, 8 March 2011
  2. 2. hello…i used to work in an“advertising” agency § off-site § creative first or § ux firstnow, I help buildsoftware for finance § on-site § delivery driven 2
  3. 3. just enough / good enough§ good enough § generically across the project§ just enough § personas (and their use in stories) § sketching and documentation § design§ the end product 3
  4. 4. good enoughdefine your quality very satisfiedstandards§ what does done look performance like? excitement§ does the kano model have some answers? fail win hygiene very dissatisfied 4
  5. 5. good enoughdevelopment qualityis easy(ish) to define§ what are the coding standards§ what is acceptable (bug wise) 5
  6. 6. good enoughcreative quality?§ whatcreative standard are we striving to achieve (chevrolet, toyota, porsche, audi ferrari…) 6
  7. 7. good enoughinteraction quality?§ what level of “usability” is good enough 7
  8. 8. just enough / good enough§ good enough § generically across the project§ just enough § personas (and their use in stories) § sketching and documentation § design§ the end product 8
  9. 9. Personaswhat is appropriate§ generic library§ “sketch”§ primary / secondary FX ONLY :: LAB49 IN TERNAL DI STRIBUTIO N ONLY City Perso nas EDITION 1 9
  10. 10. personasthen use them!§ as[persona…], I want to [goal…], so that [reason] FX ONLY :: LAB49 IN TERNAL DI STRIBUTIO N ONLY§ mostuse: “as a user I…” City Perso nas§ use your personas EDITION 1 “as bob jones, I…” “as bob, mary or fred, I…” 10
  11. 11. just enough / good enough§ good enough § generically across the project§ just enough § personas (and their use in stories) § sketching and documentation § design§ the end product 11
  12. 12. interface states and event-based user actions. Through a few simple and standardized rules, what the user sees (drawn in greys and blacks) and does (drawn in red) are unified into a coherent sketching system. This unification of both interface and use, intends to enable designers to tell more powerful stories of interaction.sketching and documentation Events Events are initiated when users perform Unspecified Event. A simple arrow that Event Binding To Element. A rounded various actions on an interface. Think of represents a CLICK action by default. starting point denotes events as causes and screens as effects. For an event bound to a par-does anyone like the purpose of this notation, some relevant events could include: Specific Event. To represent a user action with an event, note it above the ticular drawn element. CLICK FOCUS arrow. To Anywhere. An eventproducing documents DBLCLICK RCLICK BLUR KEY: X Combined Events. Sometimes users is attached to the full window. MOUSEOVER KEYUP: X perform more complex actions such asthat don’t get read? MOUSEOUT MOUSEMOVE KEYDOWN: X LOAD holding a key and clicking. To Area. An event is MOUSEUP UNLOAD Real World Actions. User actions can also bound to a specific area§ canyou get away with MOUSEDOWN SCROLL happen outside of an interface. on the screen. CHANGE SUBMIT just sketches… Transitions Emphasis Techniques Page Organization Unspecified Transition. A default Emphasis. Indicating Concept Title. Each page transition is instant without delay. an important element can contain a title in the with a 10% grey. top left. For multi-page Delay. The time it takes before a concepts, use roman transition starts. numerals as a suffix. Selected State. Variations. Each concept Duration. The time it takes for a Showing a selected can have multiple varia- transition to complete. item with a 30% grey. tions which are referred to alphabetically. Effect. Two possible effects include: FADE, and SLIDE. Advanced Notations Rapid Tactics Basic Condition. If something is to Drag&Drop. Quickly Delta Box. Only draw items be met before the next screen. show a drag and drop which changed, suggesting interaction. that previous screen ele- Automatic Sequence. Use a black ments will also appear. arrow(s) if there is a sequence of screens that are shown automati- Multi Clicks. Use the Zooming. Draw atlinowski least 12
  13. 13. sketching and documentation§ we have, but only under in certain conditions§ whensketches don’t work we spike prototypes - sometimes within the app!§ requirements are “acceptance tests” 13
  14. 14. just enough / good enough§ good enough § generically across the project§ just enough § personas (and their use in stories) § sketching and documentation § design§ the end product 14
  15. 15. designa beautiful photoshopfile… 15
  16. 16. designbut, the application… 16
  17. 17. finally…§ if phase 2 happens, how much of your detailed ux work will actually get used, or (realistically) will it all be changed again based on new things you’ve learnt - if so - why do it?§ thank youmark@found.me.uk@uxplant 17

×