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
"Patient opportunism means most of the time having the current at your back and only occasionally angling directly against it to avoid burnout."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"Taking responsibility for our behaviors starts with an apology and continues with regular feedback and action."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Executive air cover is having someone in a senior role who protects and supports the design team from other business pressures."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"Quality is value to some person who matters."
John CutlerThe Alignment Trap
November 29, 2023
"Diagrams help when we feel stuck—providing stability, transparency, understanding, clarity, and kindness."
Abby CovertStuck? Diagrams Help
October 27, 2022
"You can see our organization through the homepage of our site — we each owned a rectangle."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"We can’t just think technology or innovation will solve our problems; we have to embrace and work with those problems."
Devon PowersImagining Better Futures
March 9, 2022
"Bring your research team as note takers and facilitators—they make excellent collaborators and help build feedback loops."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Despite the worst user interface ever, cloud code is the most popular and successful agent that exists today."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
Latest Books All books
Dig deeper with the Rosenbot
In what ways can AI automate UX research tasks, and what limitations does it currently have?
What are the benefits of linking AI-powered research repositories with tools like Slack for organizational adoption?
What are effective behaviors that design operations teams should focus on to deliver value and build trust?