Lessons From the DesignOps Journey of the World's Largest Travel Site
Summary
Key Insights
-
•
Lack of a design lead for 1.5 years at TripAdvisor caused fragmented, siloed design efforts and multiple conflicting design systems.
-
•
TripAdvisor’s culture focused heavily on small optimizations yielding big revenue impact, which made teams resistant to broad changes and design system stability.
-
•
Design systems require clear governance, including accountability for pattern approval and an escalation path, which TripAdvisor developed with McKinsey.
-
•
Incentives like cash prizes helped initially motivate teams to contribute to the design system, but sustained engagement required deeper ownership.
-
•
A single source of truth for design patterns aligns designers, developers, and product managers and improves efficiency and collaboration.
-
•
Real-time communication channels like dedicated Slack groups serve as effective support desks, increasing clarity and responsiveness.
-
•
Design and engineering alignment is critical to achieve design-to-code parity, avoiding confusion and mismatched implementations.
-
•
Opening design reviews to project managers and researchers fosters cross-functional understanding and balances user experience and business goals.
-
•
Onboarding and education about what design systems are and their value is essential since many skilled professionals may never have used one at scale.
-
•
Sustaining change requires empowering others to champion initiatives, adapting messaging to different roles, rather than one lone advocate.
Notable Quotes
"TripAdvisor hasn’t had a design lead for about 1.5 years, leaving teams to work as individuals in silos with their own design systems."
"People saw small changes as having very large impact; a half-percent increase in conversion could mean 12 million dollars in revenue."
"Everyone wanted to know what the official pattern was, so they could have confidence that they were using the right one."
"The process was do what you want, I’m cool with that. Nobody really cared what others did, which created silos of indifference."
"We gave cash prizes for the best overall design pattern, most research, or most timely contributions to keep people engaged."
"It’s normal for people to say you failed, sometimes even in meetings you’re not in, but you shouldn’t let that stop you."
"72% of people surveyed had never used the design system before, showing a gap in understanding despite having skilled teams."
"People didn’t want explanations about how to use patterns; they felt designs were self-evident and wanted just examples."
"We stopped talking about patterns and consistency as it made me the ‘patterns guy’—instead, I shifted language to what different roles cared about."
"Once you have momentum, you need to enable others to broadcast your wins, or your efforts just become ‘one of the other things people have stopped caring about.’"
Or choose a question:
More Videos
"The risk of AI is that it will over-rely on past priorities and miss new, emerging signals."
Mark Interrante Harry MaxAI for Prioritization (3rd of 3 seminars)
July 11, 2024
"Building product today is getting more and more complex, and organizations desperately need professionals who speak compliance and product."
Patrizia BertiniThe (r)evolution of designOps: It’s Time to Think (really) BIG
September 11, 2025
"We prioritize to code switch to clarify value and relevance using language as a tool for meaningful activities."
Shan ShenTranslating UX Terms into Business Contexts
November 29, 2023
"60 to 90% of our ideas do not improve the metrics they were intended to improve."
Adam ThomasSurvival Metrics – Making Change in a Fast, Data-Informed, and Politically Safe Way
December 6, 2022
"Experiential significance is that moment in research when something just hits you as really important and impossible to ignore."
Robin BeersResearch as a Catalyst for Organizational Transformation
March 12, 2021
"Accessibility defects are bugs. If it’s a P1 blocking bug for an accessibility issue, treat it like any other P1 bug."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"To me, sweating the pixel means paying attention to the details of interactions and keeping our eye on quality as designers."
Joseph MeersmanSweating the Pixel: Scaling Quality through Critique
June 10, 2021
"Your strengths, even if perceived as weaknesses, can be your superpower."
Deanna Washington Bria Alexander Jon Fukuda Saara Kamppari-Miller Farid SabitovConnecting the Ops: Plenary Panel and Closing Circle
September 9, 2022
"Iterative engagement models mean we test, learn, and adapt rather than seeking a perfect solution from the start."
Aaron Stienstra Lashanda HodgeLeveraging Civic Design to Advance Equity and Rebuild Trust in the US Federal Government
December 8, 2021
