The Enterprise UX Journey: Lessons From the Voyage & The Opportunity Ahead
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
"In Western modernity, if something is not an object, it is not real research or real knowledge."
Victor UdoewaBeyond Methods and Diversity: The Roots of Inclusion
March 26, 2024
"When we understand organizations as ecosystems, we recognize the need for organic simplicity."
Peter MorvilleThe Architecture of Understanding
May 13, 2015
"You have to be careful not to be too weird; mental models differ internationally."
Sam LadnerHow Research Can Drive Strategic Foresight
March 9, 2022
"Over a third of the company signed in shortly after launch, which felt like a great success."
Michelle Bejian Lotia Anne-Marie MorellRolling Out a Repository: How Zapier Centralizes Insights from Across their Organization
March 28, 2023
"My kids know everything. If you listen to conversations with them, they say I know, Ma, I know."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"If we’re really centering it on people and experiences, consider life before place, and place before technology."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"You enter a single prompt, like washing your own car, and the system analyzes the whole context and returns research artifacts."
Joerg Beringer Thomas GeisScaling User Research with AI: Continuous Discovery of User Needs in Minutes
September 10, 2025
"Designers embedded in teams often feel lonely and their work leads to fractured user experiences."
Peter MerholzCustomer-Centered Design Organizations
June 8, 2017
"The single most important thing we can do at the table is expanding the boundaries of knowledge for decision makers."
Dalia El-ShimySo You've Got a Seat at the Table. Now What?
March 31, 2020
