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
"Be honest with yourself: it won’t always be fun, it will be slow and full of blockers, but the impact is real."
Charlotte Vorbeck Shahzma Esmail Edward Alton Sarah McArthur Ariel KennanPipeline to Civic Design
December 9, 2021
"The way we build software now is fundamentally different; it's just easier to write code using platforms and microservices."
Greg PetroffEverything is About to Change: Software as Material
June 8, 2016
"There is a large and growing capability overhang in these models we haven’t discovered yet."
Peter Van DijckHands-on AI #1: Let’s write your first AI eval
October 8, 2025
"We want it to take two weeks instead of two years for a skilled operator to pilot these new vehicles."
Teresa SwinglerLook, Up in the Sky! UX/UI for Aerospace
October 27, 2022
"Every single thing that we would plan to say to the participant is spelled out in this interview guide to build transparency and trust."
Lisa Spitz Nikki BrandBuilding Trust Through Equitable Research Practices
November 18, 2022
"Designing for the real world means dealing with practical constraints and making refinements in the face of compromise."
Craig VillamorResilient Enterprise Design
June 8, 2017
"Everyone had encyclopedic knowledge of their product and they didn’t exploit that knowledge gap."
Nova Wehman-BrownWe've Never Done This Before
June 4, 2019
"You could never do all this marketing alone—it’s all hands on deck, relying on different strengths and creativity across the team."
Molly FargotsteinMultipurpose Communication & UX Research Marketing
September 12, 2019
"Design ops is the heart, the connective tissue of our design organizations."
Alana WashingtonTheme 1: Introduction and Provocation
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
What is the purpose of Leadership Dichotomies and how can leaders use it for self-awareness?
How can metrics like the Accessible Usability Scale be used post-launch to improve accessibility?
How can co-created custom investment models change decision-making processes in government development agencies?