Product Management

Create the smallest complete product record that explains who needs the product, why it exists, how it behaves, what constrains it, how success is measured, where it ships, and what evidence supports it. Read the focused reference that matches the task:

• Product catalog for scope, taxonomy, hierarchy, evidence, metadata, and a worked example
• Feature specifications for reusable rules, states, permissions, quality requirements, and analytics contracts
• Question model for answer coherence, uncertainty, relationships, time, product claims, and completeness dimensions
• Platform design for product-platform capabilities, control-plane scope, architecture, and progressive construction

Core Model

Keep these layers distinct and linked:

• Product truth: durable capabilities, features, journeys, rules, permissions, data, interfaces, quality requirements, and analytics.
• Change intent: initiatives, requirements, stories, tasks, releases, flags, and rollout plans.
• Evidence and operations: research, feedback, metrics, experiments, decisions, service objectives, incidents, and support procedures.

A capability is a durable customer or business ability. A feature is a product mechanism that provides that ability. A story or task is a planned slice of change. Never use one object for all three.