Summary
Phil and Nathan share experiences and strategies for embedding design thinking in large, complex organizations. Phil recounts his journey at IBM since 2010, leading a distributed design program that empowers designers within business units rather than centralizing them. He explains how the program grew organically starting in 2012 and is built to last decades, prioritizing a safe executive channel paired with grassroots adoption. Nathan focuses on the importance of relationship as a foundation for value in organizations and design culture. He explains that culture is formed through relationships and deliberate conversations, and that knowing oneself and others is key. Both speakers emphasize shifting organizational conversations from persuasion to experience-based change, with Nathan advocating doing ethnographic research within organizations to align language and interests. They address challenges of risk-taking in innovation, navigating organizational resistance, and how design thinking can help run the change program itself. Practical tactics also involve listening deeply without judgment, co-creation across silos, and reframing risk as hypothesis testing. Phil and Nathan discuss hiring strategies balancing youthful openness and experience, and how design must speak the language of business to gain traction. The overall message is about maturing design into an organizational force by building authentic relationships, listening, and creating room for experimentation within business constraints.
Key Insights
-
•
Culture change is more effective through experiential learning and doing design rather than merely persuading through theory.
-
•
Phil’s IBM design program avoids a centralized studio model; designers are embedded in business units with matrix reporting to maintain influence and autonomy.
-
•
Strong relationships are foundational for culture and value creation but are difficult to represent and discuss explicitly in organizations.
-
•
Design programs succeed when they have both grassroots team-level adoption and an executive-level safe outlet for reporting dysfunction.
-
•
Risk-taking is essential for innovation, but organizations must balance acceptable risk with mitigation, often requiring collaborative conversations between design, legal, and finance.
-
•
Listening deeply to individuals across silos without judgment builds trust and opens opportunities for meaningful collaboration and co-creation.
-
•
Meaning, emotion, and identity often matter more than features or price, especially when buyers differ from end users in B2B contexts.
-
•
Hiring mixes entry-level and experienced designers to balance openness to learning with practical knowledge, avoiding both close-mindedness and overly rigid mindsets.
-
•
Organizational change efforts often fail by becoming check-box processes; finding early wins and allies helps make programs credible and scalable.
-
•
Designers need to adapt their language to align with business goals, effectively 'speaking the language' of leaders to gain influence.
Notable Quotes
"It’s about design doing, not just talking about design theory."
"Without relationship there is no value. You can’t have culture without relationships either."
"Every one of those hundred teams self-selected in. They want in and they’re trying to do the right thing."
"A leader is someone who clearly communicates a vision that other people want to follow."
"Find some allies and get some wins to prove that change can take root in your company."
"Most people come to work not to make their life harder or to build crappy products."
"We rejected a studio model because designers need to be part of business teams taking direction from them."
"Listening deeply without judgment is maturing design research into active leadership."
"Risk conversations are less about risk or no risk and more about acceptable risk balanced against opportunity value."
"The program is built to last until 2025 and 2030, not just to deliver short-term outcomes."
Or choose a question:
More Videos
"Spreadsheets for profiling people across an organization can take an awful long time to create and update."
Shaping design, designers and teams
November 8, 2018
"A hackathon with designers, developers, business and architects can accelerate UI coded component delivery."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
"We need to stop treating digital and physical services as separate—they’re one holistic experience."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"If you start now with small tweaks and passion, you will gain ground and rally people behind you quickly."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility (Videoconference)
May 26, 2022
"Dana and Davis weren’t seen on stage at Adobe Max, but you felt their impact throughout the experience."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"The 1500 are designers, we don't distinguish strictly between UX or visual or industrial—they all bring design to the org."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Surprising to me, PMs benefited from the platform and were able to work faster in their own lifecycles."
Operationalizing DesignOps
November 7, 2018
"Journey maps and personas often disappear into the void because they’re too dense for business folks to consume."
Leah Buley Joe NatoliAsk Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)
October 8, 2024
"You need to learn the vocabulary, tools, and processes your peers know and understand where they are inadequate."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020