Designing Data Services
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
"At the turning point, the team realized they were in charge of their own process and got engaged."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"If there’s a performance gap, don’t sit on it; it doesn’t age well and hurts the team, employee, and business."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"We share the inconvenience of meeting times across time zones, alternating so no one team always bears it."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"We treat our shared tooling and design system as a product with a dedicated team maintaining reusable components and governance."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Working in healthcare means every tiny moment in a patient’s experience can either uphold or erode their dignity and sense of control."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"Generative fill is now the most used tool in Photoshop, with 3 million users and over 2.3 billion images generated."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Service design is 10% connecting the dots and 90% creating the conditions that bring those dots closer together."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"If you press the exact same button today and tomorrow you get two different results, that’s non-deterministic UX."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Our design ops team was a step behind the growth of our design team, solving the wrong problems at the wrong scale."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
How can personal energy assessments and understanding control help in managing work stress and growth?
How can research repositories score or show the impact of research recommendations to enhance organizational learning?
What strategies help non-researchers build empathy skills to conduct better user interviews?