A field guide, not a hall of fame.

What “comprehensive” means

There is no canonical boundary around product management frameworks. The catalog therefore includes widely used frameworks alongside methods, canvases, processes, metric systems, principles, and mental models. Every entry carries a visible type so inclusion does not imply equivalence.

How lessons earn “complete” status

A complete lesson must explain origin, purpose, vocabulary, application, a realistic worked example, a labeled case, company adaptations, an interaction or exercise, a template, limitations, failure modes, alternatives, questions, a knowledge check, and sources. Planned entries remain catalog records; they are not presented as finished lessons.

How evidence is handled

Primary and authoritative sources are preferred. A named company is said to have used a framework only when a reliable source supports that claim. Public material can establish chronology or reported practice but rarely proves that one framework caused an outcome.

How to disagree with a framework

Use the limitation sections. A framework is useful when it improves the quality or speed of a decision relative to the cost and distortion it introduces. If a tool hides uncertainty, rewards gaming, or forces the wrong unit of analysis, adapt it or choose another.

Privacy and local state

Bookmarks, notes, theme choice, progress, and path completion use browser local storage. No information leaves the browser, and the core content remains available without JavaScript.

Project status

Phase 1 publishes ten representative lessons and the complete extensible catalog. Remaining batches are listed in the project plan. The JSON catalog and generator are deliberately inspectable.