Continuous Discovery

Discovery & Research

For: PMs running user interviews and synthesizing feedback

Interview debrief: from transcripts to opportunities, not feature requests

Five user interviews this week. Extract opportunities — not feature requests — while keeping quote-level receipts.

Copy & paste into your own LLM · open in archive →

You are a product-discovery coach processing user-interview transcripts. I will paste anonymized notes or transcripts. Produce:

A) OPPORTUNITY TABLE — columns: opportunity (the need or pain, phrased in the user's own words), verbatim quote + interview number, frequency across interviews, severity signal (workaround built / paying for alternative / complaining only), existing workaround.

B) FEATURE-REQUEST TRANSLATION — every explicit feature ask in the material, mapped back to the underlying need it expresses, with the quote.

C) NEXT TESTS — the 3 assumptions now most worth testing, each with the cheapest honest test design (fake door, prototype walkthrough, concierge).

Inputs: [PASTE ANONYMIZED TRANSCRIPTS OR NOTES, LABELED BY INTERVIEW NUMBER + SEGMENT] · [PRODUCT + SEGMENT CONTEXT]

Rules: Do not invent user quotes, merge users into composites, or infer needs no quote supports — write "not observed" instead. Verify frequency counts before this enters a roadmap argument. Keep users anonymous: no names, emails, or company identifiers in the output.

Why it works: Translating feature asks back to needs is what separates discovery from order-taking. Frequency and severity columns stop the loudest interview from writing the roadmap, and the quote-level receipts survive the stakeholder who asks 'says who?'

Useful? 👍 Yes👎 No

Write the Contract

PRDs & Specs

For: PMs drafting specs engineering will actually build from

PRD skeleton with the edge cases the eng team will actually find

You have a validated problem and a solution sketch. Draft the PRD skeleton — with the edge cases and non-goals that prevent the week-3 surprise.

Why it works: PRDs fail at the edges, not the happy path. A forced sweep of empty/error/permission/concurrency/migration states is where 'we didn't think about that' dies, and explicit non-goals are the cheapest scope-control tool a PM has.

Useful? 👍 Yes👎 No

Sequence With Receipts

Prioritization & Roadmaps

For: PMs force-ranking backlogs and defending roadmaps

Backlog stack-rank: RICE with an audit trail and a kill list

Planning week. Force-rank the backlog with every assumption visible — so the roadmap review is about trade-offs, not vibes.

Why it works: RICE without input provenance is false precision. Labeling measured/estimated/guess plus a sensitivity pass shows exactly which ranks are real and which are one stakeholder's opinion deep — that is the honest version of the roadmap fight, held before the quarter starts.

Useful? 👍 Yes👎 No

Manage the Room

Stakeholder Comms

For: PMs driving cross-functional decisions and updates

Decision memo: one page that gets an aligned yes (or a fast no)

You need a cross-functional decision and the meeting keeps slipping. Write the memo that gets it decided async — or makes the meeting 15 minutes.

Why it works: Default-if-no-decision is the forcing function — silence becomes a choice with a stated cost. Mapping each stakeholder's objection to the exact line that answers it turns the review from re-litigation into ratification, and 'not deciding today' kills scope sprawl in the room.

Useful? 👍 Yes👎 No

Evidence Over Opinions

Metrics & Experiments

For: PMs and analysts turning test results into ship decisions

Experiment readout: from raw results to ship / iterate / kill

The A/B test ended. Write the readout that survives the skeptic in the room — validity checks, segment cuts, and a labeled-confidence recommendation.

Why it works: Most experiment 'wins' die under three questions: was the sample ratio right, did you peek, does it hold by segment. Building the validity table into the readout means you ask them before your CPO does — and labeled confidence keeps a marginal result from shipping as a sure thing.

Useful? 👍 Yes👎 No

What you did NOT get today (Pro)

Prompt of the Week (Pro)

This week's bonus: a churned-user postmortem prompt that turns exit-survey verbatims and usage timelines into a ranked churn-driver table — with a strict quote-or-it-didn't-happen evidence rule.

Which section is most useful to you this week?

One tap — it shapes which prompt leads next week.

What would you like to see more of?

Get all five sections — every day

Pro unlocks all 5 sections’ prompts each issue, plus the full searchable archive. $14.99/mo.