Eric Reiss gives a talk on moving beyond responsive design to anticipatory design. He argues that designers should anticipate users' needs rather than simply respond to devices. Reiss also stresses the importance of embracing content and context over worshipping form. He concludes by warning against complacency in the industry and encouraging designers to change the world.

1. Beyond responsiveness
Eric Reiss
@elreiss
UX Camp CPH
13 April 2013
Copenhagen, Denmark
Observations
Stories
Lessons

2. Some thoughts from today
� Responsive…to what?
A firm notion
Big data, bigger insights
Putting the “A” into “IA”
� Design or mass-production?
� Process or pedantry?
� The Charles H. Duell myth

3. re·spon·sive
adj
1 : responding, reacting
2 : quick to react

7. Responsive design?
Responsive content?
Mobile first?

9. I’d like to suggest a new term:
Anticipatory Design*
* With apologies to Buckminster Fuller

11. Anticipatory design...ESP
1. Extracts patterns
2. Situationally aware
� Location-based services
� Motion-based services
� Time-based services
3. Predicts needs

12. Users

13. Content strategy

14. The design failure

15. Context is the kingdom

17. No clicks – everything is in play

18. 1st click – is there a preference?

19. 2nd click – this could be a pattern

20. Third click – yes, there’s a pattern

21. Fourth click – time to zero in

22. Eric’s life-lesson #1
Don’t respond to the device.
Anticipate the needs of those
who will use the device.

23. Some thoughts from today
� Responsive…to whom?
A firm notion
Big data, bigger insights
Putting the “A” into “IA”
� Design or mass-production?
� Process or pedantry?
� The Charles H. Duell myth

24. We control the experience

25. We define the paths

26. We have ethical responsibilities

27. It’s about how we combine content

28. Some thoughts from today
� Responsive…to whom?
A firm notion
Big data, bigger insights
Putting the “A” into “IA”
� Design or mass-production?
� Process or pedantry?
� The Charles H. Duell myth

29. Buzzword du jour

30. Snow Semmelweis Taylor

31. 1854 Broad St. cholera outbreak

32. Infant mortality in Vienna

33. The Hemline Index

34. Some thoughts from today
� Responsive…to whom?
A firm notion
Big data, bigger insights
Putting the “A” into “IA”
� Design or mass-production?
� Process or pedantry?
� The Charles H. Duell myth

35. Marco Vitruvius Pollio

36. firmitas, utilitas, venustas

37. If everything is usable, findable,
how do we differentiate our
brand, product or service?
Personality
is the venustas (beauty)
in interactive media!

38. Some thoughts from today
� Responsive…to whom?
A firm notion
Big data, bigger insights
Putting the “A” into “IA”
� Design or mass-production?
� Process or pedantry?
� The Charles H. Duell myth

39. Source: Standard screen patterns by Theresa Neil
Design patterns are not design

40. Photos by Isabella J. Fortino

41. Photos by Isabella J. Fortino

42. Photos by Isabella J. Fortino

43. Photos by Isabella J. Fortino

44. Eric s life-lesson #2
Don’t worship the form.
Embrace the content and context.

45. Some thoughts from today
� Responsive…to whom?
A firm notion
Big data, bigger insights
Putting the “A” into “IA”
� Design or mass-production?
� Process or pedantry?
� The Charles H. Duell myth

47. ag·ile
adj
1 : able to move quickly and easily
2 : mentally quick and resourceful

48. The three Scrum questions
1. What did you do yesterday?
2. What will you do today
3. What is blocking your progress?

50. The three Scrum questions
1. What did you do yesterday?
I sailed west.
2. What will you do today?
Sail back to where I was yesterday.
3. What is blocking your progress?
These fucking Scrum meetings!

51. My Favourite Process
DWYNTDTGTSD
Do What You Need To Do To Get The Shit Done

52. Eric s life-lesson #3
Don’t become a slave to process.
Break the rules.
Accept the unexpected.

53. Some thoughts from today
� Responsive…to whom?
A firm notion
Big data, bigger insights
Putting the “A” into “IA”
� Design or mass-production?
� Process or pedantry?
� The Charles H. Duell myth

54. Charles H. Duell
U.S. Patent Commissioner, 1899
“There is nothing left to invent…”
(Urban myth)

56. Could there also be too much
complacency in our industry today?

58. Can we put our work into
historical perspective?

59. How long is an internet year?

60. 1895 00 05 10 15 20 25 30 1935
Wall St. crash
First commercial
automobile
First series-produced
automobiles
First assembly line

61. 1895 00 05 10 15 20 25 30 1935
1993 94 95 96 97 98 99 00 2001
Wall St. crash
First commercial
automobile
First series-produced
automobiles
First commercial
web browser
First commercial
websites
Dot-bomb
First assembly line
First commercial
CMS

62. 1895 00 05 10 15 20 25 30 1935
1993 94 95 96 97 98 99 00 2001
Wall St. crash
First commercial
automobile
First series-produced
automobiles
First commercial
web browser
First commercial
websites
Dot-bomb
First assembly line
First commercial
CMS
4.7 years – about 1 standard business cycle!

63. So, we’re somewhere in the 1980s...

64. Bonus lesson
2-Way Empathy

65. Count Helmuth von Moltke
No battle plan
survives contact
with the enemy.

66. Eric’s life-lesson #4
Don’t sacrifice your users for the
benefit of your employer.
No business plan has ever
succeeded without customers.

67. Bad design causes bad results

68. Good design wins customers

69. “Cease not to learn until thou
cease to live. Think that day
lost wherein thou draw’st no
letter to make thyself more
learn’d, wiser, and better.”
Guy Du Faur de Pibrac

70. My big message:
Don’t be complacent.
And you CAN
change the world,
so get on with it!

71. Thanks!

72. You can (usually) find Eric at:
The FatDUX Group ApS
Strandøre 15
DK-2100 Copenhagen
Denmark
Office: (+45) 39 29 67 77
Mobile: (+45) 20 12 88 44
Twitter: @elreiss
er@fatdux.com
www.fatdux.com