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
"Knowledge is not only intended for human consumption, it is meant for human action."
Ren PopeBuilding Experiences for Knowledge Systems
June 6, 2023
"The internal dialects developed by project teams require intentional translation into a formal, limited lattice framework for portfolio analysis."
Sean Baker Sara RomanoskiWeaving Knowledge Management into the Fabric of Our Design Practice
September 11, 2025
"Democratization of research is not just about scaling capacity but about fostering collaboration."
Jane DavisStrategic Shifts and Innovations in User Research: Navigating Challenges and Opportunities
March 11, 2025
"Many customers struggle to get anyone to listen to actual insights because of the volume and complexity of raw video data."
Andy Barraclough Betsy NelsonFrom Costly Complexity to Efficient Insights: Why UX Teams Are Switching To Voxpopme
September 23, 2024
"Everyone contributes to conflict; it’s not about right or wrong, but what each person is trying to protect."
Laura WeissTurn Down the Heat: 3 Ways to Handle Conflict in the Moment
November 20, 2024
"The moment you spend more on maintaining legacy than creating the future, you’re probably doing the wrong thing."
Ted Booth Sam Ladner Fredrik Matheson Russ UngerDiscussion
June 8, 2016
"We’re typically designing products to solve really complex issues."
Kit UngerTheme 2: Introduction
June 10, 2021
"Previously, IBM designers were inventing their own buttons for every product, which exasperated chaos and inconsistency."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
"AI agents should understand the entire context and, if no suitable result exists, come back honestly without lying."
Maria Rosala Shivanjali M.Research Repositories
March 12, 2026
