Discovery Hand-Offs Kill Momentum: Here’s What to Do Instead

Teresa Torres argues that handing discovery findings from a product trio to the rest of the delivery team recreates the old waterfall 'game of telephone', losing context and distorting customer needs. Discovery should be led by the trio but involve the whole team, who need a direct line to customers. She proposes making work visible while it happens rather than packaging it into decks afterward, and continuously reminding teammates where to follow along. Keeping discovery artifacts in tools the whole team already uses, and weaving updates into standups, sprint planning, and retrospectives, lets the team stay engaged without sprint planning becoming a hand-off.

01Key takeaways

• Avoid handing discovery findings to delivery as requirements, since each hand-off loses customer context.
• Have the product trio lead discovery, while everyone on the team participates in some discovery activities.
• Visualize your thinking during discovery with artifacts like interview snapshots and opportunity solution trees.
• Store discovery artifacts in tools the whole team already uses rather than introducing a new one.
• Post continuous updates and actively invite and act on team feedback rather than broadcasting only.
• Link every user story to its supporting discovery work so sprint planning is never the first time the team hears the rationale.

02Key sections

Why hand-offs distort customer needs

Each functional hand-off strips context and nuance, so requirements reaching engineers bear little resemblance to what customers said. Direct trio involvement with customers avoids this.

Discovery is led by the trio, not a separate team

Dual-track Agile should not mean separate discovery and delivery teams. The trio leads discovery, while all team members contribute and see customers at times.

Show your work while doing it

Rather than separating doing and showing, teams should visualize their thinking continuously using artifacts like interview snapshots, opportunity solution trees, and assumption maps.

Remind the team where to follow along

Pick an existing asynchronous channel everyone already uses and post continuous updates there, inviting feedback and reinforcing them in standups, sprint planning, and retrospectives.

03From the post

“One of the primary benefits of working in a product trio is we reduce the hand-offs between functional roles. In the old way of working, a business stakeholder communicated a need to a product manager, the product manager wrote requirements, handed them off to a designer, who then created”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.