People + Places + Practices = Outcomes
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
"AI can accelerate prioritization tasks, but the final judgment must come from humans who understand context."
Mark Interrante Harry MaxAI for Prioritization (3rd of 3 seminars)
July 11, 2024
"The accessibility expert was simply lost into shouting, we must be accessible without creating a strategy."
Patrizia BertiniThe (r)evolution of designOps: It’s Time to Think (really) BIG
September 11, 2025
"A tree test focuses on intuitive navigation while a prototype aims for the desired modality of an end solution."
Shan ShenTranslating UX Terms into Business Contexts
November 29, 2023
"If you’re not investing or quitting something, what is the point of having a strategy?"
Adam ThomasSurvival Metrics – Making Change in a Fast, Data-Informed, and Politically Safe Way
December 6, 2022
"We’re still operating from an industrial era hangover — a mechanistic way of problem solving that doesn’t fit today’s complexity."
Robin BeersResearch as a Catalyst for Organizational Transformation
March 12, 2021
"Assistive technology has to communicate with the destination, that’s your website or product."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"Designers are uniquely entitled to critique—it’s a privilege to rigorously improve craft while others might envy that process."
Joseph MeersmanSweating the Pixel: Scaling Quality through Critique
June 10, 2021
"Go meet someone new at this conference and set up a coffee chat next week."
Deanna Washington Bria Alexander Jon Fukuda Saara Kamppari-Miller Farid SabitovConnecting the Ops: Plenary Panel and Closing Circle
September 9, 2022
"We have the responsibility to redistribute our power and include those who have a stake in the work we do."
Aaron Stienstra Lashanda HodgeLeveraging Civic Design to Advance Equity and Rebuild Trust in the US Federal Government
December 8, 2021
