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
"Leaving tech meant rebuilding my social and professional networks outside the industry, which took time and courage."
Chelsey GlassonExit Interview #3: Same as It Ever Was: What Leaving Tech Taught Me About Change
December 17, 2025
"Start small and learn in low-stakes ways so you can train the organization to think, act, and react to AI."
Erika FlowersAI-Readiness: Preparing NASA for a Data-Driven, Agile Future
June 10, 2025
"Having each other's backs is like literal video game hero style slaying constraints."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"Tactical empathy is critical—it takes time and effort, but it’s always worth it."
Meredith Black Elyse HornbacherBuilding Community and Common Trends to Look for in 2021
December 17, 2020
"Sometimes vocal feedback reveals problems that digital behavior can’t see—like offline factors affecting perception."
Andrew Custage Michael MallettThe Digital Journey: Research on Consumer Frustration and Loyalty
March 29, 2023
"The boundary between design and development must open up; I ask if designers can make pull requests to code."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"If people already love their process, you’re fighting their emotional state — start where dissatisfaction exists."
Andrew WebsterScaling Design Capability: How Involved Should You Be?
September 30, 2021
"Demonstration projects produce focused learning that supports decision making for future directions."
Ed MullenDesigning the Unseen: Enabling Institutions to Build Public Trust
November 16, 2022
"If people are complaining about the present, it’s very difficult to imagine a future without addressing current challenges."
Robert Fabricant Sahibzada Mayed Nidhi Singh RathoreIndustry junctures: Paths forwards for UXR and the critical decisions that get us there [Advancing Research Community Workshop Series]
October 2, 2024
