Product Discovery Diary

Marty Cagan walks through a fabricated three-week product discovery sprint to show what the fast, iterative rhythm of discovery actually looks like compared with linear, Waterfall-style processes. The team sets product principles, builds rough prototypes, tests them with charter customers, and repeatedly cuts scope while checking feasibility with engineering and legal. Each cycle surfaces wrong assumptions and reshapes the product before any detailed documentation is written. The account matters because teams new to discovery often either over-document early or delay putting ideas in front of real users, and this concrete timeline makes the pace and purpose of discovery easier to picture.

01Key takeaways

• Start discovery by aligning on the business objectives from the opportunity assessment.
• Bring your lead designer and lead engineer in from day one and iterate together instead of handing off documents.
• Get ideas into a prototype quickly and test it with target customers early and often.
• Surface and test your assumptions fast, since stakeholders and team members often hold different beliefs about users.
• Keep cutting toward the minimal product, but verify each removal with customers so you don't lose the features that create value.
• Hold off on detailed engineering documentation until you have a product definition that is valuable, usable, and feasible.

02Key sections

Week 1: Aligning and sketching early

The team reviews the business objectives, sets product principles, drafts personas and scenarios, and builds a first prototype. Early calls reveal that the stakeholder and the product team hold different assumptions about users.

Week 2: Testing with real customers

Prototype sessions with charter customers expose usability gaps and lead to simplification. The engineer finds a feasible alternative to a costly component, and an unnecessary data requirement is removed.

Week 3: Converging on the final product

A key feature is proven critical through testing with and without it, and the prototype is refined with visual design. Stakeholders are looped in, and documentation is written only once the product definition is settled.

Key takeaways and the discovery rhythm

Cagan distills ten principles, including prototyping early, collaborating with designers and engineers, identifying assumptions, and deferring detailed documentation until the right product is found.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

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