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 imperative that we maintain hope, even when the harshness of reality may suggest the opposite. — Paola Freire"
Angelos ArnisNavigating the Rapid Shifts in Tech's Turbulent Terrain
October 2, 2023
"Interviewing for design ops needs a special toolkit that shows how to present your skills and prepare effectively."
John Calhoun Rachel PosmanBring your DesignOps Story to Life! The Definitive DesignOps Book Jam
October 3, 2023
"Look at your partnership with product and engineering as a design task—understand their pressures and needs."
Alfred KahnA Seat at the Table: Making Your Team a Strategic Partner
November 29, 2023
"No matter how good I think I am at my job, it doesn’t make me a good parent."
Dan WillisEnterprise Storytelling Sessions
June 3, 2019
"You have to give respect to get respect—it's the foundation for connecting people across teams."
John Maeda Alison RandAbout Design Organizations (Videoconference)
May 13, 2019
"We had four different supply chains fighting for priority, with different business teams and conflicting systems."
Anat Fintzi Rachel MinnicksDelivering at Scale: Making Traction with Resistant Partners
June 9, 2022
"There is a common thread in craft: dignity, purpose, utility, and beauty."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"There was a need around definition but also understanding the value our teammates would find in this role."
Kristin SkinnerTheme 1 Intro
September 29, 2021
"Design is a rendering of intent, and at the national level, this intent shapes everything from innovation to being a lovable city by 2025."
Maish NichaniSparking a Service Excellence Mindset at a Government Agency
December 9, 2021
