Your SlideShare is downloading. ×
Agile/Lean/Rapid UX
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Agile/Lean/Rapid UX

3,201
views

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

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

0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,201
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
24
Comments
0
Likes
7
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Transcript

    • 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. Make user research routine.Copyright © 2012 by IQ Agency 2
    • 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. Visualize quickly.Copyright © 2012 by IQ Agency 4
    • 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. Shift from requirements to hypotheses.Copyright © 2012 by IQ Agency 6
    • 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. 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. Design collaboration is a buy in tool.Copyright © 2012 by IQ Agency 9
    • 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. Thanks Extras: Follow me on twitter @jeniferv More AgileUX slides on http://agileuxnyc.comCopyright © 2012 by IQ Agency 11