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
-
•
Moving research out of UX gave the team more agency to frame broader business problems, not just UX design issues.
-
•
The organizational move was framed as a conscious uncoupling, highlighting the identity shift for researchers.
-
•
Long-term persistence and a carefully built business case were key to gaining executive buy-in for the move.
-
•
The research team’s impact grew by extending involvement along the entire product lifecycle, from pre-build to post-ship.
-
•
Separating research from UX enabled direct budget advocacy and investment in research operations, improving infrastructure and effectiveness.
-
•
Identity anxiety among researchers about skill transferability and team culture was underestimated during the transition.
-
•
Research impact measurement shifted from design quality metrics to more complex influence and strategic input metrics.
-
•
Salesforce’s B2B context required research beyond UX because many product decisions happen early at enterprise levels.
-
•
Researchers valued the uncoupling as it allowed them to focus on craft and do more meaningful research work.
-
•
Strong cross-functional relationships remained important after the move, redefined as peer-level partnerships.
Notable Quotes
"What happens if research does not report into UX? If we uncouple research from UX, what might happen?"
"Our research practice was perceived largely as design testers, empathy vehicles, and policing functions within UX."
"We could do more for the company, our customers, our stakeholders, and for ourselves with more agency."
"I played the long game. You often need to embrace the long game to really have influence or change."
"When we moved out of UX, our work had more impact and we received more visibility within the company."
"Being separate from UX allowed us to invest explicitly in the research operations infrastructure—the spine of any successful research group."
"I completely underestimated the importance of UX in my team’s identity and how anxious people would feel."
"People worried their skills weren’t transferable outside of UX, even though the research craft is similar."
"Tracking research impact after the move is harder because influence is less tangible than design-testing metrics."
"For many decades, research wasn’t associated with UX; it was about framing problems, choosing methods, analyzing, and providing solutions."
Or choose a question:
More Videos
"Imagine if everyone you worked with had deep empathy for your customers and made decisions based on those customer needs."
Amy Jiménez Márquez Michael J. Metts Joie ChungThe Atypical UX Manager Path (Videoconference)
July 23, 2020
"Product and design teams are usually the best initial stakeholders to engage for rapid research programs."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"Building relationships means listening more than evangelizing and making research a partnership rather than a solo mission."
Chris Geison Cristen Torrey Eric MahlstedtWhat is Research Strategy?: A Panel of Research Leaders Discuss this Emergent Question (Videoconference)
March 4, 2021
"You have to trust the process even when the fuzzy front end is scary and you don’t know where it’ll take you."
Julie BaherCulture Change—My Journey
May 14, 2015
"Facilitation is part setting the stage and part performing on it."
Shelby SwitzerMaking Space for Community Knowledge-sharing in a Distributed World
December 10, 2021
"Concept validation lets us objectively decide which features to build based on perceived usefulness and intent to use."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"Taxonomy tags should be relevant to user goals and shouldn’t be changed often without intention and governance."
Tony TurnerCapturing Deep Insights
September 30, 2021
"Inclusive design is an additional layer that anticipates broad human perspectives, not just usability or accessibility alone."
Lija HoganContexts of Use: A Framework for Connection
December 9, 2021
"Hybrid analog-digital tools allow teams in low-resource contexts to engage effectively."
Surya VankaUnleashing Swarm Creativity to Solve Enterprise Challenges
June 10, 2021