Summary
Traditional design metrics and KPIs are often geared towards measuring product success. Dark metrics challenge this paradigm by proactively measuring the unintended yet harmful psychological, social, and physical effects of our technologies. The examples within digital health are plentiful. From accelerating burnout among clinicians to widening racial disparities in quality of care, we can only reach the height of our most courageous solutions when we expose our deepest failures.
Key Insights
-
•
Traditional product metrics often ignore the broader individual and societal impacts of digital health technologies.
-
•
Dark Metrics is a framework focusing on measuring disempowerment, exclusion, addiction, and distraction caused by health tech.
-
•
Disempowerment occurs when technology undermines user autonomy, especially in sensitive healthcare decision-making.
-
•
Racial bias in AI can manifest indirectly, as in algorithms using proxies like healthcare costs that perpetuate inequities.
-
•
Co-creating design solutions with diverse voices is critical to proactively identifying unintended consequences.
-
•
Measuring unhealthy engagement requires going beyond 'engagement' metrics to include wellbeing indicators like stress or eye strain.
-
•
Distraction from clinical tools (e.g., EMRs) can reduce quality of care by pulling medical professionals away from patient interaction.
-
•
Embedding racial equity rubrics into the design process helps ensure inclusive user experiences beyond just product visuals.
-
•
Augmented intelligence should support, not replace, human decision-making especially in healthcare.
-
•
Early, collaborative risk ideation exercises like 'premortems' are recommended to anticipate potential harms before launch.
Notable Quotes
"Traditional product metrics focus narrowly on the product itself, missing what success means for the people using our technologies."
"Our tools are meant to support and enhance, not to take over — we call this augmented intelligence at IBM Watson."
"An algorithm that doesn’t explicitly use race but uses healthcare costs as a proxy can perpetuate racial discrimination."
"Exclusion doesn’t have to be explicit — you just have to be indifferent to it."
"The difference between technology and slavery is that slaves are fully aware they are not free."
"Doctors don’t want to be on a machine all day; they want to help people."
"Designing for people means acknowledging where we might be exclusionary and embedding equity like accessibility."
"If the product doesn’t allow people to override decisions or control their data, it’s likely disempowering."
"Collaborative conversations and diverse co-creation help catch blind spots and biases in design."
"We have to ask before building something new: what could possibly go wrong?"
Or choose a question:
More Videos
"I wish I could tell my 22-year-old self what to stop doing and what to embrace to be a better designer."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Knowing your subject matter as a UX leader is just as important as knowing your craft."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance isn’t about choking creativity, it’s about putting bounds and clarity that enable purposeful collaboration."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"The time for action is now, and it must be collaborative."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Design your processes around learning, have blameless post mortems and celebrate failures especially."
Brenna FallonLearning Over Outcomes
October 24, 2019
"It’s human infrastructure—community organizing, unions, activists—that saves the day when other infrastructures break down."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Creating hypotheses from pain points with measurable success criteria helped prioritize which to pursue."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Knowledge needs to be thought of as a reusable circular process, not a linear one ending at project completion."
Designing Systems at Scale
November 7, 2018
"Most product teams work linearly, but systems thinking captures the real-world complexity of moving forward and sometimes stepping back."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
