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
-
•
Data services must be designed with user needs in mind to improve the quality of healthcare.
-
•
Interoperability issues in healthcare IT can significantly delay patient care and negatively impact outcomes.
-
•
Modular technology and data standards facilitate flexible integration of genomic data into healthcare services.
-
•
Effective collaboration between service designers and technical teams is key to developing seamless data services.
-
•
Using service maps helps identify critical data flows and potential use cases for new data services.
-
•
Service design should focus on both developer experiences and the end-user experiences to ensure comprehensive solutions.
-
•
Early involvement of service designers can help ensure that technical infrastructures meet user needs effectively.
-
•
Creating clear documentation and support tools for developers is essential for successful integration of data services.
-
•
Service design can have exponential effects when applied at a technical level, connecting infrastructure to user experiences.
-
•
Maintaining a holistic view of data services allows for better foresight into future healthcare needs.
Notable Quotes
"This kind of issue happens almost every day to patients and doctors."
"If the technical infrastructure isn't built for the real context of use, it can risk the quality of care."
"We are adopting common data standards and modular technology to better serve the healthcare system."
"Identifying these patterns is not enough to create a data service; we need to solve for a collective need."
"When discussing data services in technical terms, it can exclude some people from the conversation."
"Our work follows two parallel tracks — one for the developers and another for the patients and healthcare providers."
"This layered approach allows us to create flexible and future-proof services."
"The impact of service design can be exponential when applied to data services that will be foundational to human-facing ones."
"Technical colleagues are amazing problem solvers, so engaging with them is critical for service design."
"We hope to spark your curiosity about data services and continue the conversation."
More Videos
"Collaboration is crucial to navigate ambiguity in government service design projects."
Ed MullenDesigning the Unseen: Enabling Institutions to Build Public Trust
November 16, 2022
"When I suggest that we could be catalysts for robust action, this is what I mean."
Peter LevinSolve a Problem Here, Transform a Strategy There: Research as an Occasion for Expanding Organizational Possibility
March 25, 2024
"Language in OKRs is critical - are we using user-centric words?"
Bria Alexander Benson Low Natalya Pemberton Stephanie GoldthorpeOKRs—Helpful or Harmful?
January 20, 2022
"We are stronger when we work together towards a unified goal"
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"Show them, don’t tell them."
Amy MarquezINVEST: Discussion
June 15, 2018
"What you build matters, but what matters more is if you learn."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Resilience should be supported by organizational structures, not just individuals."
Brian MossWhat Does it Mean to be a Resilient Research Team?
March 9, 2022
"Our mission is about unlocking the potential of those who advance the world."
Adel Du ToitGet Your CFO To Say: 'Our Strategic Goal is User Obsession'
June 10, 2022
"We're super ops, and we've discovered we have a lot of superpowers."
Kate Koch Jean-Claire FitschenFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 29, 2021
