Summary
The speaker from IBM outlines how the company's design culture is deeply rooted in shared values, rituals, heroes, symbols, and practices, emphasizing that culture cannot be faked or bought but must be lived over time. Drawing from their experience at IBM and SteelCase, they highlight the importance of behaviors over time as the foundation of culture. Key contributors like Paul Rand and Doug Powell are cited as heroes shaping this legacy. IBM’s design talent acquisition is highly selective, reviewing over 10,000 candidates to hire 1,500 designers, all entering with a unified 'designer' title fostering multidisciplinary growth. The IBM Studios Network offers adaptable workspace designed for collaboration across disciplines, dissolving 'us vs them' mentalities between design and engineering. Their IBM design thinking framework centers on user outcomes, multidisciplinary teams, and continuous iteration via 'the loop' of observe, reflect, and make. Tools like Hills, Playbacks, and Sponsor Users keep teams aligned and rooted in user needs. The IBM design language provides a system of unity rather than uniformity across 3,000 products, enabling cohesive yet expressive design. Announcement of forthcoming IBM design research underscores user-inclusive, practical inquiry beyond traditional methodologies. The speaker candidly admits ongoing challenges in scaling design at IBM but remains optimistic about refining practices and sustaining culture, always with outcomes and user impact at the center.
Key Insights
-
•
Culture is defined by behaviors over time, not slogans or statements.
-
•
IBM hires design talent extremely selectively, taking less than 1% of applicants.
-
•
Every designer at IBM is hired under the generic title 'designer' to encourage multidisciplinary growth.
-
•
Flexible, mobile workspaces in IBM Studios empower designers and cross-functional teams to reconfigure their environment daily.
-
•
IBM design thinking emphasizes user outcomes, multidisciplinary teams, and relentless reinvention through continuous iteration.
-
•
The 'loop' model combats common pitfalls where designers avoid building and developers avoid reflection.
-
•
IBM’s Hills, Playbacks, and Sponsor Users ensure focus on user-centered intent, safe critique, and direct user collaboration.
-
•
The IBM design language aims for system unity, not uniformity, balancing cohesion with designer expression across thousands of products.
-
•
Accessibility is embedded from the start, not bolted on afterwards, supported by training and onboarding.
-
•
Sustainable design culture requires enduring elements: people, places, and practices that outlast current leadership.
Notable Quotes
"Behavior over time is your culture."
"You can’t fake culture and you definitely can’t buy it."
"One out of every 40 portfolios are selected; hiring here is super choosy."
"We call everybody a designer to encourage branching out across disciplines."
"If people say 'the design team', it sets up an us and them between design and engineering."
"The loop is an infinity loop where we observe, reflect, and make."
"An intern once challenged a senior VP in a playback about whether an idea was smart enough."
"The design language is a system of unity instead of uniformity."
"Accessibility is baked in from the very beginning and threaded through the entire effort."
"None of this matters without outcomes. We have to design with an outcome in mind."
Or choose a question:
More Videos
"When teams lose a sense of agency, they act strange, cutting corners and racing to get something out the door."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"If I don’t have a map, I can’t see patterns or apply context-specific gameplay."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Bias is a tendency, feeling or opinion for or against something without reason or evidence."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"It takes at least one team member to choose to set healthy standards for collaboration."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Providing more holistic recommendations helped us gain more trust and buy-in from stakeholders, increasing UX maturity."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"How do you create a sense of craft in an environment fraught with ambiguity, complexity, and anxiety?"
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Trust is often underestimated but is critical when designers face public critique and feedback."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"If you come with a big idea, they’ll try to dial you back to the smallest iota you can test first."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Design Ops people want to standardize processes and reuse organizational knowledge for clarity and confidence."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
