The document discusses the iterative process of designing and improving a website or digital product. It describes steps taken such as gathering user feedback, creating prototypes, testing with users, implementing changes, and continuing to iterate based on measuring success and identifying areas for further improvement. The goal is to continually evolve the design through a process of listening, learning, and refining.

1. Embracing evolution
Ge ing iterative in your approach to design
Daniel Burka @dburka
“Amoeba”, Heather Gonsior, 1984, 47x30 in., EGL coral pink, Chartpak and ink on paper, acrylic
Friday, February 26, 2010

2. Your website sucks
Trust me, it could be a lot be er
Flickr user: Creativity+ Timothy K Hamilton
Friday, February 26, 2010

3. Friday, February 26, 2010

4. Friday, February 26, 2010

5. Friday, February 26, 2010

6. Photo: Vermin Inc (CC Licensed)
Friday, February 26, 2010

7. Friday, February 26, 2010

8. Friday, February 26, 2010

9. Friday, February 26, 2010

10. Friday, February 26, 2010

11. Friday, February 26, 2010

12. Friday, February 26, 2010

13. Friday, February 26, 2010

14. Dear Digg,
Go fuck yourself.
Your pal,
— J.G.
Friday, February 26, 2010

15. Friday, February 26, 2010

16. Photo Credit: Joi Ito
“If you review your first site version and don’t feel
embarrassment, you spent too much time on it.”
Reid Ho man, LinkedIn
Friday, February 26, 2010

17. Take chances and release
Build with the expectation of change
Listen and iterate
Friday, February 26, 2010

18. How buildings learn: What happens a er they’re built
Stewart Brand
Read this book...
Friday, February 26, 2010

19. High road architecture
Friday, February 26, 2010

20. Friday, February 26, 2010

21. Low road architecture
Friday, February 26, 2010

22. Friday, February 26, 2010

23. Build a castle in no time!
Friday, February 26, 2010

24. Desire paths
Don’t waste time trying to predict everything
Credit: Phil Gyford
Friday, February 26, 2010

25. Friday, February 26, 2010

26. Friday, February 26, 2010

27. Friday, February 26, 2010

28. Credit: kimballhoman
Realign, don’t redesign
Cameron Moll is awfully clever... read it on A List Apart
Friday, February 26, 2010

29. Friday, February 26, 2010

30. Subtraction is iteration too
Try to remove as much as you add – don’t be afraid to prune
Credit: Rev Dan Catt
Friday, February 26, 2010

31. Friday, February 26, 2010

32. Friday, February 26, 2010

33. Friday, February 26, 2010

34. xx
x x x x
Friday, February 26, 2010

35. Friday, February 26, 2010

36. Really listen to your users
Both explicit and implicit feedback are crucial
Credit: Flickr user ‘Paulgi’
Friday, February 26, 2010

37. A case study
Digg comments
Friday, February 26, 2010

38. Step 1
We got it out there
Friday, February 26, 2010

39. Step 2
We added sophistication
Friday, February 26, 2010

40. 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
We kept 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
Friday, February 26, 2010

41. Establish 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
Friday, February 26, 2010

42. 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
Friday, February 26, 2010

43. Friday, February 26, 2010

44. Friday, February 26, 2010

45. 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
Friday, February 26, 2010

46. 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
Friday, February 26, 2010

47. 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
Friday, February 26, 2010

48. 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
Friday, February 26, 2010

49. 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
Friday, February 26, 2010

50. 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
Friday, February 26, 2010

51. 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
Friday, February 26, 2010

52. 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
Friday, February 26, 2010

53. One long year...
( I’m sorry )
Credit: Flickr user xjrlokix
Friday, February 26, 2010

54. Then we got it right
Well... sort of -
Friday, February 26, 2010

55. Gather feedback
Explicit and implicit
Friday, February 26, 2010

56. Set new goals
(Idea is to avoid feature creep and gauge success)
Make things feel simpler & improve interactions
Improve performance
Add most requested functionality
Friday, February 26, 2010

57. Create some comps
Somewhere to start discussion
Friday, February 26, 2010

58. User test #1
Focus group novices and experts
Friday, February 26, 2010

59. Ask for more feedback
Really? Yes.
Friday, February 26, 2010

60. Create refined comps
In this case html/css/js comps
Friday, February 26, 2010

61. Implement
Work closely with the development team
Friday, February 26, 2010

62. User test #2
Task analysis
Friday, February 26, 2010

63. Launch it!
It works? It works!
Friday, February 26, 2010

64. Launch it!
It works? It works!
Friday, February 26, 2010

65. Launch it!
It works? It works!
Friday, February 26, 2010

66. Launch it!
It works? It works!
Friday, February 26, 2010

67. Achieved goals?
Make things feel simpler & improve interactions
Improve performance
Add most requested functionality
Friday, February 26, 2010

68. Achieved goals?
Make things feel simpler & improve interactions
Improve performance
Add most requested functionality
Friday, February 26, 2010

69. Achieved goals?
Make things feel simpler & improve interactions
Improve performance
Add most requested functionality
Friday, February 26, 2010

70. Achieved goals?
Make things feel simpler & improve interactions
Improve performance
Add most requested functionality
Friday, February 26, 2010

71. Done? Nope
Start on next iterations
Friday, February 26, 2010

72. Still weak for casual visitors
Done? Nope
Start on next iterations
Friday, February 26, 2010

73. Still weak for casual visitors
Scales technically, but not socially
Done? Nope
Start on next iterations
Friday, February 26, 2010

74. Still weak for casual visitors
Scales technically, but not socially
Pseudo-pagination is cool, but not great
Done? Nope
Start on next iterations
Friday, February 26, 2010

75. Still weak for casual visitors
Scales technically, but not socially
Pseudo-pagination is cool, but not great
Hard to keep up-to-date with your conversations
Done? Nope
Start on next iterations
Friday, February 26, 2010

76. Still weak for casual visitors
Scales technically, but not socially
Pseudo-pagination is cool, but not great
Hard to keep up-to-date with your conversations
Onerous registration to comment
Done? Nope
Start on next iterations
Friday, February 26, 2010

77. Stay fit: adapt to survive and thrive
If iterative design isn’t instinctual, be convincing
Friday, February 26, 2010

78. Thanks! I’m dburka
digg twi er flickr clustershot last.fm
daniel@deltatangobravo.com
slides will be on slideshare.net/dburka
... and this is Ursula
Friday, February 26, 2010