This workshop will provide a foundation for addressing human values in the design of collaborative information systems. Participants will be introduced to the concept of values in design, discuss tools and methods for addressing values in system design, and through active engagement in a set of design challenges, gain familiarity with the opportunities and challenges for bringing a consideration of human values into the design process. BIBLIOGRAPHY Borning, Alan, and Muller, Michael. 2012. “Next Steps for Value Sensitive Design.” Proceedings of CHI 2012: 1125–1134. Flanagan, Mary, Daniel Howe, and Helen Nissenbaum. 2008. “Embodying Values in Technology: Theory and Practice.” In Information Technology and Moral Philosophy, edited by Jeroen Jvan den Hoven and John Weckert. Cambridge: Cambridge University Press. Friedman, Batya, Peter H. Kahn, and Alan Borning. 2006. “Value Sensitive Design and Information Systems.” In Human-Computer Interaction in Management Information Systems: Foundations, edited by P. Zhang and D. Galletta, 348–372. Armonk, New York: M.E. Sharpe. Halloran, John, Eva Hornecker, Mark Stringer, Eric Harris, and Geraldine Fitzpatrick. 2009. “The Value of Values: Resourcing Co-design of Ubiquitous Computing.” CoDesign 5 (December 1): 245–273. doi:10.1080/15710880902920960. Kling, Rob, and Susan Leigh Star. 1998. “Human Centered Systems in the Perspective of Organizational and Social Informatics.” Computers and Society 28: 22–29. Knobel, Cory P., and Geoffrey C. Bowker. 2011. “Values in Design.” Communications of the ACM 54: 26–28. Muller, Michael J., and Sarah Kuhn. 1993. “Participatory Design.” Commun. ACM 36: 24–28. doi:10.1145/153571.255960. Mumford, Lewis. 1934. Technics and Civilization. New York: Harcourt Brace. Shilton, Katie. 2012. “Values Levers: Building Ethics Into Design.” Science, Technology & Human Values (April 23). doi:10.1177/0162243912436985. http://sth.sagepub.com/content/early/2012/04/19/0162243912436985.abstract. Weiner, Norbert. 1954. The Human Use of Human Beings. Boston: Houghton Mifflin. Winner, Langdon. 1980. “Do Artifacts Have Politics?” Daedalus 109.

1. Values in Design for
Collaborative Systems
Matt Bietz |Cory Knobel | Katie Pine
University of California, Irvine
image: Reto Fetz
CTS 2013 | San Diego | May 20, 2013

2. Who Are We?

3. Values in Design
• Addressing human values in the design
process
• Values may be embodied in technical systems
and devices
• Considering values provides benefits
– Value alignment with stakeholders
– Opens new design opportunities
• Especially important for collaborative systems

4. Agenda
13:30-18:00
• Designing for People
• Values in Design
 Icebreaker
• Electronic Medical Records
 Stakeholders
• Break: 15:30-16:00
• Using Values in Design
 Eliciting Values
• EMR Case Study
 Value-based Design
• Wrap-up
image: Reto Fetz

5. DESIGNING
FOR PEOPLE
From User-Centered to
Human-Centered Design

6. User-Centered Design
• Understand users
• Involved users in
development
• User-centered
evaluation
• Iterative process
• Address the whole
user experience
• Include multiple
perspectives
A process in which the needs, wants, and
limitations of end users of a product are given
extensive attention at each stage of the design
process. (Wikipedia)
From ISO 9241-210

7. Shortcomings of UCD
• Defines people in functional terms
– A person is more than a collection of tasks
• Important to consider larger contexts of
activities
• Difficult to include non-functional
requirements

8. People are more than Users
• Holistic – not just a disembodied task or set of
cognitive process.
• Social – not stand-alone organisms
• Learning – People adapt and learn. Behaviors
change.
• Complex – Human systems are as (or more)
complex than technical systems.

9. Human-Centered Design (1)
• Expand design requirements beyond the task
• Design to complement human skills
• Design in context
• Design for change and adaptation
• Embrace complexity

10. Human-Centered Design (2)
• Recognize that computer systems structure
social relationships
– Respect other forms of human social organization
• Recognize the limits of design
• Articulate the values that are at stake
– For both system audiences and designers
– Whose purposes are served in the development of
the system?

11. HCD and Collaborative Systems
• Tend to bring together people from different
groups
– Reveals underlying value conflicts
• Ongoing and pervasive interaction
– Difficult to define boundaries of tasks
– Properties of use emerge over time
• Embracing this complexity in the design
process will produce better collaborative
systems

12. VALUES IN DESIGN
or more formally
Social Values in the Design
of Information Systems and
Technology
considers human values as equal
design inputs to technical
requirements

13. A few examples
• Geolocation and
sensors
• Identity and social
desirability
• Search algorithms
• Games

14. When and where to consider values
• Defining goals of the system
• Expanding requirements analysis to include all
users who touch the system
• When? From the beginning and throughout
the lifecycle (as well as after release).

15. How to expose values
• Ask where people are dissatisfied with the
current system. Think about what
fundamental personal needs are not being
met?
• Conduct observational studies. Watch how
people use the current
system, prototypes, and the redesigned
system. What motivates their choices and
actions?

16. How to expose values (con’t)
• Attach values propositions to evolving system
design diagrams and documentation. What
are the values each design decision impacts?
How? Learn to become comfortable talking
about values as valid aspects of the user
experience
• Include values rationale in the final
documentation. Make your grounded design
research transparent.

