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
"The yellow 80% allocation guide reminds that designers shouldn't be expected at full 100% project time due to meetings and breaks."
Kristin Sundermeyer Tygre MorehartDesign Ops Metrics
September 30, 2021
"Scaling up research impact means turning visibility way up and opening access despite some risk of misuse."
Jake BurghardtStop wasting research: Create new value with insight summaries
July 9, 2025
"Collaboration with another researcher was seamless because we speak the same methodology language and aligned on goals."
Joanna Vodopivec Prabhas PokharelOne Research Team for All - Influence Without Authority
March 9, 2022
"59% of roles were onsite focused in 2023, showing a shift back post-pandemic, but remote roles still exist with some location preferences."
Abbey SmalleyToday’s Design Ops and Programs Landscape & Career Paths
October 4, 2023
"Google’s photo algorithm mistakenly tagged Black people as gorillas, which was called out by Jackie Elsene."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"I don't want a component library for the account home. I want a system for all of that."
Nathan CurtisBeyond the Toolkit: Spreading a System Across People & Products
June 9, 2016
"Our role as DesignOps leaders is to focus on how work gets done, not on the specific design details."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"Depersonalizing the situation is a huge winner in nearly any hard conversation."
Joshua GravesWe Need To Talk: Navigating Conversations with Your Boss (Part 1 of 3)
April 14, 2025
"HIPAA isn’t that complicated; sending data to patients only needs two sentences."
Juhan SoninDesign Now! The Agenda for Action
September 4, 2025
Latest Books All books
Dig deeper with the Rosenbot
How does the culture clash between design's human-centered values and corporate bureaucracy manifest in organizational health?
What role does co-creation play in uncovering gaps and opportunities between collaborating organizations?
How can OKRs be used to measure outcomes instead of outputs in service design?