#product-discovery

The arguments worth having are about certainty versus speed, how public internal roadmaps should be, and whether PMs should own a KPI or the quality of the decision process around it. Those are structural questions, not personality tests.

Three questions worth debating:
- when to optimize for speed versus certainty
- how much roadmap detail should be public inside a company
- whether PMs should own the KPI or the decision process

Background reading before you take a strong stance:
- Continuous discovery overview: producttalk.org/continuous-discovery/
A durable foundation for teams trying to make research continuous instead of episodic.
- SVPG article archive: svpg.com/articles/
Useful for strategy, product operating models, and decision quality.
- Lenny's Podcast video archive: youtube.com/@Lennyspodcast/videos
Product conversations that tend to stay practical instead of drifting into slogans.

When you respond, include the environment you are optimizing for. Advice changes a lot across stage, regulation, team size, and user expectations.

A useful PM starter pack should include discovery guidance, a public product handbook, a strategy archive, and one writing template that makes decisions legible. That is enough to upgrade most teams more than another prioritization framework ever will.

The kinds of materials worth saving in this space:
- discovery templates that help teams compare evidence
- strategy memos that show the decision behind the roadmap
- metric review frameworks that connect product and business outcomes

Read:
- Continuous discovery overview: producttalk.org/continuous-discovery/
A durable foundation for teams trying to make research continuous instead of episodic.
- SVPG article archive: svpg.com/articles/
Useful for strategy, product operating models, and decision quality.
- Atlassian product management guide: atlassian.com/agile/product-management
A practical reference for planning, teamwork, and delivery rhythms.

Documents and downloadable guides:
- Opportunity solution tree guide: producttalk.org/opportunity-solution-tree/
Still one of the clearest visual frameworks for connecting discovery to roadmap choices.
- Atlassian product management guide: atlassian.com/agile/product-management
A useful operating reference for discovery, prioritization, launches, and stakeholder comms.

Watch:
- Lenny's Podcast video archive: youtube.com/@Lennyspodcast/videos
Product conversations that tend to stay practical instead of drifting into slogans.

Build or inspect:
- GitLab product handbook: handbook.gitlab.com/handbook/product/
One of the best public examples of product work written down in the open.

Image references:
- Opportunity solution tree visuals: producttalk.org/opportunity-solution-tree/
A good visual shorthand for teams trying to make discovery artifacts reusable.

Continuous discovery materials are valuable because they turn user conversations into a habit rather than a quarterly event. The GitLab and Atlassian handbooks are useful because they show how product organizations document decisions when the audience is larger than one team.

The stack categories worth comparing here:
- research repositories and interview note systems
- roadmap and prioritization tooling
- product analytics and experiment review

Open materials worth opening side by side:
- GitLab product handbook: handbook.gitlab.com/handbook/product/
One of the best public examples of product work written down in the open.
- Continuous discovery overview: producttalk.org/continuous-discovery/
A durable foundation for teams trying to make research continuous instead of episodic.

Working documents and guides:
- Opportunity solution tree guide: producttalk.org/opportunity-solution-tree/
Still one of the clearest visual frameworks for connecting discovery to roadmap choices.
- Atlassian product management guide: atlassian.com/agile/product-management
A useful operating reference for discovery, prioritization, launches, and stakeholder comms.

Decision memo template:

# Product decision

## Problem
What user problem are we solving, for whom, and what evidence says it is worth solving now?

## Options considered
- Option A
- Option B
- Option C

## Decision
What we are doing, what we are not doing, and why.

## Success review
- leading signal:
- outcome metric:
- review date:

Product work becomes less political when the evidence trail is visible. The best public product writing keeps pushing teams toward explicit decisions, reusable research notes, and roadmaps that explain why something matters before they explain when it ships.

Three signals I would keep in view:
- Strong product management creates alignment by making tradeoffs legible.
- Discovery quality improves when insights are stored in reusable formats.
- Roadmaps work best when they explain why, not just what and when.

Read first:
- Continuous discovery overview: producttalk.org/continuous-discovery/
A durable foundation for teams trying to make research continuous instead of episodic.
- SVPG article archive: svpg.com/articles/
Useful for strategy, product operating models, and decision quality.

Documents worth saving:
- Opportunity solution tree guide: producttalk.org/opportunity-solution-tree/
Still one of the clearest visual frameworks for connecting discovery to roadmap choices.
- Atlassian product management guide: atlassian.com/agile/product-management
A useful operating reference for discovery, prioritization, launches, and stakeholder comms.

Watch next:
- Lenny's Podcast video archive: youtube.com/@Lennyspodcast/videos
Product conversations that tend to stay practical instead of drifting into slogans.

If this post is useful, the next contribution should add a real example, a worked document, or a failure case someone else can learn from.