discovery-process

Run a structured product discovery cycle by executing six phases: frame the problem, plan research, conduct interviews, synthesize insights, generate and validate solutions, and document a go/no-go decision.

The best way to frame product problems before customer interviews is using problem framing canvases and structured problem statements to align cross-functional teams on the target hypothesis.

Yes, you can use opportunity solution trees and lean UX canvases together during the generate and validate phase to map solution paths and run experiments before a go/no-go decision.

For a continuous discovery cycle, you should schedule 5-10 customer interviews to gather sufficient qualitative data for synthesizing insights and testing 1-2 solution experiments.

Yes, this discovery process supports cross-functional alignment over a 3-6 week timeframe, coordinating iterative learning, interview synthesis, and experiment validation to de-risk build decisions.

You should not use a 6-phase product discovery process if your timeline is under 3 weeks, as the workflow requires adequate time for interview scheduling, synthesis, and experiment validation.