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
"We made the conscious decision not to weaponize our product, even though it could have increased revenue and sales."
Mariah HayEthics in Tech Education: Designing to Provide Opportunity for All
June 14, 2018
"That holiday party in Medina was eye-opening—tech execs talking about vacation homes, and I thought, I want that world."
Chelsey GlassonExit Interview #3: Same as It Ever Was: What Leaving Tech Taught Me About Change
December 17, 2025
"Keeping communication fluid with participants until the moderated session keeps them engaged and less likely to forget."
Roberta Dombrowski Lianna Aduana5 Reasons to Bring your Recruiting in House
September 30, 2021
"My job was to find out why. Why was he frowning? Why was he sighing?"
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"It’s not always a charismatic repository that people flock to, but tools that seek you out where you work are more effective."
Ned Dwyer Emily Stewart James WallisThe Intersection of Design and ResearchOps
September 24, 2024
"We still do a lot of coding transcripts by hand, and I’m not sure where the ideal digital intersection is."
Andrea GallagherThe Problem Space
May 16, 2019
"Emergency management is political—not partisan, but political—and that reality has transformed how we work in this field."
Alicia D. JohnsonDisasters and the 21st Century
December 10, 2021
"It’s not about solving or fixing complexity. We’re making sense of it so we can operate in it."
Kyle GodbeyNon-linear service design for complex adaptive systems
December 10, 2025
"We try to limit routine global calls and break large meetings into three regional meetings so people don’t have to join at impossible hours."
Kim LenoxLeading Distributed Global Teams
May 20, 2019