Find what deserves to exist.
Product purpose, customer discovery, market insight, strategy, priorities and evidence.
A suggested project / reading order
No books match the current filters.
Make the bookcase operational
Give one agent a useful job.
Give the organisation a way to learn.
Choose one product outcome or one team workflow. Prepare the books that make its context, ownership, permitted actions and acceptance clear. Use the build list to turn the framework into a starting implementation guide.
01 / Frame the work
Set the outcome and baseline.
Choose a real task: turning interviews into a decision brief, helping a customer finish a bounded job, or improving activation. Record how the work performs today.
02 / Prepare the minimum books
Agree context, authority and quality.
Give the task an owner, approved inputs, a work contract, tools, limits and representative acceptance cases. The suggested filenames are starting documents to create.
03 / Trial and review
Improve from accepted outcomes.
Compare quality, customer value, time, cost and review effort. Resolve failures and missing context before widening scope or granting more autonomy.
The book is the unit of design. Each book needs a purpose, scope, accountable owner, sources, approved version, review date, inputs, outputs, permitted actions, acceptance checks and escalation. A book can become a document, schema, playbook, dataset, workflow or enforced configuration.
How to set autonomy for a specific action
| Mode | Working arrangement | Example |
|---|---|---|
| Assist | The agent recommends. A person decides and acts. | Preparing alternatives for a product strategy decision. |
| Co-pilot | People and agents develop the work together. | Refining a PRD or prototype with the product trio. |
| Delegate | The agent performs bounded work; consequential release requires approval. | Preparing and verifying an implementation change before release. |
| Autonomous within limits | The agent executes permitted actions under enforced controls; people handle exceptions. | Running an approved evaluation pack on a scheduled configuration. |
Assign autonomy to an action and context. Review criteria, identity scopes, budgets and stop controls belong in the actual workflow and tool permissions.
Where the topics from your two course maps appear
| Source theme | Its place in the organisation |
|---|---|
| Product foundations and product sense | 01 Purpose & customer value; 02 Strategy & portfolio. |
| Strategy, roadmapping and competitive analysis | 02 Strategy & portfolio; 05 Discovery & customer evidence. |
| Customer discovery and customer intelligence | 05 Discovery; 09 Customer evidence and shared memory. |
| Product design, prototyping and PRDs | 06 Design & product specification; 07 Delivery. |
| Execution, delivery and product writing | 07 Delivery & lifecycle; 12 Results reviews. |
| Growth, user lifecycle, GTM and pricing | 08 Growth & monetisation. |
| Experiments and product analytics | 02 Metric contracts; 05 Behavioural evidence; 12 Experiments. |
| AI product strategy and building beyond the chatbot | 02 AI capability fit; 06 AI experience; 10 Customer-facing product agents. |
| Agent primitives, skills, memory, goals, loops and graphs | 09 Shared memory; 10 Agent roles & orchestration. |
| Research tools, prototypes, coding harnesses and team workspaces | 06 Prototyping; 10 Research and implementation agents; 11 Workspaces. |
| Context engineering, evaluations, LLM judges and observability | 06 Context contracts; 09 Context lifecycle; 12 Evaluation & reliability. |
| Company and market case studies | 02 Market dynamics; 05 A case library focused on transferable mechanisms. |
| Leadership and product organisation design | 03 Authority & accountability; 04 Team & operating model. |
| Careers, interviews and proof of work | 04 Hiring scorecards, work samples, capability development and coaching. |
Tool-heavy topics become capabilities and replaceable system roles. Named tools in search metadata are examples from the supplied maps; this edition does not assess their current features or recommend a vendor.
Inspiration, scope and attribution
Topic inspiration: the supplied images titled The Complete AI PM Course and The Complete Course to Product Management, credited to Aakash Gupta / Product Growth.
The bookshelf structure, operating documents, human and agent responsibilities, acceptance checks and project paths are an original proposed adaptation for this project. The underlying course articles were not reviewed. The maps informed topic coverage.
Scope extends to accessibility, permissions, operating economics, lifecycle ownership, recovery and organisational learning. The model applies to conventional products using agents internally and to products with agentic customer features.
Take the books into a real project.
Open books and add them to your build list. Export as Markdown when ready.