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
-
•
Lack of interoperability between healthcare IT systems causes delays and disrupted patient care, as seen in John’s genomic test example.
-
•
Genomics England moved from a research project to an integrated platform supporting NHS routine care with genomic data.
-
•
Modular data services using common data standards enable flexible, reusable technical components for multiple healthcare applications.
-
•
Service designers at Genomics England work alongside engineers and bioinformaticians early to ensure technical infrastructure serves real-world needs.
-
•
Service maps help identify data transformation patterns to create standalone data service modules usable across different use cases.
-
•
Designing data services focuses on developers as primary users, enabling them to build clinician-facing services like cascade testing or trial selection.
-
•
Comprehensive documentation, developer tooling, and support channels are critical to developer adoption of data services.
-
•
Framing data services through patient and clinician perspectives helps stakeholders make informed decisions and fosters broader inclusion.
-
•
Service design applied at the technical data layer can have exponential impact by aligning infrastructure with business objectives and user needs.
-
•
Collaboration and curiosity enable service designers to overcome intimidation by technical layers and build shared language with developers.
Notable Quotes
"The lack of consistency between healthcare IT systems causes critical information delays and interrupted care."
"Data standards are like selecting English as the common language, even if systems natively speak Portuguese or Spanish."
"Service designers embedded in leadership can preempt strategic directions and influence technical projects early."
"We are designing data services for developers, not final clinician-facing experiences."
"APIs need to provide capabilities like verifying patient identity to ensure data access is accurate and secure."
"Imagine data capabilities as Lego bricks versus a box set with instructions to build specific models."
"Developer experience hinges on clear documentation, sandboxes, sample data, and responsive support."
"Speculative use cases connect technical components to human impact and help prioritize work into slices of value."
"Don't shy away from technical conversations; service designers should map data journeys like user journeys."
"The impact of service design at the data service level is exponential, making infrastructure more human scale."
Or choose a question:
More Videos
"Slack is the heart and soul of this conference — that’s where you ask questions, get help, and connect with others."
Bria AlexanderOpening Remarks
September 9, 2022
"When I started out, I knew nothing about digital sustainability."
Nick LewisDesigning and building low-carbon websites independently
November 18, 2025
"People like innovation but hate change because change feels personal and threatening."
Ryan RumseyBusiness Influence Without Losing Your Soul
January 14, 2021
"Data scientists are part stats geek, part hacker, and part entrepreneur."
Chris ChapoData Science and Design: A Tale of Two Tribes
May 13, 2015
"Objectives are qualitative, inspirational statements about the future we want to create for our customers without mentioning any solutions."
Jeff GothelfWho does what by how much?
November 20, 2025
"You have to choose what you’re going to do in order to win—and implicitly what you’re not going to do."
Harry MaxPriority Zero: Some Things are More Equal than Others
June 9, 2016
"Listening is different than conversation, even though it looks and feels similar."
Jesse ZolnaInviting the Whole Org to Come See For Yourself
March 30, 2020
"Your partners need to trust that you are going to make their goals your goals."
Jess GrecoClaiming your power: Practical tools for amplifying your unique voice
March 13, 2025
"The head is where we are logical and rational and ask why do we need to include inclusion in Design Ops."
Saara Kamppari-MillerTheme Three Intro
September 9, 2022
