By Marty Cagan · svpg.com · LinkedIn
Marty Cagan describes a common remote-work problem in product discovery: teams drift back into passing static artifacts between product manager, designer, and engineers instead of collaborating closely. His proposed fix is a short, recurring daily meeting, as brief as 15 minutes, where the core product trio reviews the latest prototype iteration together. He is clear the practice does not fully replicate co-located collaboration, but it restores some of the energy and rapid learning that discovery depends on. The argument matters because discovery relies on quickly trying ideas and assessing results together, and talking about work is no substitute for that.
01Key takeaways
- Schedule a short daily meeting where the product trio reviews the latest prototype together.
- Do not rely on asynchronous review of prototypes, since the live back-and-forth is where collaboration happens.
- Use the session to test and assess ideas together rather than just discussing progress.
- Hold the meeting at a time, such as late in the day, that lets energetic conversations continue without rushing.
- Treat this as a partial remedy: it restores some collaborative energy but will not match co-located teamwork.
02Key sections
- The remote collaboration problem
- Remote teams often fall back into handing artifacts back and forth, which erodes true collaboration. Teams feel the strain of maintaining collaboration while coping with remote work.
- Why prototypes drive discovery
- Most prototype iterations are created by the designer and many never leave the product team. Prototyping lets teams learn quickly, before wasting engineering effort on a bad idea.
- The daily prototype review
- A short, scheduled daily meeting lets the team look at the latest prototype together. Some teams hold it late in the day so enthusiasm doesn't force a rushed exit.
- Who should attend
- The product manager, product designer, and tech lead form the core attendees, with the rest of the product team invited as optional. Asynchronous review alone loses the back-and-forth that matters.
- Purpose and limits
- The main goal is to keep discovery moving by trying and assessing solutions together, with a secondary benefit of staying focused and feeling progress. The technique does not fully recreate co-location.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.