Product Management

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.

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 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.

The tools that keep proving useful usually support research repositories and interview note systems, roadmap and prioritization tooling, and product analytics and experiment review without making the underlying work harder to understand. When you bookmark something, write down why it earned the slot.

Three sources worth opening side by side:
- Continuous discovery overview: producttalk.org/continuous-discovery/
A durable foundation for teams trying to make research continuous instead of episodic.
- 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.
- Lenny's Podcast video archive: youtube.com/@Lennyspodcast/videos
Product conversations that tend to stay practical instead of drifting into slogans.