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
"When projects are late or delayed it’s often due to organizational and cultural issues rather than conduct of the project team."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Don’t send your recruiters to spam LinkedIn. That damages your brand and turns off potential candidates."
Karen PascoeDeveloping Experience Teams and Talent in the Enterprise
June 8, 2016
"When you remove nonverbal cues from communication, messages get easily misinterpreted."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"We have over 30 contracting teams spread across roughly 10 vendors all working on parts of the veteran experience landscape."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Quick fixes rarely exist in these domains because beneath every problem are layers of complexity."
Barb SpantonDoing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
June 10, 2022
"What our users see is the perfect plate, but there is so much unseen work behind it."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"Taking ugly notes together without worrying about making things pretty lowers barriers and increases engagement."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
"Understanding how assistive technology evolves is crucial because it foretells the future of interface design."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Our design ops team was a step behind the growth of our design team, solving the wrong problems at the wrong scale."
John Calhoun Rachel PosmanTwo Sides of the DesignOps Coin: Teams Ops and Product Ops
January 8, 2024
