Product Strategy Library

Before I trust a product strategy, I want to see a clear user problem, evidence that alternatives were considered, and a review plan tied to an outcome. If those three things are missing, the roadmap is usually just a wish list with dependencies.

Three evaluation axes to compare:
- quality of evidence behind the decision
- clarity of roadmap communication
- follow-through on outcome measurement

Review materials:
- Atlassian product management guide: atlassian.com/agile/product-management
A practical reference for planning, teamwork, and delivery rhythms.
- Opportunity solution tree guide: producttalk.org/opportunity-solution-tree/
Still one of the clearest visual frameworks for connecting discovery to roadmap choices.
- GitLab product handbook: handbook.gitlab.com/handbook/product/
One of the best public examples of product work written down in the open.

Save the strongest examples, scorecards, and decision memos in this folio so future teammates can see what good evaluation looked like at the time.

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.

A backlog can absorb almost any amount of ambiguity, which is why teams mistake motion for product thinking. The most expensive mistake is shipping a roadmap item that never had a written problem frame, success criteria, or post-launch review plan.

Common traps to watch:
- confusing backlog grooming with discovery
- publishing roadmaps without decision context
- tracking proxy metrics that never change planning

References that help correct the drift:
- SVPG article archive: svpg.com/articles/
Useful for strategy, product operating models, and decision quality.
- Opportunity solution tree visuals: producttalk.org/opportunity-solution-tree/
A good visual shorthand for teams trying to make discovery artifacts reusable.

This folio post is meant to be saved and revised. Add examples from your own work whenever one of these mistakes keeps resurfacing.