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
"I’ve been using screen readers for 30 years and accessibility has always been a passion of mine."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"In government, the org chart really matters – it influences who talks to whom and who gets to interface."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Going from 100 to 200 people, suddenly product managers started hearing from a dozen people a week with conflicting requests."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Innovation is about being fearless, breaking rules, and refusing to stop at the way things have always been done."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The trusted partnership between the chief of staff and the executive is critically important."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Self-service was a model with the most unknowns but possibly the biggest rewards."
Amy EvansHow to Create Change
September 25, 2024
"Teleportation lets us move throughout the organization by building tools that gather disparate data for real-time decision making."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"The enterprise feels like a big elephant; different people touch different parts and argue what it really is."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"We wanted a living network of knowledge so yesterday’s insight connects to today’s evidence and tomorrow’s learning."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
