Read Me First
Choose a starting point and build your Product 360.
This handbook covers the full product job: customers, strategy, economics, delivery, launches, operations and retirement. Use it to build a Product 360 you can keep current.
What Product 360 means
A Product 360 connects the decisions, evidence and working documents that explain your product. It covers nine dimensions: customer, strategy, business, build, measure, go-to-market, operate, lifecycle and leadership. AI affects the product and the work across all nine.
Chapter 00 defines the model. Each dimension needs an answer, a source, an owner and a review date. Gaps tell you where to work first.
Who this book is for
The primary reader is a Senior to Principal product manager in a B2B, enterprise or platform business. On-ramp boxes explain assumed knowledge. For product leaders boxes address portfolio, organization and governance decisions.
The examples emphasize enterprise constraints: buying groups, long sales cycles, partner channels, compliance reviews and products that last a decade. Consumer examples clarify concepts where useful.
How the book is organized
- Part I, Product Management: hypothesis, personas, vision, goals, strategy, prototyping, analytics and engineering.
- Part II, Technical Product Management: technical risk, growth and retention analysis, consumer insight, delivery methods and value-based pricing.
- Part III, Business and Market Strategy: market sizing, business cases, platforms, pricing and defensibility.
- Part IV, Data-Driven Decisions: decision questions, data sources, reports and verified AI-assisted analysis.
- Part V, Innovation: strategy, experiments, innovation tools and scaling.
- Part VI, Go-to-Market: positioning, offers, launches, events, enablement and customer success.
- Part VII, Product Operations and Lifecycle: operating cadence, governance, reviews and retirement.
- Part VIII, AI-Era Product Management: AI products, AI-assisted work and responsible AI.
- Part IX, Influence and Leadership: writing, presenting and stakeholder management.
- Part X, Capstone: a 30/60/90-day plan to build your own Product 360.
Each chapter explains the concepts, gives a method, applies the AI lens and works through the Beacon case. Templates, prompts and checklists turn the teaching into working tools. The final chapter brief gives the background, idea in brief and practical takeaways.
The running case: Beacon
Beacon is a fictional AI agent platform from Northlight Systems. It helps IT operations and SRE teams detect, diagnose and resolve incidents. It began as an alert-correlation feature and now supports agentic diagnosis and supervised remediation. You are its newly appointed Principal PM.
The case connects buying groups, platform strategy, inference costs, pricing, launches, legacy migration and AI risk. Beacon, Northlight and all their numbers are invented.
Conventions
Key idea boxes highlight a principle. The AI lens explains AI implications. Beacon case boxes work through the example. Anti-pattern boxes describe common failures.
Prompts state the goal, inputs and output checks. Replace [square brackets] with your context. Use approved tools for confidential data and check the results before acting. Appendix B collects the prompts.
Templates use Markdown and work in common document tools. Appendix A collects them with download links.
Tools and vendors illustrate categories. Named examples reflect late 2026. Check current capabilities before choosing a tool.
Start with your product’s gaps
- Read Chapter 00 for the model, artifact stack and cadence.
- Use Appendix C to score your product. Choose the two weakest dimensions.
- Read those chapters and build the artifacts your decisions require.
- Use the Capstone’s 30/60/90-day plan to address the remaining gaps.
- Run the cadence in Chapter 28 to keep the Product 360 current.
For a shorter read, use the Concise edition. It collects the same chapter briefs into a printable companion, one page per chapter.