> Markdown copy of [https://aimaturitymodels.com/functionmodels/pm/](https://aimaturitymodels.com/functionmodels/pm/), generated at build time: a rendering, not a source of truth. Map: [/functionmodels/llms.txt](/functionmodels/llms.txt). Site map: [/llms.txt](/llms.txt).

## Product Management Function Model

Product management turns market, user, and business inputs into product decisions and outcomes. A governed system of activities, capabilities, and tools — this is a function model, not a process nor a lifecycle — inputs to outputs.

### Function, Process, and Lifecycle

Most experienced product executives can feel when product management is working and when it's fragmented. It can be difficult to articulate why. The usual answers reach for process maturity or tooling — which is an overcomplication.

PMs are taught sprints, ceremonies, and cadences without knowing the layer beneath. They get the verbs without the nouns.

The product management function can be represented at three levels, and each answers a different question:

- **Function model:** flat and structural. What must exist: inputs, activities, capabilities, outputs. No sequence, no arrows. A trigger presumes a time axis, and this layer has none.
- **Process:** a linear path through part of the function. The function model is the dictionary; a process is a sentence built from it.
- **Lifecycle:** the function projected onto time, derived from the processes that form the flywheel of a practice.

Most organizations struggle to adopt lifecycles before they understand the function.

In short:

- **The function model:** is a flat, ontological form; what the function is and what it does.
- **Processes:** are linear renderings of portions of the function.
- **A lifecycle:** is an approximate rendering of the function in motion. That's what it looks like when it's running.

This page represents the first layer only. Nothing here is missing an arrow. Arrows belong to a different diagram, answering a different question.


### Inputs

- Organizational strategy
- Market targets
- Revenue requirements
- **Market intelligence:** Competitor data, Buyer intelligence, Customer/user insights, Analyst insights

### Product Management Function

**Activities** (What the PM does all day):

- Define Markets
- Requirements Management
- Prioritization & Tradeoffs
- Engineering Interface Cadence
- Executive Interface Cadence
- Organizational Evangelism
- Product Portfolio Alignment Cadence
- GTM Cadence
- Experimentation & Validation
- User/Customer/Analyst Meetings

**Capabilities** (What the PM is good at):

- **Market intimacy** — Customer/Buyer Engagement, User Intimacy, Market/Analyst Engagement. *Deep knowledge of markets, customers, users & analysts.*
- **Persona generation** — User Personas, Buyer Personas, Delivery & Support Personas. *Structured archetypes for effective PDLC and key stakeholder groups.*
- **Strategic Analysis** — *Beat competitors — cheaper, faster, higher quality.*
- **Requirements Articulation**
- **Executive Engagement** — *Where authority over portfolio, prioritization, roadmap, pricing & scope is maintained.*
- Pricing · Market positioning

**Enabling substrates:**

- **Tools:** RMS / ALM / Engineering Collaboration Tools, Document & Presentation Tools, Design & UI Tools, GTM & MarCom Tools, Analytics & Outcomes & Market Measurement Tools.
- **Governance:** Stage-gate reviews, OKR cadence, Compliance & risk review.
- **Resources:** PMs, Designers, Engineers, Data analysts, GTM stakeholders. *Resources execute the function, but do not define it.*
- **Standards:** Agile / SAFe / dual-track discovery, Data privacy, Accessibility.

### Outputs

- **Engineering & delivery** (What engineering needs to know what to build): Requirements, Prioritization, Release goals
- **GTM & market-facing** (What sales and the market need to price, position, and sell): Positioning & Pricing, Market messaging, Provisioning & Billing Plans, Buyer Personas & Battlecards
- **Operations** (What operations needs to keep customers happy and paying): Support materials & training, User feedback mechanism
- **Leadership & governance** (What leadership needs for cadence, fiduciary duty & alignment): Product strategy, Executive transparency