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
"Many hiring managers feel stuck by bureaucracy and policies that haven’t adapted, limiting candidate pools to specific locations."
DesignOps and The Great Talent War of 2021
August 19, 2021
"Bring your clients and stakeholders into the process early to make sure the visual language works for them."
Mujtaba HameedFrameworks for Excellence: Using Visual Thinking and Communication to Elevate Your Research
March 26, 2024
"Use your UX skills to design better working relationships by empathizing with colleagues like you do with users."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
"Operations is a verb. You’ve always been operating — the role just invites you to do it better."
Kate Towsey Jake BurghardtResearchOps AMA with Kate Towsey & Jake Burghardt
October 16, 2025
"Design annotations in handoffs prevent accessibility details from getting lost between designers and developers."
Gabriela BarnevaOperationalizing Inclusive Design in Service Design
November 20, 2025
"You can't just measure ethics like a scientific question; you have to reason differently."
Cennydd BowlesExit Interview #2: Rediscovering the ethical heart of design
November 6, 2025
"Most teams have way too many false priority ones – their number one priority is the lack of a priority."
John Cutler Harry MaxPrioritization for designers and product managers (1st of 3 seminars)
June 13, 2024
"You have to design for throw away ability because the majority of experience gets thrown away."
Bill ScottLean Engineering: Engineering for Learning and Experimentation in the Enterprise
May 14, 2015
"If we don’t respect legacy habits, we risk interrupting workflows and causing users to have a bad day."
Paula BachImproving Legacy Software: How Much Better Does it Have to Be?
March 11, 2022
