Centering Patients and Clinicians in a Complex Government Ecosystem
Summary
Key Insights
-
•
Federal healthcare product teams often face unpredictable legislative shifts that require maintaining multiple roadmap iterations.
-
•
User story mapping helps align diverse clinical stakeholders and clarify priorities in complex healthcare projects.
-
•
Clinicians use outdated documentation methods like pen and paper alongside legacy digital systems.
-
•
Close, continuous collaboration between product managers, UX designers, and researchers is key to success in regulated environments.
-
•
Agile frameworks inherently support adaptability needed in government healthcare product development.
-
•
Direct access to patients is often restricted, so teams rely heavily on clinicians' perspectives to infer patient needs.
-
•
User story maps focus on visible user journeys and usually do not represent backend technical work like database schemas.
-
•
Contractors struggle when not fully informed on decisions due to restricted access to federal-only meetings and data.
-
•
Visual, shared artifacts like user story maps foster internal alignment even if too detailed for external stakeholder presentations.
-
•
Product teams must accept limited control over roadmaps and proactively prepare for inevitable pivots in priorities.
Notable Quotes
"Healthcare IT is a highly regulated industry with a lack of standardization and many legacy systems."
"Prioritizing across a complex ecosystem of business owners requires deep alignment between product and UX or the product never moves forward."
"We often have to rely on Google Newsfeeds to stay informed about legislative changes that impact our roadmap."
"Our users still rely on email, Excel spreadsheets, pen and paper, and even post-it notes for documentation."
"User story mapping helped us put the needs of clinicians front and center in a complicated federal healthcare space."
"We decided not to build a new app but instead integrate within the legacy electronic health record system."
"Working in agile keeps our teams nimble and able to adapt to frequent reevaluations and shifting priorities."
"We don’t get direct access to patients, so we rely on clinicians to represent patient needs to us."
"Sometimes information we need as contractors isn’t shared due to federal restrictions, which makes decision-making challenging."
"We created a change log to document roadmap and user story map updates due to evolving requirements and regulations."
Or choose a question:
More Videos
"The biggest myth of all is you can't teach creativity."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"Making your chief legal officer your best friend as a designer makes a lot of sense."
Amy MarquezINVEST: Discussion
June 15, 2018
"When you look at data without training, confirmation bias makes you just find what you already believe."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Splitting people’s allocation across different teams created work-life balance issues requiring more oversight."
Alicia MootyDesign Staffing Models
September 30, 2021
"I am not throwing away your UX."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"You can’t really advocate for UX or move an organization forward without interacting with your team and business colleagues."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Data entry is the enemy; automation is the key to making research repositories successful."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Nobody loves it when someone from another department shows up to tell people how to do their jobs better."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Embedded squads build domain expertise but risk losing knowledge if someone leaves, while centralized teams help reduce duplicated effort."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
