Summary
In this talk, Phil and Nathan engage in a deep discussion about transforming corporate culture through design thinking and relationship-driven work, particularly within IBM. Phil shares his ongoing journey since 2010 in scaling design practices across a vast, distributed organization, emphasizing organic team-level adoption and executive support for designers. Nathan highlights the centrality of relationships and shared meaning in driving value, asserting that culture and innovation emerge from deliberate, sustained conversations and experiences rather than mere persuasion. Both speakers underscore the importance of listening deeply to individuals across silos and acknowledging the complex risk environment of organizations. The discussion reveals how design must not only speak the language of business but innovate it, balancing youthful openness with experience, and how successful change initiatives require finding allies, framing wins in business terms, and piloting safely to gradually shift mindsets. Practical tactics include ethnography on internal stakeholders, framing successes to evidence new possibilities, and reframing risk to enable experimentation. The speakers reflect on historical shifts that emphasized numbers over relationships and articulate a hopeful, adaptive approach to embedding design as a cultural craft in traditionally rigid business settings.
Key Insights
-
•
Design transformation in large companies like IBM succeeds when designers are embedded within business teams rather than centralized in studios.
-
•
Changing organizational culture is more effective through experiential learning and behavior change than through mere persuasion or theory.
-
•
Relationships are fundamental to innovation and culture, yet difficult to visualize and quantify within organizations.
-
•
Listening deeply and non-judgmentally to individuals at all levels enables building empathy and meaningful connections that foster change.
-
•
Risk-taking is essential for innovation, but organizations must balance it with risk management through dialogue and safe-to-fail experiments.
-
•
Embedding design at scale requires executive support with direct communication channels while enabling organic growth from the team level.
-
•
Meaning and identity in design add value especially when buyers and users differ, requiring research on both to align priorities.
-
•
Youthful openness to learning can be more valuable than years of experience when adopting new cultural approaches to design.
-
•
Framing design efforts in terms of existing business goals and language helps secure allies and advance cultural change.
-
•
Top-down mandates alone often fail to create lasting change; combining grassroots adoption with leadership support is more effective.
Notable Quotes
"It’s really about design doing, not just knowing the theory but acting and behaving differently."
"Without relationship, there is no value. You can’t have culture without relationships either."
"Every team that’s come into the program has self-selected in. They want in and are trying to do the right thing."
"A leader is someone who clearly communicates a vision that other people want to follow."
"The conversation about risk needs to shift to what’s the acceptable amount compared to the value of the opportunity."
"Listening deeply with no judgment allows you to start making profound invitations across silos."
"Most people don’t come to work to make their own life harder or work on a bad product."
"We rejected a studio model because designers should take business direction from the teams they’re embedded in."
"We’re building a program here that lasts through 2025 and 2030, so we can take risks on entry level folks."
"You have to speak the language of business and innovate that language to show what design can do together."
Or choose a question:
More Videos
"I call it proactive research ops because often teams only think about ops when something breaks, but we started early before there was drama."
Saskia LiebenbergStart Small for Big Impact
May 15, 2019
"We got to get everybody to tell stories in the whole room."
Dan WillisEnterprise Storytelling Sessions
June 8, 2017
"There has to be some connection between our results and how our partners see the value in it."
Dr. Jamika D. Burge Jemma Ahmed Chris GeisonBridge Building across Research Disciplines
August 26, 2021
"Don’t dress for the job you have, dress for the job you want—this applies to people and companies alike."
Mark TempletonCreating a Legacy: the ultimate experience
June 9, 2017
"Every culture has things to celebrate and improve upon; we should learn from others instead of imposing our own standards."
Tricia WangSCALE: Discussion
June 15, 2018
"Language is hard, and we use anthropomorphic words like reasoning and thinking to describe what the model does technically."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 3: Understand AI architectures: RAG, Agents, Oh My!
July 30, 2025
"Some of the most impactful insights come from data analytics and user research collaborating to find behaviors seen in real people and aggregate data."
Eduardo Ortiz Robin Beers Rachael Dietkus, LCSW Bruce Gillespie Jess Greco Marieke McCloskey Renee ReidDay 3 Theme Panel
March 13, 2025
"We need to create evolving system loops that incorporate feedback and allow our units of one to learn and adapt."
Dave Malouf Adrienne Allnutt Jon Fukuda Dominique WardThe Future of DesignOps
January 8, 2024
"We ended up doing an average of five labs per quarter covering 12 to 15 research questions, which helped avoid design delays."
Feleesha SterlingBuilding a Rapid Research Program
May 18, 2023
Latest Books All books
Dig deeper with the Rosenbot
What types of UX and product design content are included in the Rosenverse platform?
What does Steve Krug mean when he says AI in UX is like power steering rather than self-driving cars?
How does Rally’s research infrastructure facilitate participant management and integration with enterprise data systems?