Summary
Moving the research function out from UX can transform how insights influence product-making in an organization. In this talk, Nalini explains how and why she led this shift for her team at Salesforce, as well as the move’s effect on their work and impact. Nalini will also share lessons learned in the process - “the how to’s” and the “absolutely how not to’s” - that may inspire and guide leaders and individual contributors alike.
Key Insights
-
•
Decoupling research from UX can provide researchers with more agency to frame broader business problems beyond design.
-
•
Identity work is a fundamental challenge when moving research out of UX, requiring careful leadership attention.
-
•
Playing the long game through persistent business case building and internal socialization is essential for organizational change.
-
•
Research teams positioned alongside product management, engineering, and data science gain higher visibility and influence.
-
•
Measuring research impact becomes more complex but broader, shifting from simple metrics like study counts to influence and strategic involvement.
-
•
Research operations functions are crucial infrastructure that enable scalable, efficient research beyond UX.
-
•
Control over budget and headcount advocacy improves significantly when research reports outside UX.
-
•
COVID-19 amplified issues around identity and belonging for team members during organizational transitions.
-
•
In B2B companies like Salesforce, much product decision-making happens before UX, necessitating research involvement earlier in the lifecycle.
-
•
Providing reassurance and support for new research skills helps ease team anxieties during structural changes.
Notable Quotes
"What happens if research does not report into UX? What might happen if we uncouple research from UX?"
"We made this move in January 2020 — our research and insights team moved out of UX but stayed within product organizations."
"Conscious uncoupling is about identity — how one thinks of oneself defines oneself and how others define you."
"I believed we could do more — more for the company, customers, stakeholders, and ourselves if we had more agency."
"Our research practice was perceived largely as design testers, empathy vehicles, and policing functions — a narrow, reactive role."
"After the move, our work had more impact, more visibility, and we're present across the entire product life cycle."
"Research operations is the spine of any successful research and insights group."
"For the first time, I was able to advocate for funding directly for the research function at high executive levels."
"I underestimated how much identity our team tied to UX and how scary that loss felt to many of them."
"Our shift is structural, not because of personalities — it was needed to influence earlier, more business-centric decisions."
Or choose a question:
More Videos
"Design operations maturity has levels: defined process, scaling practices, and finally automation investment."
Farid SabitovAutomatization for Large Enterprise Teams
January 8, 2024
"A confusing, difficult hiring process is itself an equity issue—transparency helps reduce gatekeeping."
Charlotte Vorbeck Shahzma Esmail Edward Alton Sarah McArthur Ariel KennanPipeline to Civic Design
December 9, 2021
"Don’t read canned questions during interviews; make it conversational and human."
Corey LongHiring in DesignOps: A Critical Study on How to Hire and Get Hired
September 23, 2024
"We’re moving from wanting to see the table to having an actual place at it."
Bob BaxleyTheme 4: Intro
January 8, 2024
"Don’t tell government teams you’re using design thinking—use their language and let them experience it first."
Steve ChaparroBringing Into Alignment Brand, Culture and Space
August 13, 2020
"Small, tactical projects helped us secure political will and organizational capacity needed for systemic policy change."
Sarah AuslanderIncremental Steps to Drive Radical Innovation in Policy Design
November 18, 2022
"We’re selectively skeptical—skeptical about some things but not others based on what we want to believe."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"When a cognitive level is missing, users adapt by performing higher-level tasks as workarounds, which is exhausting."
Zen RenTaking Inspiration from Instructional Design for Research
March 10, 2022
"Sometimes you have to give permission to yourself and your team to try something different."
JD Buckley Margot Dear Jim Kalbach Janaki KumarCOMMUNICATE: Discussion
June 14, 2018
