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
"Findings from marginalized groups aren’t just relevant to them but often improve the experience for many more people."
Kaitlin TaskerFast and Fearless Inclusive Research
March 27, 2023
"Sometimes you have to take a chance and hire someone because they have the ability to grow into the role."
Jackie Velasquez-RossTalent Acquisition and Our Responsibility
June 16, 2020
"The assistant asks open-ended questions that focus on what truly matters: performance, budget, and preferences."
Kritika YadavOptimizing AI Conversations: A Case Study on Personalized Shopping Assistance Frameworks
June 10, 2025
"Your work is not your identity. You are gonna hear no, and that’s okay."
Lori Muszynski Peter MerholzKeeping Design Weird
October 2, 2023
"We seldom question whose table we want a seat at or why we don’t rebuild the entire table altogether."
Megan Blocker Lada Gorlenko Fatimah Richmond Molly StevensWhat UX research maturity looks like and how we get there [Advancing Research Community Workshop Series]
November 9, 2023
"The most significant source of confusion is the difference between research questions and interview questions - Erica Hall."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"Knowledge multiplies the more it is shared; enabling others makes your insights stronger, not your position weaker."
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
"Product managers learn to attach at the end of every sentence something about money — no money, no attention."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"Design thinking has helped raise awareness but often lacks the depth of design practice which requires dedicated craft."
Jorge ArangoDesign as an Antidote to VUCA
May 9, 2019
Latest Books All books
Dig deeper with the Rosenbot
How can teams integrate inclusive design into early product development stages to avoid costly late fixes?
How can AI enable product managers and designers to participate more effectively in research and prototyping?
How can program or project managers support design ops activities when no dedicated ops role exists?