Summary
When is DesignOps about more than building tools and systems that improve the effectiveness of R&D? For athenahealth, our DesignOps team has housed two cross-product teams—by organizational necessity at first—that have become critical early adopters of the instruments and programs their DesignOps colleagues have developed.
Key Insights
-
•
Athena faced a massive 'mountain' of design debt from decades of federally mandated, checkbox-heavy healthcare software.
-
•
The end of federal EHR incentives in 2016 forced Athena to shift focus from speed of payment to usability and design.
-
•
Transitioning from waterfall to Agile enabled Athena to reorganize into product zones and scrum teams with generalist UX designers.
-
•
Design ops was established to reduce friction for generalist designers by centralizing specialists and building supporting tools and systems.
-
•
A key initiative was auditing 55 mission-critical workflows using Nielsen's 10 heuristics to create quantitative 'design quality' scores.
-
•
Introducing design heuristics and scoring provided a shared language for leadership and product teams to discuss and prioritize design issues.
-
•
Design quality audits were resource intensive but were scaled via asynchronous review apps and integrated into release dashboards.
-
•
A major knowledge management challenge was caused by tagging knowledge based on unstable org restructuring, prompting adoption of a job map taxonomy tied to user needs.
-
•
Design ops at Athena owns not just designer enablement but also influences product development processes and hosts cross-product scrum teams focused on visionary design.
-
•
Ongoing questions include how design ops can balance operational support with strategic leadership and whether they should lead or enable cross-team collaboration.
Notable Quotes
"I actually joined our design ops team about six months after it was created and I am not the head of design ops but part of its leadership."
"We built software to make birthing clinics more efficient, and for 18 years we wrestled with whether we were a software-supported service or a service-supported software company."
"No doctor wants to use an EHR, and our competition was basically who was the least bad option."
"In 2016, the federal incentives stopped and the market shifted—the buyers started caring about usability, not just getting paid faster."
"We were a waterfall shop for years but kicked off a two-year Agile transformation that completely redesigned our product and design teams."
"Our new UX model placed generalist designers on scrum teams supported by centralized design ops specialists."
"We audited 55 mission critical workflows over nine two-week sprints and scored them using Nielsen’s heuristics for design quality."
"Introducing hard numbers and a shared language around design helped product and engineering leadership better prioritize improvements."
"We found that tagging knowledge by org structure was a mistake due to frequent reorgs causing instability and loss of findability."
"We see design ops as providing constancy in culture amid changing teams, priorities, and market conditions, operating as a 'slower changing' layer."
Or choose a question:
More Videos
"The 1500 are designers, we don't distinguish strictly between UX or visual or industrial—they all bring design to the org."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Developing trust means showing you understand what it takes to get something shipped, that you’re reliable, and that people can be vulnerable with you."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Everything that has been put online, someone like us made and put there; we bake our own biases into it."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Policy change is the backbone of effective climate strategies in urban areas."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Growth and learning is your long term change management plan."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Thick data is the opposite of big data; it’s stories, qualitative, and crucial during moments of rapid change."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Creating hypotheses from pain points with measurable success criteria helped prioritize which to pursue."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Context-related data gathered through qualitative research is the first to reach our decision-making centers in the brain."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
