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 had no budget, we had no backing, and it was a huge success."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"We shifted from thinking of salary as an individual thing to thinking of revenue as a collective resource."
Chelsea MauldinLet's Talk About Money
November 17, 2022
"Math models don’t just provide numerical precision, they can be inspirational for thinking about UX spread."
Scott PlewesWhy Isn't Your UX Approach Going Viral?: A Mathematical Model
March 28, 2023
"Companies are rethinking their role as more than just business; they’re thinking about new forms of care and community."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Where are our blind spots that cause us to forget or ignore important parts of our journey?"
Dave MaloufTheme 3: Introduction and Provocation
January 8, 2024
"Adoption is the only thing that matters in innovation. If you’re not changing behavior, you haven’t innovated."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Design is open source; everybody participates, but you need facilitation to make good on that promise."
Bob Baxley Sara Asche Anderson Sharon Bautista Frank Duran Jamie Kaspszak Abbey Smalley Sylas SouzaTheme 4: Discussion
January 8, 2024
"The most successful way to ask about job function is a single-select question, not an open field."
Sydney LawsonAnatomy of a Strong User Panel
March 10, 2026
"There is an emerging role of document architects who design how information is interconnected and triggers workflows in these platforms."
Scott StephensThe Next Generation in DesignOps Toolsets
July 28, 2022
