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
"Slack is a huge part of how we are going to be engaging in today’s conference."
Bria AlexanderOpening Remarks
October 3, 2023
"Using modules or templates in co-design helps participants remix and add, making it easier to surface rich insights."
Nidhi Singh Rathore Amber DavisEmbracing participation to unlock deeper truths in commercial research
March 12, 2025
"The conversation is about how much is this team costing the organization and whether that cost will be worth it in the future."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"Legacy applications linger because changing them is risk-ridden and a major undertaking."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"We hire these people full time to be designers, and they were only spending about three hours per day actually designing."
Brennan HartichCommunicating and Establishing DesignOps as a New Function
November 7, 2018
"You need to ask, who are you excluding in the conversation? That’s the disservice to empathy."
Dantley DavisLeadership & Diversity—A Fireside Chat with Dantley Davis
September 17, 2020
"We were asking for users to give us their time, but we weren’t showing them that we recognized that their time had value."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"Even bad research can be good because it creates learning opportunities."
James Wieselman SchulmanResearch is a team sport: advancing the work when everyone does the research
March 11, 2026
"We have a code of conduct. It’s not just window dressing, it’s the front door to a process with people behind it."
Uday Gajendar Louis RosenfeldDay 2 Welcome
June 5, 2024
Latest Books All books
Dig deeper with the Rosenbot
How can organizations manage the noise created by non-expert researchers conducting user research?
How can research and operations teams collaboratively evaluate new UXR tools for usability and operational fit?
What is automation bias in AI clinical decision support and how can UX design address it?