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
"There’s never enough attention you can give to change management in scaling design impact — don’t do it alone."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"The only people who can effectively map a space are those who work and understand that space intimately."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Many smartwatch designs assume male hands as default, excluding smaller wrists and diverse body types."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"Appealing to stakeholders’ best interests helps build trust and rapport."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"ChatGPT didn’t have the full context of what was most important to stakeholders, so I had to edit its output before sharing."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"The seven-foot-wide diagram showed the product’s true complexity, sparking necessary conversations with leadership."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Relying on a single content strategist was a strategic mistake that created a single point of failure."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"We stopped talking about patterns and consistency and started talking about scalability and speed to connect with stakeholders."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"The operational glue that binds strategy, execution, and measurement in design is often missing, and that’s critical for scaling."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
