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
"We moved from Evernote to spreadsheets, to a giant affinity board in Mirror, then to UserVoice, and finally to idiomatic software with AI."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"We often use radio buttons when check boxes or sliders would reveal the truth."
Peter MorvilleThe Architecture of Understanding
May 13, 2015
"If you make a pretty page, that’s great. But if the users can’t actually use the page or they’re frustrated, you just have a pretty page."
Renee ReidBecoming a ResearchH.E.R (Highly Enterprise Ready)
June 3, 2019
"The environment can disrupt critical interactions, like when Stacey gets caught up in cords and takes her eyes off the patient."
Dane DeSutterKeeping the Body in Mind: What Gestures and Embodied Actions Tell You That Users May Not
March 26, 2024
"Avoid strictly timed interactions because they stress everyone, especially people using screen readers or with cognitive disabilities."
Sam ProulxOnline Shopping: Designing an Accessible Experience
October 3, 2023
"Younger visitors are nearly twice as likely to engage with digital chat or help but are less satisfied afterward."
Andrew Custage Michael MallettThe Digital Journey: Research on Consumer Frustration and Loyalty
March 29, 2023
"You can’t have a hackathon without free food."
Shelby SwitzerMaking Space for Community Knowledge-sharing in a Distributed World
December 10, 2021
"Right now, there’s a fear of being replaced by AI, and while a lot of that’s overblown, researchers have a legitimate reason to feel uncomfortable."
Llewyn PaineCoexisting with AI: A practical guide for researchers to navigate tools, ethics, and integration
March 11, 2025
"A metaphor is like a flashlight—it shines on some things and keeps others in the dark."
Robin BeersNavigating organizational systems: Rethinking researcher’s role in driving change
March 13, 2025
Latest Books All books
Dig deeper with the Rosenbot
What steps help build trust and healing in communities affected by historical traumas during engagement?
Why is assessing design students challenging, and what are the limitations of traditional grading systems?
How should designers prepare for AI-driven cognitive agents that understand emotional personas?