Discussion
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
"We ramped up from six-month release cycles to releasing every two weeks to keep ahead and still deliver experiences that wow."
George Hinchliffe Joy LiuDelivering Amazing Experiences
June 10, 2021
"Sketch’s open file format allowed us to build custom tooling that shapes the design data to our needs."
Luca RagerEmpowering Gaming at Scale: How Xbox Builds Powerful, Automated, and Distributed Design Systems with Sketch
September 30, 2021
"Make a proof of concept before investing a lot more time and energy into a design system."
Dave Malouf Amy ThibodeauPanel: Design Systems and Documentation
November 7, 2017
"Maintaining large-scale design systems is a real challenge that AI tools are starting to solve."
Ryan Matthew Alex KurchevBridging Design and Code: AI-Powered Design System Integration
September 11, 2025
"A frustrated passenger at a delayed flight might just need acknowledgment, not dismissal."
Indi YoungThinking styles: Mend hidden cracks in your market
January 8, 2025
"There’s still folks who are entering saying I’m a team of one, no one knows what I do."
Bud Caddell Kristin Skinner Alana WashingtonDesignOps Community Sensing Session
May 13, 2021
"Designers often resist processes meant to streamline their work because it feels restrictive."
Kristin Skinner Kamdyn Moore8 Types of Measures in Design Operations
April 16, 2020
"Critical thinking is our strongest asset, not just automation or AI."
Ben Reason Aline Horta Majid Iqbal Fabiano LeoniMaking the system visible: The fastest path to better decisions
November 20, 2025
"If you use AI tools, ask for five different ways to do something, not just one, to force exploration."
Dan Mall“Ask Me Anything” with Dan Mall, Author of Upcoming Rosenfeld Title, Design that Scales
October 2, 2023
