Summary
During the talk, panelists including Nova, Adam, Melissa, and others shared practical strategies for integrating customer success teams into product development early, as Nova recommended embedding them within scrum teams. Lauren McEwan raised challenges around documenting design decisions, which Melissa and Adam addressed by attaching rationale directly to screens and embedding customer profiles in JIRA stories for developer clarity. A key topic was the evolving role of research teams beyond conducting studies toward empowering others, a concept highlighted by the Autodesk team’s approach to enable research across the organization. Marco Ducostano’s question about managing feedback focus was tackled by using the RICE prioritization framework and maintaining frequent sprint discussions to balance effort and impact. Caroline Lamb’s query on improving product manager (PM) feedback highlighted the importance of relationship-building and co-leading research initiatives to coach PMs in asking better questions. Julie’s inquiry on data synthesis revealed best practices involving pre-planning, track leads organizing moderators, and using tools like MURAL to facilitate distributed collaboration. Michael Maternal raised concerns about managing customer expectations when vision exceeds delivery pace, and panelists stressed transparent, ongoing communication and real product delivery, using Intuit’s User Voice as an example of closed feedback loops. Malini Rao and Smitha described methods for translating research into product improvements, including dedicated engineering days to address prioritized customer requests. The session emphasized collaboration, synthesis, democratization of research, prioritization, and maintaining trust through responsive customer engagement.
Key Insights
-
•
Embedding customer success leaders early in scrum teams enhances alignment and product outcomes.
-
•
Documenting design decisions alongside screens with explanations aids clarity and future reference.
-
•
Research teams add value not only by doing studies but by enabling and coaching others to conduct research.
-
•
The RICE method (Reach, Impact, Confidence, Effort) effectively prioritizes customer feedback for sprint scope.
-
•
Effective feedback management requires frequent, ongoing team discussions to dynamically prioritize issues.
-
•
Building strong personal relationships with PMs is critical to improve the quality of research questions and product feedback.
-
•
Synthesizing vast research data requires structured planning before and after research with collaboration tools like MURAL.
-
•
Closing the loop with customers by sharing how feedback influences product releases builds trust and loyalty.
-
•
Dedicated engineering days focused on incremental improvements help act on smaller research insights outside big tracks.
-
•
Democratizing research amplifies impact, but researchers remain essential as coaches, mentors, and program managers.
Notable Quotes
"Find who the customer success leader is and get them embedded right in your scrum teams at the beginning, that's huge."
"We would put design decisions along with each screen to explain the rationale, so if people had questions they could refer back."
"The value of research is magnified when we democratize it and let others do research with us and on their own."
"We use the RICE method—reach, impact, confidence divided by effort—to prioritize customer requests in our sprints."
"At our sprint meetings three times a week, we discuss if a piece of feedback has already been prioritized or needs attention."
"You have to build a relationship first before you can advise PMs on asking better questions."
"Organize synthesis before the research happens by aligning on themes and goals with moderators and track leads."
"Real research by real teams that can build real products and show customers they're listening is massively helpful."
"Our engineering days let engineers pick up smaller ideas from research or bugs and improve the product incrementally."
"The researchers' role includes coaching, mentoring, and leading research efforts, not just doing research ops."
Or choose a question:
More Videos
"Land acknowledgments don’t actually change the allocation of power or resources; they work at the mythological level."
Victor UdoewaRadical Participatory Design: Decolonizing Participatory Design Processes
December 10, 2021
"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
"Disability isn't rare; one in five people have a disability right now."
Sam ProulxAccessibility: An Opportunity to Innovate
September 8, 2022
"Bring your clients and stakeholders into the process early to make sure the visual language works for them."
Mujtaba HameedFrameworks for Excellence: Using Visual Thinking and Communication to Elevate Your Research
March 26, 2024
"Always engage with the brand team on day one to avoid awkward and confrontational approval processes later."
Michele WongHelping Them Help Us
January 8, 2024
"Our field was not born five years ago; we've been through these growth pains before."
Tala Tayebi Kelly Goto Jared SpoolVoice and influence in an age of noise
March 10, 2026
"If you’re not investing or quitting something, what is the point of having a strategy?"
Adam ThomasSurvival Metrics – Making Change in a Fast, Data-Informed, and Politically Safe Way
December 6, 2022
"Almost every kind of UX is happening in settings that have big challenges of scale and complexity that you see in enterprises."
Wendy Johansson Surya VankaDesign at Scale: Behind the Scenes
April 29, 2021
"Taking care of the basics and creating opportunities lets us get out of the way and let the team thrive however they see fit."
Tess DixonC'mon Get Happy
September 29, 2021
Latest Books All books
Dig deeper with the Rosenbot
How does Rosenfeld Media ensure high quality and relevance across its Rosenverse offerings?
What strategies help speed up the procurement and legal review of UX research platforms in organizations like LinkedIn?
How should product teams approach AI-generated insights to ensure research rigor and avoid bias?