Theme 3 Discussion
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
"Google Docs is not a web page; it’s a web app that requires handling many keyboard shortcuts and focus management."
Sam ProulxEverything You Ever Wanted to Know About Screen Readers
June 11, 2021
"There is no need for you to take notes because session notes, videos, and decks will be shared as soon as possible."
Bria AlexanderOpening Remarks
November 17, 2022
"Layoffs are a collective trauma – it’s okay to acknowledge the emotions and grief you feel."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"Enterprises are basically people pursuing outcomes, doing activities, and using objects—this simple theory underpins the language of Edgy."
Milan GuentherA Shared Language for Co-Creating Ambitious Endeavours
June 6, 2023
"Without releasing control, democratizing research won’t scale. We have to empower people even if some things won’t be perfect."
Erin May Roberta Dombrowski Laura Oxenfeld Brooke HintonDistributed, Democratized, Decentralized: Finding a Research Model to Support Your Org
March 10, 2022
"When blind users choose between Android and iPhone, they weigh trade-offs between stability and customizability."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
June 6, 2023
"For many of our tech clients, there’s a demand not just to use AI but to transparently show how and why, to respond to internal scrutiny."
Mujtaba HameedThe new horizon of ethnography: using AI to unlock the full potential of in-person research
March 11, 2026
"We decided these would be the social norms now, and we just went for it."
Ilana LipsettAnticipating Risk, Regulating Tech: A Playbook for Ethical Technology Governance
December 10, 2021
"Accessibility is innovation and the kinds of features people with disabilities need are incredible conveniences for the rest of us."
Samuel ProulxFrom Standards to Innovation: Why Inclusive Design Wins
September 10, 2025
