1. Context
2. Content
3. Information Architecture
4. Consistency
5. Friction
5 KEY AREAS OF SUCK
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
1
Slide 9
Slide 9 text
The how, when, where and why
users’s use your app.
Context
Slide 10
Slide 10 text
Environmental
Ecosystem
CONTEXT
Slide 11
Slide 11 text
ENVIRONMENTAL
The physical location a user is while
using your app.
Slide 12
Slide 12 text
Environmental image
Slide 13
Slide 13 text
Environmental image
Slide 14
Slide 14 text
Environmental image
Slide 15
Slide 15 text
Context Fail
Slide 16
Slide 16 text
Context Fail
Slide 17
Slide 17 text
DESKTOP
TABLET
WATCH
PHONE
Slide 18
Slide 18 text
“The best interface is the one within
reach”
CAMERON MOLL
Slide 19
Slide 19 text
ECOSYSTEMS
Where your app falls in broader use
Slide 20
Slide 20 text
No content
Slide 21
Slide 21 text
As systems become more and more
complicated the need for them to be
“designed” increases.
Slide 22
Slide 22 text
“It is the designers responsibility for
the design of those relationships
and ensuring that their collective
value significantly exceeds the sum
of their individual values,…
Slide 23
Slide 23 text
…and their cumulative complexity is
significantly less than the sum of
their individual complexities.”
BILL BUXTON
Slide 24
Slide 24 text
Understanding Context
Solution
Slide 25
Slide 25 text
ETHNOGRAPHIC
RESEARCH
Slide 26
Slide 26 text
Watching the user, in their
environment, use your software.
Slide 27
Slide 27 text
Observe and listen in a
non-directed way
Slide 28
Slide 28 text
DIARY STUDY
Slide 29
Slide 29 text
JOURNEY MAPS
Slide 30
Slide 30 text
A map of the user’s experience
across all channels from end to end.
Slide 31
Slide 31 text
Guide to Experience Mapping
Adaptive Path
http://www.mappingexperiences.com