Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile/Lean/Rapid UX


Published on

4 things I learned last week @ AgileUX NYC 2012 and IxDA New York and NYC-CHI present: New and Up and Coming Rapid Wireframing and Prototyping Tools

Published in: Design, Technology
  • Be the first to comment

Agile/Lean/Rapid UX

  1. 1. AGILE/LEAN/RAPID UX 4 things I learned last week @ AgileUX NYC 2012 and IxDA New York and NYC-CHI Present: New and Up and Coming Rapid Wireframing and Prototyping ToolsCopyright © 2012 by IQ Agency
  2. 2. Make user research routine.Copyright © 2012 by IQ Agency 2
  3. 3. Make user research routine. • Interact with users often and continuously • Schedule weekly/biweekly routine meetings for user research/testing • Don’t make a big deal about it: last minute recruitment and test planning • Turn observations to recommendations quickly, avoid time intensive reportsCopyright © 2012 by IQ Agency 3
  4. 4. Visualize quickly.Copyright © 2012 by IQ Agency 4
  5. 5. Visualize quickly. • In a rapid timeline, the sooner ideas are visualized -> the sooner feedback returned. • Increased visual fidelity = greater understanding to clients and users. • How to visualize? A: sketches, wireframes, mockups, prototypes. • How much do you prototype? A: Enough to get your point across.Copyright © 2012 by IQ Agency 5
  6. 6. Shift from requirements to hypotheses.Copyright © 2012 by IQ Agency 6
  7. 7. Shift from requirements to hypotheses. • Requirements are dictated by the business and don’t give creative people a problem to solve. • Defining requirements is counterintuitive to the iterative and exploratory nature of design. • Hypotheses are assumptions framed as questions, which can be tested and validated.Copyright © 2012 by IQ Agency 7
  8. 8. EXAMPLE Requirement: Create an Internet Mouse that people can use when surfing the internet on their TV from their couch. Hypotheses: We believe that people will pay for a device that makes it easier and more fun to surf the internet from their living room couches in front of the TV. ... and: We’ll know that we’re right when 1. People use our mockups without trouble 2. People offer to pay when we offer to leave the mockups with them Example from Josh Seiden: Replacing Requirements with HypothesesCopyright © 2012 by IQ Agency 8
  9. 9. Design collaboration is a buy in tool.Copyright © 2012 by IQ Agency 9
  10. 10. Design collaboration is a buy in tool. • Tap into people’s pride by giving them a part of the design ownership - everyone wants to work on something meaningful. • Collaborating on the design streamlines the on-boarding process to keep things moving. • The designers role shifts to facilitator of design thinking and steward of the vision.Copyright © 2012 by IQ Agency 10
  11. 11. Thanks Extras: Follow me on twitter @jeniferv More AgileUX slides on http://agileuxnyc.comCopyright © 2012 by IQ Agency 11