How to write each product document well — the method step by step, the mistakes that sink them in review, and a checklist before you call it done. Each guide pairs with a structured template in the document library.
Establish why the question is being asked now, with data rather than fatigue: usage, revenue, cost to maintain, strategic drag.
Define what fit would look like for this product and market before examining any evidence — the signals, and the bar each must clear.
Work backwards from the decision you need.
Choose the competitor set from your customer's point of view — include the alternatives they actually weigh, which may be spreadsheets and doing nothing, not just rival products.
Define the market before you measure it — a fuzzy boundary makes every later number meaningless.
Capture why discovery is being commissioned — the trigger, the background, what is already known.
Anchor everything to the problem and objectives first, so each requirement can be traced to a reason.
Begin by restating what you set out to test and what result you agreed would count as validation — before you look at the findings.
Ground the vision in inputs — strategy, customer evidence, market direction — rather than wordsmithing in a vacuum.
Start from the customer problem and the evidence behind it, not the idea.