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.

API First: Creating ecosystems instead of products

1,971 views

Published on

Workshop presented at MoDevUX in the DC suburbs, 19 May 2014

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

API First: Creating ecosystems instead of products

  1. 1. 1 @shoobe01 @MoDevUX API-First Design Creating ecosystems instead of products
  2. 2. 2
  3. 3. 33
  4. 4. 4
  5. 5. 5
  6. 6. 6 Designing solutions.
  7. 7. 7 Users are part of your system.
  8. 8. 8 Futureproof design is user centered design.
  9. 9. 99
  10. 10. 1010
  11. 11. 1111
  12. 12. 12 ―Sadly, no decision about architecture is a decision, one that will determine your success or failure as a company.‖ – Michael Sharkey @michaelsharkey
  13. 13. 13 ―I publish a website, but tens of thousands of my most loyal readers consume it using RSS apps. What should they count as, ―app‖ or ―web‖? I say: who cares? It’s all the web.‖ – John Gruber @daringfireball
  14. 14. 14 4ourth.com/ nyt
  15. 15. 15 Practical, useful user centered design.
  16. 16. 16 Design high points: • First, don’t draw • Gather, understand • Ecosystems first • Hold, look, tap, connect • Annotate, describe, understand • Evaluate, and validate
  17. 17. 17 What are we going to build today?
  18. 18. 18 First: Don’t draw.
  19. 19. 19 KJ (Post-It®) Process: • Determine focus questions • Get in a room • Answer questions • Put up answers • Group answers, label groups • Vote on most important groups
  20. 20. 20 Focus Questions: • What is the product? • What is it’s one main purpose? • What one problem does it solve? • How is this solved today? • Who will use the product?
  21. 21. 21
  22. 22. 22 Learn what you know.
  23. 23. 23 Note what exists.
  24. 24. 24 KJ (Post-It®) Exercise: • “What one problem does it solve?” • “How is it solved today?” • Put up answers • Group answers (draw a circle) • Label groups (write the label) • Pick the top three (at most) groups
  25. 25. 25 Measure your success. Or failure.
  26. 26. 26 Objectives and key results.
  27. 27. 27 Users and personas.
  28. 28. 28 Presumptive personas.
  29. 29. 29 Google personas.
  30. 30. 3030
  31. 31. 31 Ecosystems first.
  32. 32. 32 User task flow.
  33. 33. 33
  34. 34. 343434
  35. 35. 35
  36. 36. 3636
  37. 37. 3737
  38. 38. 38 User task flow.
  39. 39. 39 Hold, look, tap, connect.
  40. 40. 4040
  41. 41. 4141
  42. 42. 4242
  43. 43. 43
  44. 44. 4444
  45. 45. 45
  46. 46. 46
  47. 47. 47 How bad can it be?
  48. 48. 48
  49. 49. 49 Cut it apart.
  50. 50. 50
  51. 51. 51 Annotate, describe, understand.
  52. 52. 52
  53. 53. 53
  54. 54. 54 ―…consider the ―non-use-case‖… Broadcasting a sound—particularly voices—into an empty room in the middle of the night can be both startling and annoying.‖ – Dan Saffer in Microinteractions
  55. 55. 55 Validate.
  56. 56. 56
  57. 57. 57 Thing
  58. 58. 58
  59. 59. 59 Testing Hints: • Test in context. • Watch what they do. • Encourage talk-aloud. • Let the test drift. • Full prototypes aren’t needed.
  60. 60. 60 Contact me for consulting, design, to follow up on this deck, or just to talk: Steven Hoober steven@4ourth.com +1 816 210 0455 @shoobe01 shoobe01 on: www.4ourth.com
  61. 61. 61 Embrace failure and complexity.
  62. 62. 62
  63. 63. 63 There is no happy path.
  64. 64. 64
  65. 65. 65 Information snacking & re-engagement.
  66. 66. 66 Local…
  67. 67. 67 5 billion SMS users.

×