Please enable JavaScript.
Coggle requires JavaScript to display documents.
Know User (Interaction design process (Key activities (Identifying needs,…
Know User
Interaction design process
Goal-directed problem solving activity
Informed by actual use, target domain, materials cost and feasibility
Creative Activity
Decision making activity to balance trade-offs
Key activities
Identifying needs
Establishing requirements
Developing alternative designs
Building interactive versions (paper proto)
Evaluating designs
Involving users
Expectation Management
Realistic expectations
No surprises / disappointments
Timely training
Communication but no hype
Ownership
Make users active stakeholders
More likely to accept or forgive problems
Can make a big difference to success of project
Participation
Cycle Users
Design Workshops/ Evaluations
User-Centered design
Early focus on users and tasks
Empirical measurements
Iterative design
Design must:
Acknowledge
who
the users are
Support the activities being carried out
Appreciate
where
the interaction is taking place
Optimize
the interactions being carried out by the user
Match
the users activities and needs
Scenarios
Informal narrative / story
Illustrate using storyboards
Good to show to mgmt, marketing and customers
Can replace walls of text
Similar to use cases in SE
Personas
Understanding the user
Clarifying assumptions
Fully Exploring the design
Providing a context for reviewers
Helping other project tasks
Best buy: roster of shopper profiles
Professionals in Interaction design
Interaction designer
Usability designers
Web designers
Information architects
UX designers
How to choose between alternatives
Prototype
Technical feasibilities
Quality thresholds
Safety
Utility
Effectiveness
Efficiency
Who are users / stakeholders?
Not always obvious
Primary users: freq hands on
Secondary users: Occasional or via someone else
tertiary: Those affected by the project
Types of users
Novice
Frequent feedback
Actions prompted by choices
Safe exploration supported
Easy undo
Selective disclosure
Intermediate
Knowledge of broad aspects
Needs easy access to the details
Can be an amalgam of novice and expert
Experts
Critical help system user
lower, more subtle support and feedback
Accelerators required
Customisability desired
Experts less risk-averse in usage patterns
Defining needs
Users are poor visionaries
Instead look at existing tasks
Where?
Who?
What?
Why?