2. Do you want to DESIGN A SYSTEM which considers...
An organization's business User's needs, limitations
objectives and goals and preferences
Organization gets benefits User will like it
3. We all want, that is, just to SATISFY THE USERS
User’s Satisfaction = Organization’s Benefit
4. So lets go back and analyze, what are the major aspects
that makes our system ineffective, incapable
5. So lets go back and analyze, what are the major aspects
that makes our system ineffective, incapable
- BADLY DESIGNED NAVIGATION
(Difficult to use, user get lost in between)
6. So lets go back and analyze, what are the major aspects
that makes our system ineffective, incapable
- BADLY DESIGNED NAVIGATION
(Difficult to use, user get lost in between)
- POORLY DESIGNED CONTENT STRUCTURE
(Hard to read information)
7. So lets go back and analyze, what are the major aspects
that makes our system ineffective, incapable
- BADLY DESIGNED NAVIGATION
(Difficult to use, user get lost in between)
- POORLY DESIGNED CONTENT STRUCTURE
(Hard to read information)
- INCONSISTANCY THROUGH-OUT ALL PAGES
(Get lost in between)
8. So lets go back and analyze, what are the major aspects
that makes our system ineffective, incapable
- BADLY DESIGNED NAVIGATION
(Difficult to use, user get lost in between)
- POORLY DESIGNED CONTENT STRUCTURE
(Hard to read information)
- INCONSISTANCY THROUGH-OUT ALL PAGES
(Get lost in between)
- POOR/DULL CONTENT, SEEMS NOT RELEVANT TO THE SERVICES
(Doesn’t answer user’s questions, what user can do on the site)
9. So lets go back and analyze, what are the major aspects
that makes our system ineffective, incapable
- BADLY DESIGNED NAVIGATION
(Difficult to use, user get lost in between)
- POORLY DESIGNED CONTENT STRUCTURE
(Hard to read information)
- INCONSISTANCY THROUGH-OUT ALL PAGES
(Get lost in between)
- POOR/DULL CONTENT, SEEMS NOT RELEVANT TO THE SERVICES
(Doesn’t answer user’s questions, what user can do on the site)
- SLOW LOADING PAGE
(User have to wait till the content loads on the page to perform the action)
10. So lets go back and analyze, what are the major aspects
that makes our system ineffective, incapable
- BADLY DESIGNED NAVIGATION
(Difficult to use, user get lost in between)
- POORLY DESIGNED CONTENT STRUCTURE
(Hard to read information)
- INCONSISTANCY THROUGH-OUT ALL PAGES
(Get lost in between)
- POOR/DULL CONTENT, SEEMS NOT RELEVANT TO THE SERVICES
(Doesn’t answer user’s questions, what user can do on the site)
- SLOW LOADING PAGE
(User have to wait till the content loads on the page to perform the action)
- UNPROFESSIONALLY DESIGN
(Icons, typography, colors, images etc.)
11. Because we use START
WATERFALL SOFTWARE DEVELOPMENT
life cycle model
DESIGN
DEVELOPMENT
TESTING
NO
DESIGN
ERRORS
ERRORS
YES
END
12. Because we use START
WATERFALL SOFTWARE DEVELOPMENT
life cycle model
DESIGN
OPMENT
Missing
USER
STING
DESIGN
ERRORS
ERRORS
YES
END
13. USER is the one
- We design and develop for
- We want to satisfy
- We get benefits from
14. so HOW do we design a system that fits into...
Organization’s objectives and goals
Users Expectations
15. USER CENTERED DESIGN
User-centered design (UCD) is an approach for employing usability.
It is a structured product development methodology that involves users
Throughout all stages of Web site development, in order to create a system
that meets users' needs.
- usability.gov
16. START
USER CENTERED DESIGN process
PLANNING
Analysis
TEST Analysis
Evaluate Implement
RESEARCH
Evaluate Implement
Development
Team with Users
Analysis
Analysis
DESIGN
Evaluate Implement
ANALYZE
Evaluate Implement
17. SCOPE
What are you developing?
What is the system going to cover?
What the users goals are?
AUDIENCES
Who are the major groups you want the site to serve?
OBJECTIVES
What goals should the system help your agency or organization to meet?
PLANNING
18. Who are the users?
What’s their tasks and goals are?
What are marketing & branding goals?
What influence user to use the system?
Which tasks are critical, important?
What is users environment?
PLANNING RESEARCH
19. How user perform the task and how long will it take?
How do user want to use the system?
How easy user can use the system without any error?
What mental model user use to use the system
PLANNING RESEARCH ANALYZE
20. User will like this color combination?
How can we put branding elements into design?
How easy we can make the system structure?
Have we use consistency through-out the system?
Have we used relevant content?
PLANNING RESEARCH ANALYZE DESIGN
21. Is the navigation easy to access?
How is the speed of the system?
User found the system interesting?
User could perform the task that he want to perform?
Is user satisfied?
Does user find consistency in the system?
NNING RESEARCH ANALYZE DESIGN EVALUATE
22. Why should we follow UCD process...
100
90 LAUNCH SYSTEM
80
Cost of making changes
70
60 TESTING
50
40
30
DEVELOPMENT
20
10 DESIGN
0
Time
23. BENEFITS of UCD process
USER
Achieve their goals easily and effectively
Enjoy the interaction with the system
Satisfied instead of frustrated
Increase trust to use the system again
ORGANIZATION
Reduce development cost and time
Reduce training cost and time
Reduce support cost and time
Reduce maintenance cost and time
Increase traffic / user’s interest
Increase product’s sale and revenue
Attract new customers
Retain existing customers