A major functional area within a product. The subdivision that typically maps to a team or squad.
A product area is the grouping layer that sits between an organisation and its individual products: a domain or pillar that a related set of products, and the teams behind them, belong to. It exists because a flat list of forty products tells you nothing about how the company is actually organised, and a single org chart tells you nothing about what the products do. The area carries the shape that connects the two.
Product area is an organisational convention that hardened as companies scaled past the point where one product manager and one roadmapRoadmapProduct SpecificationA strategic plan of features and milestonesView reference → could hold everything. It draws on the long line of work on product portfolioPortfolioPortfolioA grouping of products by strategic axisView reference → structure and on the team-topology thinking popularised by Team Topologies (Skelton and Pais, 2019), where stream-aligned teams own a slice of the product and the boundaries between slices are designed deliberately. The area is the structural home for one of those slices when the slice is bigger than a single product.
The thinking settled on nesting. Early models treated the hierarchy as flat (organisation, then products), which broke as soon as a company had a "Payments" group spanning checkout, invoicing, and payouts. Modern practice allows areas to contain other areas, so the hierarchy can be as deep as the business is, while each level still names a coherent domain a team can reason about. The distinction from portfolio matters here: portfolios tend to be investment-and-reporting groupings, while areas tend to be ownership-and-domain groupings, and the two needNeedUserA user need, pain, desire, or constraintView reference → not align.
A company with eighteen products is drowning in a flat backlog. It introduces four areas: Payments, Identity, Growth, and Platform. Payments contains three products and nests a sub-area, RiskRiskComplianceA risk to the product or businessView reference →, that holds two more. Each area has a directly responsible lead, and roadmap reviews now happen per area rather than per product, so the checkout team and the payouts team finally see the dependencyDependencyTeam & OrganisationA cross-team or system dependencyView reference → between them that the flat list hid. When a new compliance requirementCompliance RequirementComplianceA compliance requirementView reference → lands, leadership routes it to one area lead, and no longer pages eighteen product owners. The areas did not add work; they made the existing structure legible, and they gave dependencies a place to surface.
In the Unified Product Graph, a product area is a portfolio-region node that an organizationorganization_organised_into_product_areaproduct_area_contains_productproduct_area_contains_product_areaportfolioteam
Type-specific fields on BaseNode
strategic_prioritystringStrategic priority assigned to this area
descriptionstringNarrative description of what this area covers
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
6 edge types connected to this entity.
product_categorised_in_product_areaorganization_organised_into_product_areaproduct_area_contains_product_areaproduct_area_contains_productproduct_area_contains_product_areaproduct_area_contains_featureProduct Area is the organisational axis. It groups products by team or ownership structure, independently of strategic theme.
In a portfolio document, Product Area entities can participate in cross-product edges, the typed relationships that link entities across different products. These edges are declared in UPGPortfolioDocument.cross_edges.
shares_personashares_competitorshares_metricdepends_on_productcannibalisessucceeds{product_id}/{node_id}. They are declared in the cross_edges array of a UPGPortfolioDocument, not inside individual product graphs. See Portfolio for the full model.1 framework use this entity type.