Inclusive Technology: Designing For Under-served and Marginalized - - PowerPoint PPT Presentation

CMSC 20370/30370 Winter 2020 Inclusive Technology: Designing For Under-served and Marginalized Communities

Jan 6, 2020

In Class Exercise (5 minutes)

• Take 5 minutes to think about a product or

technology you like

• Why do you like it?
• Do you think the design could be

improved?

• How does the design support the task you

want to do?

• We will share our answers next

Usability Goals

I Technology

Effective to use Efficient to use Safe to use Easy to learn Good functionality Easy to remember

I Technology

Satisfying Enjoyable Helpful Enhancing Supporting Provocative

Technology breaks my

Frustrating Boring Annoying Hard to use Unhelpful Makes us feel stupid

Why do we need inclusive technology?

Let’s look at other examples of good and bad design*

(*many of which are inclusive technology fails)

vs

https://twitter.com/i/status/897756900753891328

14

https://www.youtube.com/watch?v=FhGU4z YGgYk

Technology alone is not the answer.

As Toyama says, technology only amplifies human intent and behaviors. We need good design to make technology inclusive (while minimizing harm).

What is Inclusive Technology?

“Designing interactive products to support the way people communicate and interact in their everyday and working lives” – Preece HCI textbook Essentially it’s what happens when a human and a computer get together to perform a task

– E.g. writing a document, tracking a run, playing a song

Making technology inclusive relies on Human- Computer Interaction

HUMAN

Human Computer Interaction

Technology

In this class, we will study different target user groups including…

• Developing Countries
• Children
• Elderly
• Accessibility
• Gig Economy
• LGBTQ+
• Gender
• Low Income Communities
• AI and Bias

Why do we need to learn HCI to make technology inclusive?

HCI is an important aspect of Computer Science

• People trained in HCI build better

interfaces

• Defined methods to help create good

designs

• Bad products can fail
• Errors can result
• Computers are everywhere (in your watch,

fridge, toilet) but not always well designed

Better interfaces

• Easier for novices to learn (don’t have to

read the manual)

• Easier for experts to do what they need to

do

• Leads to better user experience

– Pleasure, satisfaction, productivity – Reduce errors

• Tailor to specific user needs and context =

key to making technology inclusive

Introductions: Who Am I?

Marshini Chetty

University of Chicago Computer Science Research Field: Human Computer Interaction (HCI) Areas of Interest: Ubiquitous Computing Usable Privacy and Security Information and Communication Technology for Development (ICTD) Contact: marshini@uchicago.edu JCL 355

Where I am from

Introductions: Who helps make this course run smoothly?

Teaching Assistants

Ozan Gokdemir

Teaching Assistant Contact: ogokdemir@uchicago.edu Office hours: Mondays 1-3pm

Xuefeng Liu

Teaching Assistant Contact: xuefeng@uchicago.edu Office hours: Fridays 9-11am

What is the course format?

My Expectations

• Read required reading before you come to

class

• Participate in discussions
• Give your best efforts in the class projects

and assignments

• Provide honest and constructive feedback

What You Get in Return

• My guidance and commitment to teaching

you about HCI and inclusive design in the most fun and appealing way possible

• Attention to detail and efforts to go

beyond the readings

• Availability to take questions and provide

guidance within reason

Class Overview

• Introduction to Inclusive Technology
• Learn about working with different populations that

are marginalized or under-served

• Learn about tips for success and common pitfalls when

working with different communities

• All couched in Human Computer Interaction (HCI)

– Learn about good and bad design – How to engage in a user centered design process – Learn different HCI data gathering, design, and evaluation techniques – Improve your HCI and design skills

No Required Textbooks

• All required and optional readings will be

posted on class website

• Complete readings before you show up to
• class. You will be quizzed on most

readings.

Course websites

• Course website:

www.classes.cs.uchicago.edu/archive/2020/winter/20370-1

• CANVAS: https://canvas.uchicago.edu/courses/25816

• Piazza: https://piazza.com/class/k4ytsrlynkx70b

Schedule

• Check on the course website – tentative

schedule

• Note the hand in/due dates
• Focus on lecture materials in class
• Fridays are group project focused
• Assignments geared to give you practical

experience with different HCI design methods

• Goal is to make an inclusive technology

prototype by the end of the quarter

Deliverables and Evaluation

• 1. Group Project Assignments (45%)
• 2. Individual Assignments (30%)
• 3. Midterm (15%)
• 4. Class Quizzes (5%)
• 5. Attendance and Participation (5%)

Assignments and Grading

• All assignments are due on the day of class

by the time class starts (11:30am CST)

• Electronic submissions via CANVAS and

posted on your project website for the group assignments

• For IA 2, teams can submit one report per

group/pair

• Everyone gets the same grade as group or

pair

Individual Assignments

• IA 1 – Class Introduction and CITI training

– due Jan 10 (Friday)

• IA 2 – Design Critique – due Jan 24 *Done

in pairs

• IA 3 – Peer Evaluation - due Mar 6

Individual Assignment 1

• Introduce yourself on the class wiki

Hi there, I’m awesome! Let’s make great Inclusive Technology together!

Individual Assignment 2

• Design critique and redesign of a

technology you know that you have had a positive or negative experience with.

