Summary
Design Ops and Research Ops teams are essential to design and research, providing strategic perspective as they solve problems and remove blockers. In this session, we review the shared functions of these two teams, focusing on Knowledge Management. We will talk about the rise and fall of research repositories in the ReOps space, outline the lessons learned, and present a way forward: a knowledge management system for both Design and Research - created and managed by Ops.
Key Insights
-
•
Effective knowledge management requires differentiating between static explicit and dynamic explicit knowledge.
-
•
Repositories alone do not solve UX knowledge challenges; principles from library science offer essential guidance.
-
•
Separating the goals of asset organization and insight sharing prevents conflated, ineffective strategies.
-
•
Reframing UX outputs as business assets shifts how organizations manage, organize, and value them.
-
•
Design information management systems enable traceability and connections between assets to drive business decisions.
-
•
Design intelligence adds a missing layer to business intelligence by providing actionable insights from UX data.
-
•
Different stakeholders require tailored views and context from UX knowledge systems, from VPs to individual contributors.
-
•
Integrated, scalable UX ops that combine research and design operations align better with product and business operations.
-
•
Building shared taxonomies and connective tissue is critical to making UX assets findable and useful.
-
•
Human expertise is essential alongside technology in building successful knowledge management ecosystems.
Notable Quotes
"Don’t decide on the solution before you understand the problem space."
"UX research repositories were trying to do what librarians and archivists have been doing for hundreds of years."
"Many key outputs we create in UX are actually valuable resources that generate revenue and contribute to business success."
"The repository isn’t the solution to your problem—knowledge management is."
"We need to build stronger scaffolding or connective tissue—shared taxonomies and relational schemas."
"Design intelligence is the layer that sits on top of the design information management system to produce actionable information."
"Different roles need different slices of information and types of context from UX knowledge systems."
"We’re currently contributing to the siloing of information by how we organize ourselves."
"Business intelligence exists in many functions, but design intelligence is often missing."
"As soon as teams start using these tools, they often see how much easier it makes their job—that resistance usually goes away."
Or choose a question:
More Videos
"You need strong regional players with negotiation skills to navigate the split loyalties in global teams."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"UX directors often feel like this poor person in the middle here getting pulled in all these directions."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Human biases are the real problem behind algorithmic bias, not the algorithms themselves."
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
"OKRs are a tool for each of us to tidy our house and focus on what’s important."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Most organizations are still asking design questions at a global level; we need to be hyper-local now."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Clusters describing demographics and behaviors alone were not enough; we needed emotional personas to find value propositions."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Leadership buy-in is really important—having an executive who understands the value of knowledge creation, distribution, application, and evaluation."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
