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
"Standardization lives deep in my heart partially because of the teams that I’ve worked on and also because I’ve just had so many domains under the umbrellas of my teams over time."
Candace MyersStandardizing Design at Scale
September 9, 2022
"Design Ops is going to have to deal with Product Ops, and figuring out that relationship will be a big deal."
Dave Malouf Meredith Black Farid SabitovThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 1)
February 17, 2022
"Every group has their own vocabulary that signals belonging, but jargon can become a barrier to understanding."
Joshua GravesWe Need To Talk: Managing Ludicrous Requests at Work (Part 3 of 3)
May 12, 2025
"Truly listening can push us beyond empathy to respect and reflection."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"Evaluation might be the most important part of your entire development effort and is often the hardest to do well."
Sarah BarrettAI in Real Life: Using LLMs to Turbocharge Microsoft Learn
February 13, 2025
"People saw small changes as having very large impact; a half-percent increase in conversion could mean 12 million dollars in revenue."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Nudge to me now is much more about wiggle it and see what happens rather than expecting exact outcomes."
Jen BriselliLearning Is The Engine: Designing & Adapting in a World We Can’t Predict
April 16, 2025
"Design ops served as the backbone to operationalizing the organization, enabling scale, repeatability, and stakeholder confidence."
Jenny PriceFrom Tradition to Transformation: Unlocking Startup Agility in a Legacy Enterprise
September 10, 2025
"Starting small with relationship-building is key when safety is lacking, especially in large or hierarchical groups."
Alla WeinbergHow to Build and Scale Team Safety
January 8, 2024
