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
"It takes patience—brick by brick—to move things forward in large organizations."
JD Buckley Margot Dear Jim Kalbach Janaki KumarCOMMUNICATE: Discussion
June 14, 2018
"We’ve got Tim Gilligan, Meredith Blackbrand, and Bria Alexander on a panel about the future of design ops."
Alana WashingtonTheme 3 Intro
October 1, 2021
"You can’t convince any organization into having some great user experience by saying it would be nice for it to be simpler."
Fredrik MathesonFirst-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix.
June 8, 2016
"Incentives are a benefit but should not be the number one reason people join a panel."
Sydney LawsonAnatomy of a Strong User Panel
March 10, 2026
"Speed matters, but saving time in recruitment and analysis can lead to invalid and biased research."
Leisa ReicheltThe Five Dysfunctions of Democratized Research at Scale
March 30, 2020
"People were taking vacation days just to homeschool or take care of a loved one."
Ariba JahanTeam Resiliency Through a Pandemic
January 8, 2024
"If you want to work with Hilton, you have to bring accessibility to the table like security and privacy."
Nicole Bergstrom Anna Cook Kate Kalcevich Saara Kamppari-MillerAccessibilityOps: Moving beyond “nice to have”
September 19, 2024
"You can be right without making others wrong by telling a story that respects their worldview."
Jon FukudaStorytelling for DesignOps
August 17, 2023
"I used GPT-4 to retag 1,200 blog posts, reducing an estimated 10–12 hours of tedious manual work to about a third of that time."
Jorge ArangoScale Smart: AI-Powered Content Organization Strategies
September 24, 2024
Latest Books All books
Dig deeper with the Rosenbot
How might cultural figures like Taylor Swift influence future movements demanding fair treatment of creators in AI?'
What does the builder team model with AI in the loop look like compared to traditional product teams?
How has AI changed the traditional design-to-development handoff process in software projects?