Summary
Cross-disciplinary collaboration is key to tackling large scale change in hypertension rates (Margins of Victory) in underserved communities (Innovation at the Margins). Low income minoritized populations have shown to have a high prevalence of hypertension but a low treatment rate . There are many factors that play a role in these statistics many of them which are historical and systemic. In order to design a hypertension study for these populations, co-design methods that emphasize collective good must be employed by a comprehensive team. Our process to build this study focused on sharing power with members of the community to decentralize the designer and build design capability with the participants. We prioritized building relationships to combat mistrust of healthcare professionals and address difficult topics like social determinants of health (healthcare access, housing challenges, employment, etc) – both key factors in high hypertension rates. This presentation will bring together the collaborative team that built the Pressure Check study. First, a Yale cardiologist who is an expert in this space and acknowledges the influence and perspective that the design process can provide. The second speaker is a design research and strategy professional who defined an inclusive and relational protocol that tapped into the deepest needs of the study community and translated them into the study materials. The third, is a visual designer who incorporated the learnings into patient education and study tools to overcome deeply ingrained perspectives on healthcare. This team and the outputs demonstrate how critical it is to have a team that brings in shared and lived experiences into service design.
Key Insights
-
•
Healthcare data fragmentation creates delays and risks in patient care, as illustrated by John’s story.
-
•
Genomics England evolved from a sequencing project to building modular data services for NHS integration.
-
•
Modular data services enable flexible, non-linear clinical workflows rather than rigid, linear processes.
-
•
Service design embedded early in technical leadership allows anticipation of strategic infrastructure needs.
-
•
Developers are the primary users of data services, so prioritizing their experience is essential.
-
•
Use case-driven design helps identify meaningful data service modules that solve common problems.
-
•
Comprehensive documentation, testing environments, and support channels are key for developer adoption.
-
•
Storytelling through patient and clinician use cases makes technical discussions accessible and actionable.
-
•
Iterative, slice-of-value delivery reduces risk compared to big-bang transformations in healthcare IT.
-
•
Service designers benefit from engaging deeply with technical teams and learning enough to speak their language.
Notable Quotes
"This kind of issue—different hospital IT systems not talking—is happening almost every day to patients and doctors."
"Data standards are like selecting English as the common language even if systems natively speak Portuguese or Spanish."
"We are designing the data services that developers can use to build the clinician-facing services, not the services themselves."
"Building and nurturing relationships with engineers is key because they hold a massive stake in the service."
"It is uncommon to encounter service design working at the technical level, but this is precisely where it can have exponential impact."
"Imagine handing a developer a box set of Lego with instructions rather than a random selection of bricks."
"Use cases give human meaning to technical components and help product teams prioritize slices of value."
"Technical colleagues are amazing problem solvers and service designers have more in common with them than they might think."
"If service design wasn’t there, we probably wouldn’t consider data services stitched together to create seamless experiences."
"Mapping the data journey through technical infrastructure is like mapping a user journey—be curious and ask questions."
Or choose a question:
More Videos
"It is part of your role to say no, enforce guardrails, and stop people pleasing when democratizing research."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"Customers rarely ask us to fix inconsistencies directly; we must watch activation rates and confusion instead."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"When you have a success, measure time saved and reduction in bugs to build your internal business case for the system."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"Adoption is the only thing that matters in innovation — if you’re not changing someone’s behavior, you may have invented something, but you have not innovated."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Designing for change management is just as important as the product experience strategy."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Some people prefer their beliefs to data even in academia, which may surprise you."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"If you signed up for a cohort, please make sure you’re in your private cohort channel to meet and discuss with your group."
Bria AlexanderOpening Remarks
June 9, 2021
"Everyone is looking for ways to build better products and go faster."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"Soft eyes means zooming between the particular tree and the whole forest to see the bigger picture."
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024