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
"First-do-no-harm actually goes farther than just not causing harm; it involves striving for the best possible outcome."
Mariah HayEthics in Tech Education: Designing to Provide Opportunity for All
June 14, 2018
"A great design solution for a poorly defined problem is infinitely worse than an average solution applied to a well-defined problem."
Billy CarlsonIdeation tips for Product Managers
December 6, 2022
"If you have any tech issues or need customer support, #deogenerall.help is here to assist you throughout the conference."
Bria AlexanderOpening Remarks
September 30, 2021
"No two teams are the same, and no two individuals are the same—every team has unique relationships and dynamics."
Séamus ByrneAligning Teams with Choreography
January 8, 2024
"Having 'service design' in your official job title does not give you an advantage in salary globally."
Marc FonteijnFirst Insights from the 2025 Service Design Salary(+) Report
December 4, 2024
"Dominic had tried to apply 12 times and kept running into PDF and terminology problems."
Marina MartinLives on the Line: The Stakes of UX at the Scale of Government
June 14, 2018
"Researchers and participants cannot tell the same story because they occupy different locations of power."
Bilan HashiThe Tension Between Story Collecting and Story Telling in Research
March 10, 2021
"We decided with the COP to view our budget as a moral document."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
"An agent is anything that displays agency, the ability to take actions and choose which actions to take."
Christopher NoesselAI of the now: Designing for Agents
July 31, 2024
