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
"If you’re rewarding designers for delivering on time, great, but if you reward them for delivering accessible products on time, you’ll get better results."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"Observation reveals needs users themselves haven’t recognized yet."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"Companies had to relearn their customers during COVID because behavior had fundamentally changed."
Janelle EstesUX Research Trends
January 28, 2021
"Start with content first wireframing and avoid lorem ipsum to prevent treating words like decoration."
Craig Brookes Andreas Huebner Morgan Quinn"Just Make it Look Good" and Other Ways We're Misunderstood
June 11, 2021
"Slow and intentional communication allows you to be fully present rather than distracted by constant notifications."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Research ops is heavily reliant on clear and consistent research leadership to define strategy and priorities."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"If I make a mistake on our team, it’s not gonna be held against me; my team won’t disconnect from me."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"We treat our shared tooling and design system as a product with a dedicated team maintaining reusable components and governance."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"You need to build credibility. It's not enough to just state a problem, you have to show you'll do the work and push for it."
Tricia WangSCALE: Discussion
June 15, 2018
Latest Books All books
Dig deeper with the Rosenbot
What impact does AI have on the speed and demand for user research according to Basil Faqiri?
How do research operations teams manage the tension between consolidating tools and needing specialized capabilities?
How can a product vision avoid becoming just a pretty prototype with no strategic impact?