Lifecycle · Phase 1 of 8
Discovery comes down to one key decision: is this problem worth solving? Gensudo provides 58 governed templates to help teams answer it with evidence and confidence.
Discovery is where a product team works out whether a problem is real, who has it and how much it matters. The phase ends with one key decision: is this problem worth solving? Everything produced during Discovery, including evidence, interviews and market context, helps teams make that decision with confidence rather than instinct.
To answer whether a problem is worth solving, teams need to determine:
Gensudo includes 58 Discovery templates across five product roles, with the Creative Director using 15, the Product Manager 13 and the Product Owner 13. Discovery is treated as a shared team activity, not something owned by research alone. Templates cover key documents such as the Product Discovery Brief, Market Research Report, Opportunity Assessment, Persona Document and Jobs-to-be-Done Analysis. Each template explains why it matters, who needs to approve it and what good looks like. Gensudo’s shared research pool can also support drafts with cited market, competitor and customer evidence, with research included at no extra credit cost.
Open a Product Discovery Brief and write down what you believe, what you assume and what you genuinely don't know. Naming the gaps is the point — they set the research agenda.
Build the market picture: research reports, competitor intelligence, customer conversations. In Gensudo, project-level research runs once per category and every finding carries a source you can check.
Turn raw evidence into personas, jobs-to-be-done and journey maps — a shared, concrete picture of who has the problem and what they're trying to get done.
Bring it together in an Opportunity Assessment: how big, how urgent, how contested. This is the document the decision will lean on.
Decide — with the evidence in front of you — whether this problem is worth solving. If yes, Validate is next. If no, discovery has done its job cheaply.
There is no fixed answer — discovery should be proportionate to the risk of being wrong. A small bet in a familiar market needs days; a new market or a large investment deserves weeks. The exit test isn't elapsed time, it's whether you can answer "is this problem worth solving?" with evidence someone else could check.
Discovery establishes that a problem is real and worth attention; validation tests whether your intended response to it will actually work. Discovery asks "is this problem worth solving?" while validation asks "will this solution earn demand?" — and closes with a proceed, revise, pause or stop decision. Doing them in order keeps you from testing a solution to a problem nobody has.
Start with a Product Discovery Brief. It captures what you believe, what you're assuming and what you don't yet know — which tells you exactly what research to do next. Documents like the Market Research Report, Persona Document and Opportunity Assessment then build on it in a sensible order. In Gensudo, each carries guidance on why it matters now and what good looks like.
Direct customer evidence is the strongest input, but it isn't the only one. Gensudo's research pool gathers cited market, competitor and customer jobs-to-be-done evidence at project level, and you can add your own facts, which are treated as first-party. Where something genuinely isn't knowable yet, a good discovery document says so plainly rather than papering over the gap.
Discovery is one of eight phases. See how all 382 templates fit together across five roles and the whole lifecycle.
Browse the document library →You've decided the problem is worth solving. Validation pressure-tests your response to it before serious money is committed.
Go to the Validate phase →Create a project, open a Product Discovery Brief and see what guided, decision-grade documentation feels like.