Product discovery

Mines competitors' app store, G2 or marketplace reviews for loved features, recurring complaints, switching triggers and unmet needs, with counts and verbatim quotes. Use to find openings.

Writes jobs-to-be-done statements and maps the forces of progress (push, pull, anxiety, habit) and the switching timeline from customer interviews, with evidence for each.

Designs a cheap experiment such as a fake door, concierge, Wizard of Oz, landing page or prototype test for one risky assumption, with pass and fail thresholds set before it runs.

Runs a two-week discovery sprint from problem framing and assumption mapping through interviews, synthesis and tests to a decision readout, pausing for the team between steps.

Maps the desirability, usability, feasibility and viability assumptions behind a product idea, ranks them by importance and evidence, and picks the riskiest ones to test first.

Builds an opportunity solution tree from a desired outcome and research, choosing a target opportunity and pairing each candidate solution with its riskiest assumptions and a quick test.

Acts as a product coach who builds continuous discovery habits, frames outcomes over outputs and favours small tests, asking questions before offering frameworks. For PMs and product teams.

Designs or analyses a willingness-to-pay study (Van Westendorp, Gabor-Granger or interviews) with questions, sample, analysis steps and how to read the result. Use before setting a price.

Synthesises customer interview transcripts into themes, needs, pains and verbatim quotes, with how many participants support each and a confidence level. Use after a round of interviews.

Writes a discovery interview guide that asks about specific past behaviour instead of opinions or hypotheticals, with timed sections, follow-up probes and a check for leading questions.

Writes a product opportunity assessment covering the problem, for whom, size, alternatives, why us, why now, success measures, critical risks and a go, explore or stop call.

Writes a solution-free problem statement covering who has the problem, the evidence, current workarounds, the cost of not solving it and what success looks like. Use when starting discovery.

Writes a participant screener for interviews or usability tests with behavioural qualifying questions, disqualifiers that hide the target, quotas and an invite message.