17. Making values choices flow with the
work of system design
• Values in Design – starting with a set of core
values as guiding design principles
• Values-sensitive design – inserting
provocations that continually challenge design
assumptions
• Values Levers – recognizing when values
discussions are naturally happening and
making them do productive and creative
work.

18. Case Study: An EMS Field System
• Conducted by Joshua Gelman and Cory Knobel in Pittsburgh, PA

19. Activity: Icebreaker
(15m)
• Introduce yourselves to
others in your group
• Identify a system you have
designed, worked with, or
used
• Identify who this system
was primarily built for –
who was the “client” for
the design?
image: Reto Fetz

20. ELECTRONIC
MEDICAL
RECORDS
A Brief Overview

21. “We will make sure that every doctor’s office
and hospital in this country is using cutting edge
technology and electronic medical records so
that we can cut red tape, prevent medical
mistakes, and help save billions of dollars each
year.”
-President Barack Obama, 12/6/2008

22. Patient Care
Patient Chart & History
Order entry
Test results
Prescriptions
Management
Scheduling
Bed management
Admissions & discharges
Administration
Billing
Supply management
Accountability
Clinical decision support
Automatized safety interventions
Outcomes reporting
image: Doug Waldron

23. EMRs are Getting Bigger
• Huge adoption
– Both carrots and sticks
• Huge expectations
– Lower health care costs
– Improve patient safety
– Increase medical
knowledge
• Similar to ERP systems

24. How do you
give a patient
medication
using an EMR?
image: ShawnOster

25. First steps in EMR:
• Home medication reconciliation
• Patient medical history
• Note any drug allergies
Image: KOMUnews

26. • Document patient symptoms
• Select drugs and order
• “Black box” alert
• Pharmacy verification
• Check inventoryimage: r.nial.bradshaw

27. • Security clearance to
access drugs
• Patient verification
and double-check
• Patient education
about the drug
image: Kratka Photography

28. • Documentation
– Treatment
– Drug response
• Review
treatment plan
• Bill insurance
• Quality
improvement
• Audits / lawsuits
image: Bill Branson, National Cancer Institute

29. Activity: Stakeholders
(15 min)
• Work in same groups
• Use the worksheet
• Identify who is
involved and
impacted at each
step
• We will discuss as a
group after
image: Reto Fetz

30. Intermission
Please return
by 4:00pm

31. Welcome Back!
• Designing for People
• Values in Design
 Icebreaker
• Electronic Medical Records
 Stakeholders
• Break: 15:30-16:00
• Using Values in Design
 Eliciting Values
• EMR Case Study
 Value-based Design
• Wrap-up
image: Reto Fetz

32. USING VALUES
IN DESIGN

33. Working with Values as Design Inputs
• Where can we find values articulated?
– In the users
– In organizations/institutions
– In designers and developers
– In societies
– In cultures
How can we accommodate these differing values?

34. How to expose values
• Ask where people are dissatisfied with the
current system. Think about what
fundamental personal needs are not being
met?
• Conduct observational studies. Watch how
people use the current
system, prototypes, and the redesigned
system. What motivates their choices and
actions?

35. How to expose values
• Attach values propositions to evolving system
design diagrams and documentation. What
are the values each design decision impacts?
How? Learn to become comfortable talking
about values as valid aspects of the user
experience
• Include values rationale in the final
documentation. Make your grounded design
research transparent.

36. Two Research-Based Approaches
• Values Provocations
– Based on the Value Sensitive Design (VSD)
practices developed by Batya Friedman
(UW), Alan Börning (UW) and Helen Nissenbaum
(NYU)
• Values Levers
– Based on organizational ethnography research by
Katherine Shilton (UMD)

37. Values Provocations
• What are the questions or provocations that
can prompt discussions of values?
• Tools such as VSD Envisioning Cards can serve
as consistent reminders to consider various
aspects of human values, both individual and
social.
• How can this translate from discussion into
design practice?

39. Values Levers
• Identifies the occasions and opportunities
within systems and technology development
for design/development teams to articulate
values embedded into built projects
• Seven primary levers (to open up the “black
box” of values discussions during
development)

43. VALUES PERSONAS
Create a values-based
persona for your assigned
stakeholder.

44. Using Personas
• Profiles of individuals who represent
stakeholder types
• Can be used as a design target
• Helps to ground vague design requirements in
a concrete example
• Typically include brief bio, goals, task
requirements, skills, personality

48. Activity: Values Personas
(30 min)
• Create a value-focused
persona for your assigned
“client”
• What do you think they value
– At work?
– At home?
– In life?
• Capture these values on flip
charts
image: Reto Fetz

49. EMR DESIGN CASE
Once upon a time, in
the far-off land of
Labor & Delivery…

50. EMR Design Case
• From hospital fieldwork conducted by Katie
Pine
• A brief example from a nurse’s morning
• EMR use in the context of patient care
• Basis of next activity – think about how this
fits or conflicts with your persona’s values

54. Image: hitthatswitch

58. Photo: ministry health

59. Image: Birth Sense blog

60. Image: Sloan-Kettering Cancer Center

65. Image: UMHealthSystem

68. Activity: Redesign
(30 min)
• The persona you
developed is your
client
• Using the case you just
heard
– Identify potential
problems
– Propose solutions that fit
your client’s values
• Use the flip charts to
capture design ideas
image: Reto Fetz

69. Wrapping Up
• Bibliography will be
available at:
http://evoke.ics.uci.edu
• Let us know if you have
questions or comments
• Please fill out the brief
survey before you leave

70. Thank you!!!
Matthew Bietz
mbietz@uci.edu
Cory Knobel
cknobel@uci.edu
Katie Pine
khpine@uci.edu