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
"Alternative navigation users pick different tools based on the task and how they feel at that moment, not just one technology."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"Design Ops in government requires a lot of diplomacy – it’s about managing relationships and stakeholder expectations."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"We had to push through analysis paralysis and trust our guts as customer-facing teams that knew the business."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Leadership doesn’t only mean managing; it can be mentoring, product leadership, or technical influence."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"We went from a team of 80 to 170 overnight, and that was a wide open cheeks flushed moment for me."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Would you feel confident leaving your project success to the flip of a coin based on the fact that almost half of all change fails?"
Amy EvansHow to Create Change
September 25, 2024
"Design ops is undergoing a transformation into a CX focused team with a refined mission to drive efficiency and customer experience excellence."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"Most enterprises are not emotionally safe places; people can’t just leave emotions at the door."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"The challenge is whether your organization has the energy to overcome cultural and technical barriers driving researchers back to disposable knowledge."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
