Week 3: Managing Design Processes
Course: Human-Computer Interaction (HCI)
Duration: 3 Hours
________________________________________________________
1. Introduction to Design Processes
Meaning of Design Process
A design process is a systematic approach used to create interactive systems that meet user
needs and organizational goals. In HCI, design processes guide developers from identifying user
problems to developing usable and effective solutions.
The design process ensures that:
Systems are easy to use
Users are satisfied
Errors are minimized
Productivity is improved
Importance of Design Processes in HCI
Design processes help:
1. Understand user needs
2. Improve usability
3. Reduce development costs
4. Avoid system redesign later
5. Enhance user satisfaction
6. Increase system efficiency
Characteristics of Good Design Processes
A good design process should be:
User-focused
Iterative
Flexible
Collaborative
Goal-oriented
Test-driven
Phases of a Typical Design Process
1. Problem Identification
Understanding the challenge users face.
2. Research and Analysis
Gathering information about users and tasks.
3. Ideation
Generating possible solutions.
4. Prototyping
Creating preliminary models of the system.
5. Evaluation and Testing
Testing usability and collecting feedback.
6. Implementation
Developing the actual system.
7. Maintenance and Improvement
Updating the system based on user feedback.
Example: University E-Learning Portal
A university notices student struggle accessing learning materials.
Design Process Applied:
Stage Activity
Problem Identification Students cannot easily access notes
Research Interviews with students and lecturers
Ideation Develop centralized portal
Prototype Create sample interface
Evaluation Students test portal
Implementation Full system developed
Maintenance Continuous updates
2. User-Centered Design (UCD)
Definition of User-Centered Design
User-Centered Design (UCD) is a design philosophy where users are involved throughout the
development process to ensure systems meet their needs, abilities, and expectations.
The focus is on:
Usability
Accessibility
User satisfaction
Efficiency
Principles of User-Centered Design
1. Early Focus on Users
Understand users before development begins.
2. Empirical Measurement
Evaluate systems using real users.
3. Iterative Design
Designs are continuously improved.
4. User Participation
Users actively contribute feedback.
UCD Lifecycle
Step 1: Understand Context of Use
Identify:
Who the users are
What tasks they perform
Their environment
Step 2: Specify User Requirements
Determine:
User needs
Functional requirements
Usability goals
Step 3: Produce Design Solutions
Develop:
Sketches
Wireframes
Prototypes
Step 4: Evaluate Designs
Conduct:
User testing
Feedback sessions
Improvements
The process repeats until usability goals are achieved.
Advantages of UCD
Advantage Explanation
Better usability Easier systems
Higher satisfaction Users enjoy the system
Reduced training Easy to learn
Increased productivity Faster task completion
Lower costs Fewer redesigns
Challenges of UCD
Requires time
User feedback may conflict
Costly user testing
Difficult to involve all users
Kenyan Case Study: eCitizen Platform
eCitizen
The Kenyan government developed the eCitizen system to improve access to government
services.
UCD Elements Applied:
Citizens were consulted
Services simplified
Mobile-friendly interfaces created
Feedback systems added
Results:
Faster service delivery
Reduced queues
Increased accessibility
3. Design Thinking Process
Definition of Design Thinking
Design thinking is a creative problem-solving approach focused on understanding users and
developing innovative solutions.
It encourages:
Creativity
Experimentation
Collaboration
Human-centered innovation
Stages of Design Thinking
1. Empathize
Understand user experiences and challenges through:
Observation
Interviews
Surveys
Example:
Students complain about slow registration systems.
2. Define
Clearly state the problem.
Example:
“Students experience delays during course registration.”
3. Ideate
Brainstorm possible solutions.
Methods include:
Brainstorming
Mind mapping
Group discussions
Example Solutions:
Mobile registration
Online queue system
Faster authentication
4. Prototype
Develop simple versions of solutions.
Examples:
Wireframes
Mockups
Sample interfaces
5. Test
Users test the prototype.
Feedback is collected to improve the system.
Benefits of Design Thinking
Encourages innovation
Focuses on real problems
Improves teamwork
Produces user-friendly solutions
Example: Mobile Banking Apps in Kenya
Safaricom developed M-Pesa using customer-centered innovation principles.
Key Design Thinking Features:
Understanding customer financial problems
Simple mobile interface
Continuous feedback and improvements
Impact:
Increased financial inclusion
Easy money transfer
Improved business transactions
4. Stakeholder Analysis
Definition of Stakeholders
Stakeholders are individuals or groups affected by a system.
They may:
Use the system
Manage the system
Fund the project
Maintain the system
Types of Stakeholders
Type Description
Primary stakeholders Direct users
Secondary stakeholders Indirectly affected
Key stakeholders Decision-makers
Examples in a University Portal
Stakeholder Role
Students Access learning materials
Lecturers Upload notes and grades
Administrators Manage records
ICT staff Maintain system
University management Monitor operations
Importance of Stakeholder Analysis
Stakeholder analysis helps:
Identify user needs
Reduce conflicts
Improve communication
Increase project success
Steps in Stakeholder Analysis
1. Identify Stakeholders
List all affected individuals.
2. Analyze Interests
Determine stakeholder expectations.
3. Assess Influence
Determine who has decision-making power.
4. Prioritize Stakeholders
Focus on high-impact stakeholders.
5. Develop Communication Plan
Determine how to engage stakeholders.
Stakeholder Matrix
Influence Interest Strategy
High High Manage closely
High Low Keep satisfied
Low High Keep informed
Low Low Monitor
Kenyan Example: Huduma Centres
Huduma Kenya
During development of Huduma Centres:
Citizens were primary stakeholders
Government ministries were key stakeholders
ICT teams maintained systems
Stakeholder analysis improved service delivery and integration.
5. Requirements Gathering in HCI
Definition
Requirements gathering is the process of collecting information about user needs and system
expectations.
It ensures systems solve the correct problems.
Types of Requirements
1. Functional Requirements
Describe what the system should do.
Examples:
Login functionality
Course registration
Grade viewing
2. Non-Functional Requirements
Describe system qualities.
Examples:
Security
Speed
Reliability
Accessibility
Techniques for Requirements Gathering
1. Interviews
Direct discussions with users.
Advantages:
Detailed information
Clarification possible
Disadvantages:
Time-consuming
2. Questionnaires
Written questions distributed to users.
Advantages:
Large audience
Cheap
Disadvantages:
Limited detailed feedback
3. Observation
Watching users perform tasks.
Advantages:
Real behavior observed
Disadvantages:
Users may change behavior
4. Focus Groups
Group discussions with users.
Advantages:
Multiple opinions
Disadvantages:
Dominant participants may influence others
5. Document Analysis
Reviewing existing documents and systems.
Examples:
Registration forms
Reports
Existing software manuals
Requirements Gathering Process
Step 1: Identify Users
Determine who will use the system.
Step 2: Select Techniques
Choose interviews, surveys, etc.
Step 3: Collect Data
Gather user information.
Step 4: Analyze Requirements
Organize and prioritize findings.
Step 5: Validate Requirements
Confirm accuracy with stakeholders.
Example: University Portal Requirements
Requirement Type Example
Functional Students can register courses
Functional Lecturers upload grades
Non-functional System should load within 3 seconds
Non-functional Secure user authentication
Learning Outcomes Summary
After this topic, learners should be able to:
1. Explain User-Centered Design
Students should:
Define UCD
Explain UCD principles
Describe benefits of UCD
2. Conduct Stakeholder Identification
Students should:
Identify stakeholders
Analyze stakeholder influence
Prioritize stakeholders
Practical Activity
Practical: Design Requirements for a University Portal
Scenario
A university wants to develop a digital student portal.
Students are required to identify:
Stakeholders
User requirements
Functional requirements
Non-functional requirements
Step 1: Identify Stakeholders
Stakeholder Responsibility
Students Access services
Lecturers Upload materials
Finance office Fee management
ICT department System maintenance
Administrators Manage records
Step 2: Gather Requirements
Functional Requirements
Student login
Course registration
Fee payment
Viewing results
Downloading notes
Non-Functional Requirements
High security
Fast response time
Mobile compatibility
24/7 availability
Step 3: Create Simple Use Scenario
Example:
1. Student logs into portal
2. Selects course registration
3. Chooses units
4. Submits registration
5. Receives confirmation message
Discussion Questions
1. Why is user-centered design important in HCI?
2. What challenges occur during stakeholder analysis?
3. Differentiate functional and non-functional requirements.
4. Explain how design thinking improves innovation.
5. Why should users participate in system development?
Summary
Managing design processes is essential in HCI because it ensures systems are:
Usable
Efficient
Accessible
User-friendly
User-centered design and stakeholder analysis help developers understand real user needs, while
requirements gathering ensures systems solve the intended problems effectively.