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
"Reflection after sessions increases ongoing collaboration design and continuous improvement."
Emilia Åström Jim KalbachUnlock Your Team’s Intelligence with Collaboration Design
June 9, 2022
"Design strategy focuses on providing a framework for developing design solutions that support a given product strategy, whereas product strategy addresses the business model, the roadmap, and prioritizing requirements - Frank Guo."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"I want Cisco to lead the industry in standardizing how energy measurement is done for products."
Amy ParnessScaling Sustainability: Complementary strategies that drive long-term success
May 29, 2025
"We adapt, we innovate, or we no longer exist."
Jemma AhmedResearch at an inflection point: Adapting to a new era of collaboration, equity, and innovation
March 11, 2025
"Happiness means different things across cultures: in the US it’s excitement, in Hong Kong it’s calmness, in Mexico it’s a process."
Verónica Urzúa Jorge MontielThe B-side of the Research Impact
March 12, 2021
"Why am I talking? Sometimes it’s better to ask a question and be silent."
Laura WeissThere is No Playbook: Leader as Coach During Challenging Times
April 26, 2024
"Explainability metrics like trustworthiness and understandability are hard, open research problems needing AI-HCI collaboration."
Joel BranchHumanizing AI: Filling the Gaps with Multi-faceted Research
March 11, 2021
"Doubt and fear come up if you haven’t established the right communication and trust."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"We run a two-week cycle now because translations back and forth require more time for quality."
Wyatt HaymanGlobal Research Panels
August 8, 2020
