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."
Dig deeper—ask the Rosenbot:
More Videos
"UX research needed to be a team sport involving all disciplines rather than the few learning on behalf of the many."
Monty HammontreeThe Future of UX Research (Videoconference)
December 3, 2020
"There are never truly conflicting futures between donors and communities—your job is to find the bridge that unites them."
Liz EbengoThe Burden on Children: The Cost of Insufficient Post-Conflict Services and Pathways Forward
December 4, 2024
"Content first design should happen after sketching but pretty early to help shape the wireframes and concepts."
Billy CarlsonTips to Utilize Wireframes to Tell an Effective Product Story
June 6, 2023
"Making bite-sized secondary research accessible allows busy designers to start right away without additional workload."
Saara Kamppari-MillerInclusive Design is DesignOps
September 29, 2021
"Innovation is about being fearless. There’s a rule or a process, but that doesn’t mean it’s right—keep pushing and breaking things."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"We trashed our old content design competencies because content designers should hold themselves to the same standards as product designers."
Jonathon ColmanHow to Maximize the Impact of Content Design
January 8, 2024
"We were told, can you please make the user experience exactly the same a year from now."
Maria SkaadenContinuous Design: One eye on the horizon and the other on the next wave
November 8, 2018
"We wanna make sure that we don't just hand it over as a black box, but also provide contextual information."
Bryce Benton[Demo] AI-powered UX enhancement: Aligning GitHub documentation with USWDS at Austin Public Library
June 4, 2024
"The satisfaction score is going down even though average salary is going up — that’s something interesting we should dig into."
Marc FonteijnFirst Insights from the 2025 Service Design Salary(+) Report
December 4, 2024