• Will be examining it with critical eye as to

how “inclusive” it is depending on who it is serving

• *Done in pairs

Individual Assignment 3

• Be a good team player
• Evaluate yourself and your peers

Group Project

• Iterative design of an inclusive technology

system to address a key HCI problem or issue

• Four group members
• Everyone is expected to contribute
• Tight timeline
• Provide feedback on what you learn from

each part of the project + what you like or dislike

Group Project Assignments

GP0 Group Formation and Project Website Due Jan 17 GP1 Project Proposal Due Jan 29 GP2 Design Alternatives and Poster Due Feb 14 GP3 Prototype and Evaluation Due Feb 28/Mar 2 GP4 Final Report and Video Due Mar 9/Mar 18

GP0 – Group Formation/Website

• Form groups and pick a topic
• Suggestion:

– Pick an under-served/marginalized population* – Pick a problem and focus on the intersection between that and technology

• Make project website and post link on

relevant Piazza thread

• *over 18, avoid vulnerable groups, check with

me to confirm topic

GP1 – Project Proposal

• Understanding the problem

– Describe users, tasks, environment, social context – Describe methods for collecting data – Outline plan for the quarter – Complete ethics and field materials

GP1 Deliverables

• In Class Presentation for feedback
• Final report
• Individual reflection on the project

GP2– User Research and Design Alternatives

• Completing user research and analyzing

results

• Creating design alternatives and exploring

the design space

• Not to develop multiple aspects of same

design but to explore entirely different designs

• Storyboards, mock-ups for multiple different

designs

• Explain decisions

GP2 Deliverables

• Group project report
• Group poster – will have in-class poster

session for everyone to get feedback on their designs.

• Individual project reflection

GP3 – Prototyping and In Class Evaluation

• Create a low to medium fidelity prototype of

the most viable design

• Evaluate this prototype and summarize

feedback to improve the design

• Conduct in class evaluation with real users*

– Use appropriate methods – Analyze results of evaluation – Characterize what’s working and what’s not – Caveat: *May not be target group

GP3 Deliverables

• Low to medium fidelity prototype
• Group project report
• Individual project reflection

GP4 – Final Prototype, Evaluation with Target Users, and Project Video

• Create a higher fidelity revised prototype

based on the feedback received from the in class evaluation

• Evaluate this prototype and summarize

feedback to improve the design

• Conduct evaluation with real target users

– Use appropriate methods – Analyze results of evaluation – Characterize what’s working and what’s not

GP4 Deliverables

• Group project report
• Group project video screening session
• Individual project reflection

Project Teams

• You decide
• Mixed group is best
• Different skill sets
• Consider your schedules
• Pick a good team name

Topic ideas

• Design a gender neutral bathroom with

corresponding fixtures and technology

• Help international students to develop a

support structure in the US

• Help students with mental health issues to

cope with campus life

• Re-envision accessibility on campus

What Makes a Good Project

• Access to domain experts & users
• “Real” clients
• Interesting human issues
• It is ok to use a subset of college students

as your target population for the purpose

• f the class
• You need to do user research with a bare

minimum of 5-7 users

Participants & Ethics

• Institutional Review Board (IRB)
• Reviews all research involving human (or

animal) participants

• Safeguarding the participants, and thereby

the researcher and university

• You will submit all IRB materials to us to

ensure you’re conducting research ethically

• You will complete CITI training by Friday

How do we create inclusive technology?

User Centered Design

• Have systematic ways to identify and

consider relevant human factors in your design

– Helps reduce the number of decisions made out

• f the blue

– Helps focus design activities – Helps document and defend decisions that may be reviewed later

• Also considers factors beyond those of just

the human and the technology

USER NEEDS DESIGN/PROTOTYPE IMPLEMENT EVALUATE USER-CENTERED DESIGN

Why a Design Process?

• It helps us get started with a proven tack
• It prevents “designer’s block”
• It keeps us directed towards a final product
• It helps us stay on schedule and within cost
• It helps us measure design progress
• It helps us to communicate where we are to others
• It prevents us from omitting important steps
• It is more reliable than intuition
• It forces us to iterate!
• It helps us to put the user first!

What is Designed?

• Artifact view

– The object, device, or system that is designed

• Holistic view

– The interaction, the flow, the user’s experience is designed – All potential users, all stakeholders, manuals, tutorials, help systems, customer support – Think in terms of users’ goals

• Artifacts have no goals
• People have goals
• Keep users in center in beginning, middle, and end

Being inclusive: Know the user

• Physical abilities
• Cognitive abilities
• Personality differences
• Skill differences
• Cultural diversity
• Motivation
• Special needs

So what’s this class about again?

• Learn more about why we need to make

technology inclusive

• Helping you to develop a critical eye for good

and bad design

• Giving you deep hands on experience with

various HCI design methods

• Getting you to follow a user centered design

process to design an inclusive technology system using the techniques from class

Coming up on Wednesday

• Getting started on Understanding User

Needs

• Start work on IA1 (due this Friday)
• Start forming your teams and

brainstorming topics

• Let us know if you need access to course

materials

Get in touch:

Office hours: Fridays 2-4pm (Sign up in advance) or by appointment JCL 355 Email: marshini@uchicago.edu