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."
Dig deeper—ask the Rosenbot:
More Videos
"Laura let out a sigh of relief and said, I don’t think I could ever recover the way that you did."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"You do not have to go publicly thank the employer who just laid you off. They’ll be fine without it."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"If you measure an infinite number of customers, every change would be statistically significant, but not every change would be meaningful."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Logic models are boring but powerful tools to align expectations that behavior change is complex and not immediate."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"Behavioral turbulence happens when flow breaks down, causing chaotic and unpredictable user interactions."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"If you dug deeper into feedback, you'd find ways to address issues without a big change."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"The establishment mindset is colonialism manifest in the design world."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"Design Ops might not just support design anymore—our work is requested by non-designers and solving broader business problems."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"Creating and holding space is like putting bumpers up in bowling so people know they won’t fail if they engage."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
