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 ops is about people, processes, and practice working together to reduce friction and help designers be productive."
Jose Coronado Julie Gitlin Lawrence LipkinPeople First - Design at JP Morgan
June 10, 2021
"All the content, including slide decks and sketch notes, will be posted promptly after each session."
Bria AlexanderOpening Remarks
March 28, 2023
"Being far removed from the consequences of your design work can lead to apathy and a shrug of the shoulders."
Mariah HayEthics in Tech Education: Designing to Provide Opportunity for All
June 14, 2018
"If I can’t fix a problem someone brings up, I tell them honestly and promise to support them however I can."
Shipra Kayan Tess DixonHow Tess Dixon Facilitates Team Engagement and Collaboration at Condé Nast Using Miro
October 1, 2021
"In the enterprise, it’s really about make me effective taking into account non-user personas as well as the individual."
Craig VillamorResilient Enterprise Design
June 8, 2017
"We must keep communication channels open and multiple — including anonymous ones — so people feel safe to speak up."
Brian MossWhat Does it Mean to be a Resilient Research Team?
March 9, 2022
"You have to go from being able to deliver a message in three bullets and then turn around in the next moment and deliver a massive service blueprint or customer journey."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"Break your design system components and stress test them to see where they break so you can improve them."
Dave Malouf Amy ThibodeauPanel: Design Systems and Documentation
November 7, 2017
"There’s never been a better time for designers to get their hands on tools that seemed far away before."
Shipra Kayan Robert Kortenoeven Eileen TangEmerging principles for using AI in Design: What the product design team at Miro has learned from deeply integrating AI in their workflow
June 11, 2025
