Five phases. Fifteen stages.

The 15 stages provide the map. There is a structured progression, but real product thinking is iterative — earlier decisions can be revisited as new insights emerge.

There is a structured progression, but real product thinking is iterative.

Method map — five phases

1. 01 Understand

   1. 01

      Idea

      Frame the initial product idea.

   2. 02

      Problem

      Define the problem independently of the proposed solution.

   3. 03

      User

      Identify the primary user who has the problem.

2. 02 Define

   1. 04

      Value

      Define the outcome and value the product should create.

   2. 05

      Product

      Define what the product fundamentally is.

   3. 06

      Lifecycle

      Name the relevant states of the central object and how it moves between them.

3. 03 Shape

   1. 07

      Jobs

      Identify what users need to accomplish.

   2. 08

      Scope

      Derive the smallest useful solution.

   3. 09

      Experience

      Describe the complete core flow, including at least one important failure or empty result.

4. 04 Specify

   1. 10

      Information Architecture

      Name the central information and objects and how they are arranged.

   2. 11

      Data Model

      Define the data model the product needs.

   3. 12

      Requirements

      Define what must be built and how it should behave.

5. 05 Learn

   1. 13

      Learning

      Define what the MVP needs to test and measure.

   2. 14

      Technical Boundaries

      Record platform and architecture assumptions, dependencies, privacy, technical risks, and open feasibility questions.

   3. 15

      MVP Boundary

      Define exactly what belongs in the MVP and what does not.

See also the method section on the homepage.