Summary
Catherine Courage opens the Enterprise Experience Conference by recounting her personal and professional journey at Citrix, where she was hired to build a design and experience team from scratch at a 20-year-old engineering-driven company. With CEO Mark Templeton’s strong support, she navigated four phases: chaos, reaction and influence, organization and impact, and refinement and differentiation. Catherine highlights the challenge of shifting company culture from feature-focused to experience-focused, the importance of building trust and credibility, and engaging middle management through programs like Stanford D School. She discusses strategic hiring, quick wins like unifying product design language after years of acquisitions, and evolving the team's organizational structure as it grew from 1 to nearly 350 people. Catherine also stresses the need for empathy by bringing engineers and product managers into the field, the power of storytelling, the role of dedicated collaborative spaces, and the importance of saying no to prevent burnout. Later, she describes expanding from product experience to end-to-end customer experience, creating a business design team, and eventually reporting directly to the CEO to influence company strategy. Catherine shares insights on measuring experience through NPS and product instrumentation, developing business acumen in designers, and maintaining ongoing communication and community engagement. The talk concludes with Q&A addressing differentiation of customer vs user experience, strategies to understand business, the tipping point of maturity, measurement techniques, and organizational challenges working with IT and web development teams.
Key Insights
-
•
Enterprise experience demand is driven by consumerization where employees expect workplace software to match consumer-grade products.
-
•
CEO Mark Templeton’s active support was crucial to embedding experience design at Citrix.
-
•
Building trust and credibility within an engineering-driven culture is more critical than just hiring a design team.
-
•
Using simple, relatable design principles (like simplicity, craftsmanship, delight, innovation, and user focus) helps align the organization.
-
•
Quick wins, such as unifying disparate product styles post-acquisition, create visible impact and build momentum.
-
•
Encouraging engineers and product managers to engage in field visits fosters empathy and customer-centric thinking.
-
•
Targeting middle management through credible executive programs (e.g., Stanford D School) can transform resistance into advocacy.
-
•
Configurable, always-available collaborative workspaces boost real-time teamwork and innovation.
-
•
Saying no strategically protects team capacity, prevents burnout, and supports sustainable growth from 1 to 350 team members.
-
•
Expanding beyond product to entire customer experience ecosystem enables reporting directly to executive leadership and driving broader business impact.
Notable Quotes
"If we don’t get good experiences in the workplace software, people will beat the system and get their own products."
"This is not just building a design team; this is about culture change and changing how the organization thinks about design."
"More features and delivering on time used to equal better products; now it’s about what those features add up to in experience."
"People really appreciate when you just ask them for their opinion and perspective before jumping in."
"Hiring is a two-way street; we have to explain why they want to come join Citrix, like a startup with big company security."
"Middle managers don’t like change and are risk averse; taking them to Stanford D School boot camps turned them into our biggest advocates."
"Collaboration isn’t scheduled; it’s about having spaces that are unbookable and always available for teams to brainstorm."
"Saying no with purpose and rationale is key to not spreading the team too thin and maintaining quality."
"You need to develop designers’ understanding of business language to prepare them for seats at the executive table."
"Customer experience is the whole journey; user experience is a part within that journey involving different types of users."
Or choose a question:
More Videos
"You need well-defined frameworks and guardrails for experimentation success to prevent chaos across teams."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"Designers are rebels; to get their buy-in, involve them and treat them as precious collaborators."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"You have to treat the design system as a product that delivers features and releases over increments, never really done."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"The word ‘key’ is an extra super duper important differentiator — among all priorities, these are the keys."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"It’s really hard to make changes to these systems because it’s risk-ridden and a major undertaking."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"We use a magic R studio button that, with one click, processes all the survey data automatically."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"Even virtually, we are a community obligated to treat each other with kindness and respect."
Bria AlexanderOpening Remarks
June 9, 2021
"Lean governance tries to find the sweet spot between chaos and command and control."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"Electric car targets for the UK alone would demand more than the world's annual cobalt production."
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024