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
"I am usually the only designer on the team, and it gets difficult to get the information needed for design decisions."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"Google Maps’ Leaf visualization helps people normalize efficient driving, demonstrating the power of design in behavior change."
Jamie Beck Alexander Nina Gregg Shawn Petersen Bill DeRoucheyHow can you find your role in climate?
January 17, 2024
"We had to push through analysis paralysis and trust our guts as customer-facing teams that knew the business."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"ChatGPT did not have the full context of what was most important to stakeholders, so I had to edit its output before sharing."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Invite support people to scrums or monthly engineering reviews so design can get visibility into common customer issues."
Toby HaugDiscussion
June 9, 2017
"Learning is a marathon, not a sprint, especially in the context of online conferences."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"You can't lay off the infrastructure, like the tooling and operations teams; they're harder to cut."
Louis RosenfeldCoffee with Lou
January 11, 2024
"I don’t know what I don’t know – new practitioners may not even realize what questions to ask at first."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"Manage the toolkit as a project—have a backlog, prioritize changes, and dedicate sprints to keep it updated."
Michele WongHelping Them Help Us
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
Why is interoperability and API access critical in modern user research tooling ecosystems?
What strategies help speed up the procurement and legal review of UX research platforms in organizations like LinkedIn?
In what ways does the Rosenbot promote self-directed, on-demand learning for UX professionals?