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
"Creating experience principles helped democratize design decision-making across teams inside and outside the design group."
Sarah WilliamsA Framework for CX Transformation
June 11, 2021
"Proactive measurement before release combined with post-release evaluation is the ideal approach."
Jack MoffettUX Metrics That Matter and The Future of our Design at Scale Conference: A Community Conversation
September 22, 2022
"Use systems thinking to connect insights and show how research impacts organizational strategy holistically."
Megan Blocker Amy Bucher Katie Hansen Ricardo Martins Nidhi Singh RathoreDay 2 Theme Panel
March 12, 2025
"Who would you rather have conduct heart surgery? A part-time or full-time surgeon? That’s specialization."
Ari ZelmanowDark Side of Democratization
October 13, 2023
"Users have more than one mental model; they can be constructed on the fly depending on context."
Dane DeSutter Stephanie ScopelitisWhat co-speech gestures reveal about users’ thinking during interviews
June 30, 2023
"Design Ops teams exist in nearly all industries and for all design functions, growing rapidly year over year."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"You know you’ve succeeded as a coach when you put yourself out of a job by giving away the role."
Alissa BriggsHow to Coach Enterprise Experimentation
May 14, 2015
"The term full kit team was coined because you needed the full set of people to produce exceptional experiences."
Carla Casariego Sarah SpencerDesignOps in Wonderland
October 24, 2019
"It's commonplace for at least two browsers to be available because some critical web-based tools work on some browsers and not on others."
Sharon BautistaTime to Make the Donuts: How User Research Helped Bridge Disparate Teams
January 8, 2024
