What to do when: Informing design at every phase Dana Chisnell Web Design World Seattle July 2009 1
What To Do When: Informing design at every phase
Jan 28, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
What to do when: Informing design at every phase
Dana Chisnell
Web Design World SeattleJuly 2009
1
The team did a great job.
2
Something is wrong.But what?
...
Input from users.
Check.
IT constraints.
Check.
Business requirements.
3
How do you fit user research into the process?
4
There are simple things you can do to inform design decisions:
5
Observe and listen to users through 3 key questions
6
http://www.flickr.com/photos/roby72/3345955051/
These phases
Requirements gathering
Design & test
Launch
7
Map to these questions
What should the design do?
How should it do it?
Does it do what we want it to do?
8
Does it do what we wanted it to do?
How should it do it?
What should the design do?
What does that look like?
9
10
What should the design do?
11
12
Learn who the users are
13
14
Brokers or administrators?
15
Doctors or patients?
16
Road warriors or vacationers?
๏Who are the users?
๏What are they like?
๏How are they reaching task goals?
17
Knowing user goals ensures
the design will be successful
18
Surveys
Focus groups
19
Ask, listen
Observe related tasksUsability test previous release
Ethnographic methods
Field usability tests
20
Learn what is useful to users
21
22
Benefit
Value
Usefulness
If benefits aren’t clear, uptake will be a struggle
23
Test competitors
24
Current users
rave or complain
interview-based tasks
25
Test inherent value
New users
tasks from current users
verbalize benefits
26
Test inherent value
Analyze
current and new users match?
anyone match Marketing?
27
Test inherent value
28
BobAdvisor
Proofthe concept
29
30
Qualitative data validating ideas
Reality checkpoint: translating research to requirements
31
Focus groups
Participatory design sessions
32
Show early designs
Test against benchmarksGoals
Previous performance
33
How should the design work?
34
35
Prototype
36
37
Flow
Steps
Information architecture
Interaction
Minimize design risks, experiment with ideas
38
Paper and pencil drawings
Wireframes
39
Low fidelity
High fidelityComps
Real data
Realistic look
Realistic interaction
40
Iterate(rapidly)
41
42
Experimenting = options, refinements
Engage the team in design,shorten time to market
43
Rapid
Iterative
Testing
Evaluation
44
RITE
45
BobAdvisor
46
BobStarBobStar*
As part of our ongoing commitment to provide first class performance reporting for our most valuable clients, we have enhanced our Quarterly Performance Statements for our managed accounts and enrolled full service accounts. The enhancements, which include a new design and expanded content will e introduced to our clients with their 4th quarter 2009 Quarterly Performance Statements this january 2010. Read more
Learn more
BobStar*
- Quick Market Update: Two charts, one table, and a bullet point - Quarterly conference to be held on March 30- 140 BobStar* mutual funds to be removed 3/14- Order BobStar* CSA accepted
Compare designsTough questions
Contentious decisions
* Must be radically different
47
http://www.flickr.com/photos/8666121@N02/2405646718
Testin context
48
49
Insights beyond the lab
Environmental factors
Holistic view of task goals
50
Narrow scope
Narrow task
User-documented data
Informal or formal
51
Go to users
Does it do what we want it to do?
52
53
Follow upon previous releases
54
BTO
55
Error rates
Hard-to-solve problems
Remedies for next release
Start somewhere
56
Holistic and summative
OR
Examine localized problems
57
Classic usability test
Compareto benchmarks
58
59
Compare, contrast quantitative data
Measure improvement
60
Against benchmarks
Defining benchmarks
Summative
61
Classic usability test
Verifyand validate
62
63
Quantitative data about success measures
Ensure goals are being met
Set priorities
64
End-to-end
Refining tasks
How usable is the design
65
Classic usability test
66
BobStarBobStar*
As part of our ongoing commitment to provide first class performance reporting for our most valuable clients, we have enhanced our Quarterly Performance Statements for our managed accounts and enrolled full service accounts. The enhancements, which include a new design and expanded content will e introduced to our clients with their 4th quarter 2009 Quarterly Performance Statements this january 2010. Read more
Learn more
BobStar*
- Quick Market Update: Two charts, one table, and a bullet point - Quarterly conference to be held on March 30- 140 BobStar* mutual funds to be removed 3/14- Order BobStar* CSA accepted
67
TextLogo Division name
Duane Chisnell shares his thoughts on investment management and trust.
What to do when
68
How do you fit user research into the process?
69
There are simple things you can do to inform design decisions
70
Observe and listen to users through 3 key questions
71
72
Take-awaysWhat should the design do?
observe and listen to users
test value
proof the concept
set benchmarks and goals
How should it work?
prototype and iterate design
test in context
Does it do what we want it to do?
compare to benchmarks
validate against usability goals
Where to learn more
73
Dana’s blog: http://usabilitytestinghowto.blogspot.com/
Download templates, examples, and links to other resources from www.wiley.com/go/usabilitytesting
Related Documents
