A Consistent Culture of Design
Summary
Phil Gilbert outlines IBM's ambitious design transformation over two and a half years, aiming to embed a culture of design across 380,000 employees. He introduces the 'culture quotient' framework, emphasizing artifacts created by behaviors, the degree to which the culture embraces them, and duration of that embrace. IBM’s approach includes hiring over 450 formally trained designers, building relationships with top design schools like SCAD and RISD, and surrounding junior hires with experienced design leads such as Doug Powell and Denise Burton. Gilbert highlights the creation of rigorous intern programs led by Devon O’Brien from SCAD and the development of IBM Design Thinking as a lightweight, collaborative practice empowering multidisciplinary teams including product managers and engineers. Instead of a top-down mandate, IBM adopted an opt-in approach, accelerating early success and sustainable adoption. They also introduced a design language that balances consistency with implementation freedom, and purpose-built flexible design studios like the Austin location, encouraging movement and collaboration. Global studios in Germany, England, China, and other locations form a network unified by digital tools and collaboration platforms. Gilbert closes with cultural notes on change as a constant, unity without uniformity, and the importance of empowerment, collaboration, and the willingness to fail gracefully, validated by devotion from leadership including CEO Ginni Rometty.
Key Insights
-
•
Design culture can be understood and shaped using a culture quotient formula: artifacts created × level of cultural embrace × duration of embrace.
-
•
IBM set an ambitious goal to hire 1,000 formally trained designers within five years, hiring over 450 in two and a half years.
-
•
IBM emphasizes 'people plus practices plus places = artifacts' to generate meaningful design outcomes.
-
•
IBM Design Thinking is a lightweight practice focusing on collaboration around artifacts, not rigid processes.
-
•
An opt-in approach to embedding design thinking helped IBM accelerate early wins, avoiding top-down enforcement.
-
•
IBM built deep relationships with top design universities to recruit diverse new talent directly from schools such as SCAD, RISD, and Stanford D-School.
-
•
IBM created formal career paths for designers parallel to engineering, including Distinguished Designer and Design Principal levels.
-
•
IBM’s design language focuses on giving broad guidance instead of rigid pattern libraries, encouraging implementation freedom and evolution.
-
•
The Austin design studio was purpose-built with movable walls and spaces to foster dynamic, radical collaboration and creativity.
-
•
The program’s success depends on empowering not only designers but all IBM employees to become design thinkers who opt into the culture.
Notable Quotes
"We could create a sustainable culture of design and use it as our leading edge weapon of transformation."
"Culture isn’t just behavior over time, it’s the artifacts that culture creates and embraces over time."
"People plus practices plus places equals artifacts."
"IBM Design Thinking is about collaborating around artifacts and frameworks, not prescribing the process teams must follow."
"We decided to make it an opt-in program and that accelerated early wins and self-selected positive outcomes."
"Design thinking is the scientific method for the 21st century."
"We had an engineering culture that confused uniformity with design, and consistency with design."
"Our design language gives broad ditches on either side of the road with some nuance, but no rigid libraries at first."
"The Austin studio’s walls can be put up and taken down by a 90-pound person on a Home Depot shopping cart."
"We’re showing people how to collaborate like crazy and how to fail gracefully."
Or choose a question:
More Videos
"I’ve literally relearned how to walk."
Tamara HaleWar Stories LIVE! Tamara Hale
March 30, 2020
"We should feel empowered to propose research initiatives that stakeholders aren’t explicitly asking for."
Joanna Vodopivec Prabhas PokharelOne Research Team for All - Influence Without Authority
March 9, 2022
"If you only measure vanity metrics like downloads, you risk tracking numbers that don’t translate to real usage or value."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Transparency and honesty are the only ways I handle difficult questions about compromises for the greater good."
Nalini P. KotamrajuTwo Jobs in One: Being a “Leader who is a Researcher” and a “Researcher who is a Leader"
March 10, 2021
"What if you didn’t know there were important questions you should be asking in your data?"
Ian JohnsonLatent Scope: Finding structure in unstructured data
June 11, 2025
"How can I guide my community to design the form and behavior of light on the edge of becoming this?"
Greg PetroffExit Interview #1: Greg Petroff: From Silicon Valley Executive to Sonoma County Possibilitarian
September 24, 2025
"We need more storytelling and positive use cases to help people see how AI affects their specific roles."
Frances Yllana Jorge Arango Maria Taylor Briana ThomasThe Big Question about Impact: A Panel Discussion
September 24, 2024
"Change really cannot be done by any individual person. Change is a team sport."
Maria GiudiceRemaking the Making Company: Moving from Product to Experience
June 9, 2016
"We look to work with authors we like and enjoy being around because writing a book is a long, collaborative journey."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
