Summary
Science orgs typically lack designers and for good reason; there is no product. The focus is on data. The currency is discovery. Why spend money on a designer when we need to buy a new microscope? So how do we create a better experience through design for science? In this talk, Mark will outline his approach to operationalizing design in science orgs, first in CERN and now at the European Molecular Biology Laboratory.
Key Insights
-
•
Scientific organizations like CERN and EMBL operate without profit motives and measure success through published research, not product delivery.
-
•
Leadership in these organizations is bottom-up, lacking top-down yearly objectives or strict product roadmaps.
-
•
Research groups are siloed and protected due to external funding and the priority of uninterrupted scientific work.
-
•
Many digital creators in scientific organizations don’t identify as designers, requiring a broader definition of design teams.
-
•
EMBL estimated about 500 people across 200 teams are effectively designers despite not holding that title.
-
•
The philosophy of marginal gains, popularized by Dave Brailsford, drives continuous small improvements across systems.
-
•
Bruce Lee’s idea that fixed patterns can't adapt to reality inspires an adaptable, experimental approach to organizational change.
-
•
Design ops success comes from working with existing organizational culture rather than trying to impose new frameworks.
-
•
Committees, though often ineffecitve in other contexts, are essential to debate and scrutiny in scientific organizations.
-
•
Effective communication is critical; repeating key messages is the core of managing design ops in complex, decentralized environments.
Notable Quotes
"In science, success is publishing. The product isn’t the output; a Nature paper is."
"The organization is bottom up. There’s no top down hierarchical guidance on where things should go."
"People making digital things here often don’t call themselves designers, but they are designers to us."
"We went from a handful of designers to about 500 overnight, by redefining who a designer is."
"If we make tiny little inconsequential changes across the whole system, they aggregate to better outcomes."
"My job is 90% saying the same thing over and over and over again."
"Committees never work, but in this context, they are how debate and scrutiny happen."
"We have to go with organization culture instead of against it, and see what sticks."
"User researchers can’t be called researchers here, because scientists are researchers already."
"Who is a designer anyway? If we think differently about that, we can think differently about design ops."
Or choose a question:
More Videos
"A 101 conversation over coffee yields better insights than written reviews in 360 assessments."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Sometimes the director is the most senior design person in the org and ends up playing the executive role without the title or support."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Digital is a system, not a project. It’s there all the time and you have to keep iterating on it."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"The time for action is now, and it must be collaborative."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"Design your processes around learning, have blameless post mortems and celebrate failures especially."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Never be afraid to get into good trouble; start by asking why."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"We aimed for research that is actionable, not just insightful or pretty to look at."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"We manage the environment in which knowledge distribution takes place, not the process itself."
Designing Systems at Scale
November 7, 2018
"You’re never testing an idea purely; you’re always testing the implementation of that idea."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
