Summary
In her keynote at the Enterprise Experience Conference, Catherine Courage detailed her personal journey at Citrix, where she began as a solo design leader in a 20-year-old, engineering-driven company with little design focus. Backed by CEO Mark Templeton, she built a team that grew to nearly 350 people by driving culture change, shifting the company's mindset from feature-centric engineering to customer-centric experience. Catherine structured the transformation into four phases: chaos, reaction and influence, organization and impact, and refinement and differentiation. She highlighted the importance of building trust and credibility, tackling middle management resistance (with programs like Stanford’s D School boot camp), and fostering collaboration between product management, engineering, and experience teams. Strategic hiring with culture fit, securing executive support, quick wins like unifying product design languages, and creating collaborative workspaces were key tactics in early phases. As the team matured, learning to say no with rationale prevented burnout and bottlenecks. Catherine expanded the focus beyond products to include the full customer journey, gaining a seat at the executive table and integrating functions like brand and web development. She stressed ongoing communication, community engagement, and developing business knowledge among designers to sustain influence. Catherine also addressed measurement challenges, recommending pilot programs for NPS and usage data. Her story offers practical advice on scaling enterprise UX teams and embedding customer experience into corporate strategy.
Key Insights
-
•
CEO support, specifically from Mark Templeton, was pivotal in legitimizing the design transformation at Citrix.
-
•
Building trust and credibility across engineering and product management was more critical than immediate design overhauls.
-
•
Enterprise companies often mistake more features and faster delivery for better products, ignoring true user experience.
-
•
A simple, shared design language with five principles helped make experience relatable and accessible internally.
-
•
Middle management is a major obstacle to change; sending them to Stanford D School boot camps converted many skeptics into advocates.
-
•
Creating open, configurable, and unbookable collaboration spaces dramatically improved team creativity and engagement.
-
•
Saying no strategically, with clear rationale, is essential to avoid team burnout and maintain quality as design teams scale.
-
•
Expanding focus from product design to end-to-end customer experience (including support and sales) is critical for large enterprises.
-
•
Designers need business acumen and language to influence at the executive level and secure a seat at the table.
-
•
Measurement of experience impact requires culturally relevant KPIs; pilot testing is better than rolling out one metric broadly.
Notable Quotes
"If we don’t get good experiences in the workplace, we’re going to beat the system and go get products that actually help us do our jobs."
"More features and functions do not equal a better product."
"This job is about culture change, not just building a design team."
"Building trust and credibility was more important than immediately overhauling products."
"Middle management likes things the way they are and are very risk averse, which can be a big obstacle."
"Having unbookable, configurable spaces for real-time collaboration is crucial for creativity."
"Saying no with purpose and rationale helped us scale from nine people to over 150 without burning out the team."
"You can’t just focus on product experience; you need to look at the whole customer ecosystem from the first touchpoint."
"Designers must develop business understanding to keep a seat at the executive table."
"Measurement is hard; pick culturally resonant metrics and pilot them before scaling broadly."
Or choose a question:
More Videos
"I’ve been using screen readers for 30 years and accessibility has always been a passion of mine."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"In government, the org chart really matters – it influences who talks to whom and who gets to interface."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Our one metric that mattered was maximizing the number of VOС-tagged tickets solved – showing customer feedback made it to the roadmap."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Why don’t we do what we do for users but apply it to our own careers? Absolutely nutty, right? So we did."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The trusted partnership between the chief of staff and the executive is critically important."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Async communications helped us reduce emails and meetings, improving overall efficiency."
Amy EvansHow to Create Change
September 25, 2024
"Telepathy as mind reading means proactively building a talent pipeline and improving recruitment processes."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"The enterprise feels like a big elephant; different people touch different parts and argue what it really is."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"Standalone insights destroy the researcher’s ability to storytelling and engagement."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
