Summary
In this talk, the speaker from IBM shares insights on cultivating a lasting design culture within a massive organization of 380,000 employees. Referencing collaborators like Phil, Doug, Charlie, and Susan, the talk stresses that culture is behavior over time, shaped by values, rituals, heroes, symbols, and practices. IBM’s design program grew rapidly, hiring over 750 designers through a rigorous process involving portfolio reviews, phone screens, and intensive in-person interviews led by a team including the speaker. New hires undergo a three-month onboarding to learn IBM design thinking and develop collaboration skills. IBM created flexible, people-centric studio spaces in Austin and elsewhere to promote productive teamwork beyond typical silos. The core IBM design practice revolves around IBM design thinking, emphasizing user outcomes, multidisciplinary teams, and a continuous loop of observe, reflect, and make. Influenced by conversations with David Kelley and Tim Brown, IBM adapted design thinking for scale, introducing tools like Hills, Playbacks, and Sponsor Users to maintain alignment and accessibility. The IBM design language balances unity and creative freedom across thousands of products, supported by embedded accessibility and bespoke design guides. The upcoming IBM design research initiative encourages all employees to participate in research roles. Above all, the speaker cautions that design efforts must drive real outcomes benefiting users. Throughout, the team embraces iterative learning and course-correcting as the design culture evolves.
Key Insights
-
•
Culture is defined as behavior over time, shaped by how people choose to behave and incentivize behavior.
-
•
IBM’s design hiring process is extremely selective, choosing less than 1% of applicants through multi-stage reviews.
-
•
A three-month onboarding program is essential to help new hires integrate and embrace IBM design thinking.
-
•
Design studios at IBM are built to be highly flexible, with furniture on wheels enabling constant reconfiguration.
-
•
IBM design thinking centers around user outcomes, multidisciplinary teams, and a continuous loop of observe, reflect, and make.
-
•
The Hills framework sets clear, outcome-focused goals to align teams and avoid internal conflict.
-
•
Playbacks provide a safe space for critique where hierarchy is set aside to focus on doing right by users.
-
•
Sponsor Users programs connect design teams directly to real clients for co-design and feedback.
-
•
The IBM design language promotes system unity but allows teams creative freedom, fostering cohesive yet diverse products.
-
•
Design research roles invite everyone in the organization to participate, expanding beyond traditional lab-bound models.
Notable Quotes
"Culture eats strategy for breakfast, but culture isn’t something you can just buy or transplant."
"Behavior over time is your culture; it’s how you choose to behave and incentivize others to behave."
"We review over 10,000 candidates and select less than 1% for hiring into the IBM design program."
"If you just throw new hires into cubeville, most of them would probably quit."
"We call everybody a designer on purpose to encourage branching out across disciplines."
"The studio is designed for whole teams to work together, not just the design team alone."
"Design thinking at IBM is not just for designers; it’s how we want all 380,000 people to think about problems."
"Playbacks are safe spaces where an intern can challenge a senior VP without hierarchy getting in the way."
"The IBM design language is about system unity instead of uniformity, so designers aren’t cookie cutters."
"None of this matters without outcomes; we design to make people’s days better, not just to design."
Or choose a question:
More Videos
"By understanding our systems and being intentional about tools and processes, everyone benefits."
Neema MahdaviOperationalizing DesignOps
November 7, 2018
"Leading the future of research isn’t about control, it’s about influence and impact."
Sean McKayCoexisting with non-researchers: Practical strategies for a democratized research future
March 11, 2025
"We help teams onboard their coded components onto the UXPin platform so they can be enabled with component-driven prototyping."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Climate change is not just a distant threat; it's happening here and now in our cities."
Lena ShenkarenkoCollaborative Wireframing for Creating Team Alignment and Shipping Better Products
October 21, 2020
"Traditional devops tools are more task and issue-centric, but designers think in processes and workflows."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"Trauma-informed is not a destination; it’s a journey, a continuous state of becoming."
Matt Bernius Sarah Fathallah Hera Hussain Jessica Zéroual-KaraTrauma-informed Research: A Panel Discussion
October 7, 2021
"Failure is easy, recovery is hard, but it’s necessary and part of the process."
Maria GiudiceEmpowering change: Reigniting purpose, passion and impact in research
March 13, 2025
"You want to let participants know it’s a bit non-typical and they are not being tricked or evaluated."
Marc Majers Tony TurnerInterrupted UX - Add A Dose of Reality To Usability Testing
March 11, 2022
"I don’t want to be included in your conversation. I want to co-create new conversation."
Jennifer Strickland Lesley-Ann NoelFireside Chat: How Design Addresses a World on Fire
March 18, 2022
