The product development cycle

In product development, it is very important to design the user experience, clearly define what future state you want to create, and validate it. After practicing those things, I created a summary of what kind of development cycle to run day to day.

Basically, we rotate with a small batch size. The point we are working on is to run the research phase at a weekly scale while also nesting it inside the release phase at a one-to-three-month scale. We are trying to avoid being trapped by local improvements while also avoiding wasteful development without validation.

In addition, as higher-level concepts above these, we rotate at the user experience design phase at a three-to-six-month scale, and at the whole-company scale at a yearly scale.

Another point we work on is continuously splitting tasks to make them smaller. If we make things small from the beginning, the ideal picture itself can become small. To prevent that, we intentionally include a step for dividing size in advance, while staying conscious of fully drawing the ideal picture.

I think product managers can create development with momentum if they stay aware of running this kind of cycle and provide the necessary follow-up at the right times.

Keywords

  • # Product development
  • # Development cycle
  • # Hypothesis testing
  • # User research