Ask Teresa: Do Product Teams Really Ship Value Weekly?

Teresa Torres answers a reader's question about how often product teams should ship customer value, concluding that weekly or biweekly delivery is an ideal benchmark rather than an immediate requirement. She explains that organizational factors like continuous deployment, regulatory gating, culture, and opportunity sizing determine feasibility. The path to faster shipping is to break large opportunities into smaller sub-opportunities through careful customer interviews and opportunity mapping, then use story mapping to find the simplest solution that still addresses the need. This matters because it reframes discovery and delivery as a continuous weekly rhythm instead of separate phases.

01Key takeaways

• Treat weekly or biweekly value shipping as a benchmark to work toward, not an overnight requirement.
• Check whether deployment practices, regulation, and culture allow frequent releases before blaming the team's discovery.
• Break large opportunities into component parts by listening closely to the detailed moments in customer stories.
• Do not confuse small batches with easy wins; still prioritize the hard, high-impact customer problems.
• When solution-shaping, start with the smallest solution that addresses the opportunity, then add value iteratively.

02Key sections

Shipping value weekly as a benchmark

Weekly or biweekly value delivery is an aspiration, but whether it is achievable depends on deployment infrastructure, regulatory constraints, culture, and how well opportunities have been broken down.

Deconstructing big opportunities

Teams should listen closely to customer stories to uncover the component decisions within a larger opportunity, then tackle them one at a time to keep batches small.

Separating opportunity choice from effort

Choosing which opportunity to pursue should prioritize impact rather than ease, while effort concerns are deferred until solution design.

Story mapping for ruthlessly simple solutions

When designing solutions, teams should start with the minimum valuable slice that addresses the target opportunity and add features over time instead of building every bell and whistle upfront.

Recap and practical steps

Increase velocity by decomposing opportunities, mapping the simplest viable solution, and iterating, building the muscle over time.

03From the post

“A good continuous discovery team is interviewing customers, mapping opportunities, and testing assumptions every week. But for teams new to discovery, it can be hard to find time for all of these new activities. Part of that is because they are still thinking about discovery as a phase that happens”

04Frameworks mentioned

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