Use this category only when the content is materially about Product Management.

Definition: Product Management is the accountability for maximising product value by deciding what to build, why it matters, and how to prioritise work across customer needs, business goals, and technical feasibility.

Must have:

• Product vision, product strategy, or outcome goals used to guide product decisions.
• Prioritisation of opportunities, features, or Product Backlog items based on value rather than output volume.
• Evidence-based decision-making using metrics, customer feedback, discovery, or measurable outcomes.
• Balancing desirability, viability, and feasibility, including technical empathy or delivery constraints.
• Clear authority/accountability boundaries, such as Product Manager/Product Owner owning “what” and “why”.

Strong fit:

• Primary: Product Management is the main subject and at least two Must have items are discussed.
• Secondary: Product Management is a substantial supporting theme and at least one Must have item is discussed.

Weak fit:

• Tertiary: Product Management is mentioned or adjacent, but the content is mostly about Agile delivery, software development, marketing, sales, or project execution.
• Ignored: Product Management is absent, only implied, or supported only by generic discussion of products, customers, teams, or business value.

Exclude:

• Project Management, delivery management, Scrum Master duties, or general Agile process guidance.
• Product marketing, go-to-market, sales enablement, or brand positioning without product value prioritisation.
• UX research, customer support, or feedback collection without product decision-making or prioritisation.
• Engineering architecture, DevOps, or technical implementation unless tied to product feasibility trade-offs.
• Generic terms such as product, roadmap, stakeholder, customer needs, features, value, or collaboration are insufficient on their own.