0
Charles Darwin
                                                                    Flickr user: cpurrin1




Changing succ...
Credit: Martin_Heigan




Your design sucks
  Trust me, you can do better
Credit: Mark Trammell
                              aka chasingfun




         Are you in or out?
contract work   vs   in...
Credit: Flickr user
‘notsogoodphotography’




        Handling feedback
      What do people want and why do they want it?
Desire paths
                      Don’t try to predict everything




Credit: Phil Gyford
Adapt to Scale
 It’s a great problem to have
Subtraction is iteration too
Try to remove as much as you add




                                   Credit: Rev Dan Catt
Credit:
                         kimballhoman + (flickr)




Realign, don’t redesign
Cameron Moll is clever
“Every time I hear a designer say the word
    innovation I reach for my revolver....
   so I can shoot them in the face”
...
Adapt to survive
If iterative design isn’t instinctual, be convincing
A case study

Digg comments
Step 1

Get it out there
Step 2

Add sophistication
by dburka 20 minutes ago

Of course, what McCain is trying to avoid anyone noticing is that the problem isn't regulators f...
Set goals
Add multiple levels of nesting

Reduce complexity of nesting

Discourage top-posting

Increase participation

Im...
by dburka 20 minutes ago

Of course, what McCain is trying to avoid anyone noticing is that the problem isn't regulators f...
Measure success
Add multiple levels of nesting

Reduce complexity of nesting

Discourage top-posting

Increase participati...
Credit: Flickr user xjrlokix




One long year...
( I’m sorry )
Then we got it right
            Well... sort of
Gather feedback
Explicit and implicit
Set new goals
(Idea is to avoid feature creep and gauge success)

Make things feel simpler & improve interactions

Improve...
Create some comps
Somewhere to start discussion
User test #1
Focus group novices and experts
Ask for more feedback
 Really? Yes.
Create refined comps
In this case html/css/js comps
Implement
Work closely with the development team
User test #2
Perform task analysis
Things we didn’t do
Set a public timeline
Try to get it perfect
Include everything people wanted
Launch it!
Start gathering feedback again...
Summing up...
Feedback, feedback, and more feedback

Follow how people actually use your system

Subtraction is iteration ...
Homework
Stewart Brand - How Buildings Learn
Thanks! Questions?
Slides will be on Slideshare

slideshare.net/dburka/slideshows
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Changing successfully: Adapting your interface over time
Upcoming SlideShare
Loading in...5
×

Changing successfully: Adapting your interface over time

7,039

Published on

Published in: Technology, Economy & Finance
0 Comments
33 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
7,039
On Slideshare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
408
Comments
0
Likes
33
Embeds 0
No embeds

No notes for slide

Transcript of "Changing successfully: Adapting your interface over time"

  1. 1. Charles Darwin Flickr user: cpurrin1 Changing successfully Adapting your interface over time Daniel Burka – Digg Creative Director – Pownce Co-founder – Silverorange Co-founder
  2. 2. Credit: Martin_Heigan Your design sucks Trust me, you can do better
  3. 3. Credit: Mark Trammell aka chasingfun Are you in or out? contract work vs in-house design
  4. 4. Credit: Flickr user ‘notsogoodphotography’ Handling feedback What do people want and why do they want it?
  5. 5. Desire paths Don’t try to predict everything Credit: Phil Gyford
  6. 6. Adapt to Scale It’s a great problem to have
  7. 7. Subtraction is iteration too Try to remove as much as you add Credit: Rev Dan Catt
  8. 8. Credit: kimballhoman + (flickr) Realign, don’t redesign Cameron Moll is clever
  9. 9. “Every time I hear a designer say the word innovation I reach for my revolver.... so I can shoot them in the face” Stuart Butterfield, Flickr March, 2008
  10. 10. Adapt to survive If iterative design isn’t instinctual, be convincing
  11. 11. A case study Digg comments
  12. 12. Step 1 Get it out there
  13. 13. Step 2 Add sophistication
  14. 14. by dburka 20 minutes ago Of course, what McCain is trying to avoid anyone noticing is that the problem isn't regulators failing to do their job; it's that that man he tapped to write his economic policy - Phil Gramm - removed oversight of the instruments that are laying waste to the finance sector from the regulators' job descriptions. Reply to this comment by marktrammell 16 minutes ago We all know McCain is incompetent when it comes to the economy, and that Phil Gramm sold out the finance sector. You would think they would have brought in someone with substance when Phil hit the road. 5 Replies to this comment by dburka 14 minutes ago We all know McCain is incompetent when it comes to the economy, and that Phil Gramm sold out the finance sector. You would think they would have brought in someone with substance when Phil hit the road. Step 3 5 Replies to this comment by kurtwilms 12 minutes ago Start revising We all know McCain is incompetent when it comes to the economy, and that Phil Gramm sold out the finance sector. You would think they would have brought in someone with substance when Phil hit the road. Reply to this comment by kevinrose 10 minutes ago
  15. 15. Set goals Add multiple levels of nesting Reduce complexity of nesting Discourage top-posting Increase participation Improve quality of discussions Address scaling issues Make things feel simpler & improve interactions
  16. 16. by dburka 20 minutes ago Of course, what McCain is trying to avoid anyone noticing is that the problem isn't regulators failing to do their job; it's that that man he tapped to write his economic policy - Phil Gramm - removed oversight of the instruments that are laying waste to the finance sector from the regulators' job descriptions. Reply to this comment by marktrammell 16 minutes ago We all know McCain is incompetent when it comes to the economy, and that Phil Gramm sold out the finance sector. You would think they would have brought in someone with substance when Phil hit the road. 5 Replies to this comment by dburka 14 minutes ago We all know McCain is incompetent when it comes to the economy, and that Phil Gramm sold out the finance sector. You would think they would have brought in someone with substance when Phil hit the road. 5 Replies to this comment by kurtwilms 12 minutes ago We all know McCain is incompetent when it comes to the economy, and that Phil Gramm sold out the finance sector. You would think they would have brought in someone with substance when Phil hit the road. Reply to this comment by kevinrose 10 minutes ago
  17. 17. Measure success Add multiple levels of nesting Reduce complexity of nesting Discourage top-posting Increase participation Improve quality of discussions Address scaling issues Make things feel simpler & improve interactions
  18. 18. Credit: Flickr user xjrlokix One long year... ( I’m sorry )
  19. 19. Then we got it right Well... sort of
  20. 20. Gather feedback Explicit and implicit
  21. 21. Set new goals (Idea is to avoid feature creep and gauge success) Make things feel simpler & improve interactions Improve performance Add most requested functionality
  22. 22. Create some comps Somewhere to start discussion
  23. 23. User test #1 Focus group novices and experts
  24. 24. Ask for more feedback Really? Yes.
  25. 25. Create refined comps In this case html/css/js comps
  26. 26. Implement Work closely with the development team
  27. 27. User test #2 Perform task analysis
  28. 28. Things we didn’t do Set a public timeline Try to get it perfect Include everything people wanted
  29. 29. Launch it! Start gathering feedback again...
  30. 30. Summing up... Feedback, feedback, and more feedback Follow how people actually use your system Subtraction is iteration too Measurable goals are crucial Avoid concrete timelines and avoid bloat Leave time to iterate, in fact plan for it Credit: Flickr user ‘ucumari’
  31. 31. Homework Stewart Brand - How Buildings Learn
  32. 32. Thanks! Questions? Slides will be on Slideshare slideshare.net/dburka/slideshows
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×