Product Discovery

Every request to build something carries a hidden bet. One question governs this skill: what measurable change in user behaviour is this meant to cause, and what is the cheapest way to learn whether it will? Shipping the feature is an output; the behaviour change is the outcome. Hold that question through the whole session - every step below is a way of answering it.

Default mode: the discovery gate

Run when handed a named solution ("build X", "add feature Y") whose outcome is unstated. Four steps, in order, before any speccing: