api first: creating ecosystems instead of products
DESCRIPTION
Workshop presented at MoDevUX in the DC suburbs, 19 May 2014TRANSCRIPT
1
@shoobe01@techjobslafair
@shoobe01@MoDevUX
@shoobe01 @MoDevUX
API-First DesignCreating ecosystems instead of products
2
@shoobe01@techjobslafair
@shoobe01@MoDevUX
3
@shoobe01@techjobslafair
@shoobe01@MoDevUX@shoobe01@techjobslafair
3
@shoobe01@MoDevUX
4
@shoobe01@techjobslafair
@shoobe01@MoDevUX
5
@shoobe01@techjobslafair
@shoobe01@MoDevUX@shoobe01@MoDevUX
6
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Designing solutions.
7
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Users are part of your system.
8
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Futureproof design is user centered design.
9
@shoobe01@techjobslafair
@shoobe01@MoDevUX
9
@shoobe01@MoDevUX
10
@shoobe01@techjobslafair
@shoobe01@MoDevUX
10
@shoobe01@MoDevUX
11
@shoobe01@techjobslafair
@shoobe01@MoDevUX
11
@shoobe01@MoDevUX
12
@shoobe01@techjobslafair
@shoobe01@MoDevUX
“Sadly, no decision about architecture is a decision, one that will determine your success or failure as a company.”
– Michael Sharkey
@michaelsharkey
13
@shoobe01@techjobslafair
@shoobe01@MoDevUX
“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
@shoobe01@techjobslafair
@shoobe01@MoDevUX
4ourth.com/nyt
15
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Practical, useful user centered design.
16
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Design high points:
• First, don’t draw• Gather, understand• Ecosystems first• Hold, look, tap, connect• Annotate, describe, understand• Evaluate, and validate
17
@shoobe01@techjobslafair
@shoobe01@MoDevUX
What are we going to build today?
Exercise
18
@shoobe01@techjobslafair
@shoobe01@MoDevUX
First: Don’t draw.
19
@shoobe01@techjobslafair
@shoobe01@MoDevUX
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
@shoobe01@techjobslafair
@shoobe01@MoDevUX
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
@shoobe01@techjobslafair
@shoobe01@MoDevUX
22
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Exercise
Learn what you know.
23
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Exercise
Note what exists.
24
@shoobe01@techjobslafair
@shoobe01@MoDevUX
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
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Measure your success.Or failure.
26
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Objectives and key results.
27
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Users and personas.
28
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Presumptive personas.
29
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Google personas.
30
@shoobe01@techjobslafair
@shoobe01@MoDevUX
30
@shoobe01@techjobslafair
31
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Ecosystems first.
32
@shoobe01@techjobslafair
@shoobe01@MoDevUX
User task flow.
Exercise
33
@shoobe01@techjobslafair
@shoobe01@MoDevUX
34
@shoobe01@techjobslafair
@shoobe01@MoDevUX
3434
@shoobe01@MoDevUX
35
@shoobe01@techjobslafair
@shoobe01@MoDevUX
36
@shoobe01@techjobslafair
@shoobe01@MoDevUX
36
@shoobe01@techjobslafair
37
@shoobe01@techjobslafair
@shoobe01@MoDevUX
37
@shoobe01@techjobslafair
38
@shoobe01@techjobslafair
@shoobe01@MoDevUX
User task flow.
Exercise
39
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Hold, look, tap, connect.
40
@shoobe01@techjobslafair
@shoobe01@MoDevUX
40
@shoobe01@techjobslafair
41
@shoobe01@techjobslafair
@shoobe01@MoDevUX
41
@shoobe01@techjobslafair
42
@shoobe01@techjobslafair
@shoobe01@MoDevUX
42
@shoobe01@MoDevUX
43
@shoobe01@techjobslafair
@shoobe01@MoDevUX
44
@shoobe01@techjobslafair
@shoobe01@MoDevUX
44
@shoobe01@techjobslafair
45
@shoobe01@techjobslafair
@shoobe01@MoDevUX
46
@shoobe01@techjobslafair
@shoobe01@MoDevUX@shoobe01@MoDevUX
47
@shoobe01@techjobslafair
@shoobe01@MoDevUX
How bad can it be?
48
@shoobe01@techjobslafair
@shoobe01@MoDevUX@shoobe01@MoDevUX
49
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Cut it apart.
Exercise
50
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Exercise
51
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Annotate, describe, understand.
Exercise
52
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Exercise
53
@shoobe01@techjobslafair
@shoobe01@MoDevUX
54
@shoobe01@techjobslafair
@shoobe01@MoDevUX
“…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
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Validate.
56
@shoobe01@techjobslafair
@shoobe01@MoDevUX
57
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Thing
@shoobe01@MoDevUX
58
@shoobe01@techjobslafair
@shoobe01@MoDevUX@shoobe01@MoDevUX
59
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Testing Hints:
• Test in context.• Watch what they do.• Encourage talk-aloud.• Let the test drift.• Full prototypes aren’t needed.
60
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Contact me for consulting, design, to
follow up on this deck, or just to talk:
Steven Hoober
+1 816 210 0455
@shoobe01
shoobe01 on:
www.4ourth.com
61
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Embrace failure and complexity.
62
@shoobe01@techjobslafair
@shoobe01@MoDevUX
63
@shoobe01@techjobslafair
@shoobe01@MoDevUX
There is no happy path.
64
@shoobe01@techjobslafair
@shoobe01@MoDevUX
65
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Information snacking &re-engagement.
66
@shoobe01@techjobslafair
@shoobe01@MoDevUX
Local…
67
@shoobe01@techjobslafair
@shoobe01@MoDevUX
5 billion SMS users.