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
"Citizen participation is like eating spinach—everyone agrees it’s good, but few actually do it meaningfully."
Aaron Stienstra Lashanda HodgeLeveraging Civic Design to Advance Equity and Rebuild Trust in the US Federal Government
December 8, 2021
"Starting from scratch is really hard, but also a cool opportunity to throw away painful patterns."
John DonmoyerShipping your code generation experiments to production
June 11, 2025
"Designers are change agents within their organizations because we’re multidisciplinary, empathetic, and compassionate."
Sheryl Cababa Alexis OhThinking in systems to address climate with Sheryl Cababa
June 12, 2024
"It can take hundreds of these contacts before they start to trust."
Ariel KennanBuilding a Design Culture
June 9, 2017
"Our evaluation tool is a Google Sheet so we can quickly make adjustments without being bogged down by unnecessary features."
Ignacio MartinezFair and Effective Designer Evaluation
September 25, 2024
"If you’re the first researcher, you will often encounter organizational inertia, and the key is to find a partner team and succeed there first."
Dave HoraAdvice for Establishing Research
December 8, 2022
"Intersectionality is a framework describing compounded levels of discrimination due to overlapping identities."
Dr. Jamika D. Burge Mansi GuptaAdvancing the Inclusion of Womxn in Research Practices
September 15, 2022
"When you project Apple CarPlay, you are basically sending the device from your phone into the car, detaching from the native OS."
James RamptonThe Basics of Automotive UX & Why Phones Are a Part of That Future
July 25, 2024
"You can't just jump to the top of the pyramid like Maslow’s hierarchy—you have to consider all the underlying layers supporting the experience."
Kristin WisnewskiMeasuring What Matters
October 23, 2019
Latest Books All books
Dig deeper with the Rosenbot
What setup is required for AI tools to incorporate broader organizational context into research analysis?
What are the benefits of structuring workshops with individual ideation followed by AI-supported refinement?
How can research be integrated throughout the product development lifecycle rather than as a one-off step?