Foundations of the Craft
The role, the trade-offs, product sense, and the four big risks the job manages.
Before you can grow a competency, you have to know what the job is. This domain is the bedrock the twelve competencies sit on. It holds the shared definitions, distinctions, and mental models I assume you already carry by the time we talk about Feature Specification or Product Vision and Roadmapping. Skip these and the competency notes will read like a checklist. Read these and they read like a craft.
I built The PM Competency Model as the skeleton of this Atlas, and a skeleton needs ground to stand on. These thirteen notes are that ground: what a PM actually does, how the role differs from the ones it gets confused with, the trade-offs at its core, the kinds of teams and orgs PMs work inside, and the judgment that separates a good PM from a great one.
#My one-paragraph thesis
Product management is the discipline of being accountable for the outcome of a product without owning the people or the code that produce it. You sit in the overlap of product, design, and engineering (The Product, Design, and Engineering Venn), and your core act is making and defending trade-offs across the four big risks. You do all of this through influence rather than authority, which is why the whole back half of this Atlas is about people. Everything else is detail.
#The map of this domain
| Note | What it gives you |
|---|---|
| The Product Manager Role | What a PM actually does day-to-day and quarter-to-quarter, accountable for outcomes rather than output. |
| Product Manager vs Adjacent Roles | PM vs Product Owner vs Product Marketing vs Project Manager. The distinctions people get wrong. |
| The Product, Design, and Engineering Venn | The classic intersection, and why the PM owns the overlap and the trade-offs. |
| Understanding Trade-offs | The PM's core act: value, usability, feasibility, and viability held in tension. |
| Product Teams vs Feature Teams | Cagan's distinction: empowered outcome teams vs output-driven feature factories. |
| The Product Organization Matrix | Outcome vs Feature teams crossed with Owner vs Facilitator. Where your specific job lives. |
| Types of Product Managers | Growth, platform, B2B vs B2C, 0-to-1, AI PM. The role is not one job. |
| The T-Shaped PM and Knowing Your Shape | Spiky, not well-rounded. Build teams that cover your gaps. |
| Product Management Across Company Stages | How the job changes from startup to scaleup to enterprise. |
| Character, Competency, and Craft | The hard-to-teach to easy-to-teach spectrum, and why character comes first. |
| Product Sense and Judgment | Taste, trainable judgment, being right more often than chance. |
| The Four Big Product Risks | Value, usability, feasibility, viability, and who owns each. |
#How to read it
If you're new to the discipline, read top to bottom. The order is deliberate. If you're experienced, three notes earn your time even if you skip the rest: The Four Big Product Risks (the cleanest model of what you're actually managing), The T-Shaped PM and Knowing Your Shape (the honest version of "what am I good at"), and Character, Competency, and Craft (why your best hire might be the one who interviews worst on frameworks).
That product management is a single, well-defined job you can master with a certification. It isn't. It's a shape of accountability that bends to the company, the stage, the team type, and the product. The foundations hold steady. Everything built on them moves.
#Continue Reading
- The PM Competency Model for the four areas and twelve competencies these foundations support.
- What Is Product Management for my one-screen definition of the discipline itself.
- The Four Big Product Risks if you read only one note in this domain.
- The Product Career Ladder for how these foundations scale from APM to CPO.
- How to Use This Knowledge Base for the reading paths through the whole Atlas.