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
"Academic Purists believe one size fits all, ignoring context and stifling innovation."
Jason Mesut Martina Hodges-Schell Jose CoronadoUnmasking Design Leadership: Navigating leadership without neglecting ourselves
October 30, 2025
"We don’t have meetings without all three sides of the business, product, and design coming together now."
Uday Gajendar Lada Gorlenko Dave Malouf Louis Rosenfeld Dan Willis10 Years of Enterprise UX: Reflecting on the community and the practice
June 18, 2025
"I had to learn to speak contractor — shorter, simpler, in-viewport text without scrolling."
Sara ConklinExit Interview: 20 Years of Tech, One Very Big Bet, and a Lot of Heat Pumps
April 10, 2026
"Discovery deficit happens when you don’t know what or how to do things in an AI system, often because of lacking affordances."
Josh Clark Veronika KindredSentient Design: New Design Patterns for New Experiences (3rd of 3 seminars)
February 12, 2025
"It’s less about processes and more about the business value of design."
Patrizia Bertini Alexandra Mengoni LeónPushing DesignOps’ Influence into New Global Markets
September 9, 2022
"There’s a lot of work to do aligning design systems so designers, engineers, and business analysts speak the same language."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"The hidden hero or villain of craft is really feedback, the quality of feedback that we give."
Vanessa VarinFeedback: The Other F-Word
September 10, 2025
"A typical enterprise customer has like five analysts who need a login, not millions of users."
Dan WillisEnterprise Storytelling Sessions
May 13, 2015
"Langauge is what shapes us, and extracting keywords helps us create narratives to understand how people think."
Andrea GallagherThe Problem Space
May 16, 2019
