Designing Data Services
Summary
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
"Monoculture in stories is like having just one narrative that doesn’t capture the full reality."
Kwabena Opoku Leonie Annor-Owiredu Sam LadnerMethodological toolkit for unique research impact
March 11, 2026
"Design for emotion to create experiences that resonate beyond functionality."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"Accessibility ownership should never fall on just one person but be understood and shared across entire product teams."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"Design is open source; everybody participates, but you need facilitation to make good on that promise."
Bob Baxley Sara Asche Anderson Sharon Bautista Frank Duran Jamie Kaspszak Abbey Smalley Sylas SouzaTheme 4: Discussion
January 8, 2024
"Getting weird in Miro lets people play and connect remotely without pressure to prepare or present."
Shipra Kayan Tess DixonHow Tess Dixon Facilitates Team Engagement and Collaboration at Condé Nast Using Miro
October 1, 2021
"From fast-paced tech worlds, you will appreciate the patience and perseverance it takes to move an old champion."
Lada GorlenkoTheme 1: Intro
January 8, 2024
"The dream of cross-functional agile collaboration is there, but it’s quite hard to realize that because teams don’t have enough time to build trust."
Abby Covert Tomer SharonPanel: Collaboration Tools
November 6, 2017
"Design operations is a servant leadership function you only get noticed when things go terribly wrong, and that’s fine."
Kevin BethuneGatekeepers and Servant Leadership
January 30, 2020
"I see this opportunity to imbue these rigid, bureaucratic corporate contexts with humanism to put people at the center of the work."
Lori Muszynski Peter MerholzKeeping Design Weird
October 2, 2023
Latest Books All books
Dig deeper with the Rosenbot
How can designers handle modality routing between voice, chat, UI, agents, and human support?
How do constant reorganizations in tech companies impact employee motivation and career decisions?
How can organizations prevent design system knowledge from being an undocumented API surface reliant on specific individuals?