Culture Change—My Journey
Summary
Julie recounts her experience evolving the design culture at Citrix from a largely unknown, small team to an integral part of the company's customer experience and innovation processes. Starting in 2010, she navigated a distributed enterprise environment with limited design awareness. Collaborating with leaders like Catherine Tudor, Julie expanded design thinking beyond products into business functions such as HR, legal, and marketing. She describes bold visibility strategies like customer conference booths and creative pop-up design studios to build internal empathy and engagement. By partnering with cross-functional teams, including facilities and HR, her team introduced interactive, human-centered activities that influenced real projects like cafe remodels and onboarding programs. Julie emphasizes integrating quantitative metrics such as Net Promoter Score and time saved through improved compliance training led by Peter Conner to tangibly show design impact. She reflects on blending design thinking’s front-end creativity with Lean Startup’s hypothesis-driven iterations, stressing shared goals and language with engineering and product management. Her lessons stress making a splash to get noticed, educating broadly, embracing both qualitative and quantitative approaches, and embracing risk and trust in the design process.
Key Insights
-
•
Design was initially invisible at Citrix, with many employees unaware a design team even existed.
-
•
Participating in Stanford’s d.school inspired expanding design thinking beyond products into business areas like HR, legal, and marketing.
-
•
Creating a design booth at a major customer conference helped build internal and external awareness and empathy for customers.
-
•
Design thinking workshops and pop-up studios made design approachable and embedded it into the company culture.
-
•
Partnering with non-design teams like facilities and HR enabled human-centered design solutions for physical spaces and onboarding.
-
•
Redesigning compliance training with lawyer Peter Conner saved nearly 10,000 work hours annually, quantifying design’s business value.
-
•
Integrating Lean Startup methods complemented design thinking by enabling measurable testing and iteration post-ideation.
-
•
Net Promoter Score (NPS) became a key metric to demonstrate improvements in user satisfaction and loyalty.
-
•
Having engineering, product management, and design share unified goals fostered collaboration and collective accountability.
-
•
Trusting the fuzzy front-end of the design process is essential, even when outcomes are uncertain or workshops fail.
Notable Quotes
"When I first got to Citrix, people didn’t even know we had a design team."
"At Stanford’s d.school, we got the religion: design thinking could be bigger than just about products."
"Our customer conference booth was strategically located by the men’s room to catch traffic from hardcore enterprise IT folks."
"We reached about half of Citrix’s 10,000 employees worldwide through workshops and education."
"We created a pop-up design studio in the cafe to trade coffee and cupcakes for employee input."
"Peter Conner, our lawyer, redesigned compliance training so people took fewer courses but more relevant ones."
"We calculated nearly 10,000 hours saved in one year from redesigning compliance training, equating to three million dollars in opportunity cost."
"Design thinking works great in the front end when you don’t know what you want to do; Lean Startup helps when you have a direction."
"Net Promoter Score is just one question, but it’s a powerful way to measure loyalty and customer experience."
"We aligned engineering, product management, and design with the exact same goals so no one could succeed while another failed."
Or choose a question:
More Videos
"Design ops’ job is like jazz rules—it provides a framework so creativity can flow without worrying about inventing structure mid-process."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"We look to work with authors we like and enjoy being around because writing a book is a long, collaborative journey."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Keeping your craft sharp, learning new tools like auto layout in Figma, and challenging yourself help maintain relevance."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"If you’re a person who studies people, then you’re a person who understands data."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"Blurring user faces loses context and doesn’t address voice privacy, making it an inadequate solution."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"Qualitative reasoning about causal mechanisms usually comes from lived experience, either the researcher or participants."
Joshua NobleCasual Inference
October 6, 2023
"Findings are observations with a short shelf life, whereas insights get deep into the why and the consequences."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"We'll have a centralized Slack channel for all discussion to come together as one community."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"If you have to learn a workaround, you want to learn it once and reuse it again and again."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
