Skip to main content
  • Enterprise
  • Pricing
  • Book a demo

Product Management

How to set up product hierarchies (with examples)

17 Nov 202611 mins read
Tomas Prochazka
By Tomas Prochazka

Key takeaways

  • Organize complex portfolios: A product hierarchy classifies offerings by relative importance or inclusiveness to provide a holistic view of different products.

  • Break portfolios into six levels: The model connects a core product need through family, class, line, and type down to a purchasable product unit.

  • Use across physical and digital goods: Although this framework originated in the manufacturing industry, it also helps digital organizations align products with strategy and user needs.

  • Real-world product hierarchy examples: The guide breaks down Toyota (automotive manufacturing) from a customer's need to travel down to a specific Aygo SKU, and maps Google (digital products) from team productivity down to Google One.

  • Build and visualize in airfocus: Follow six steps—from anchoring in user needs to setting governance rules—and link parent-child items across airfocus workspaces.


Products rarely exist in isolation. Especially in growing businesses, products, experiences, and apps multiply. At scale, the picture can become quite chaotic. That’s why product teams should have a deep understanding of the different parts of their product mix and how they connect. 

The product hierarchy framework gives teams a more holistic view of the organization’s products, going beyond the product(s) to consider the who, what, when, and why behind everything that’s being worked on. The product hierarchy model has been used in the manufacturing and automotive industries for years, but it’s also applicable to digital products and services. 

In this article, we’ll explore how to set up product hierarchies and provide real-world examples.

Explore how airfocus
can support your team.

Book a demo

What is a product hierarchy 

A product hierarchy structures, organizes, and classifies a company’s products according to relative importance or inclusiveness. It allows teams to visualize the relationships and dependencies between products, from broad portfolios to individual items.

In a product hierarchy framework, products can be divided into groups across six levels, which we’ll outline in the following section.

What are the six levels of product hierarchy

Inline product hierarchy

The product hierarchy framework uses six levels to organize products in an order that makes sense for the business and its end users. To describe the product hierarchy, we’ll illustrate each of the six levels with an example from Toyota. 

Product need

The product need describes the problem, gap, or necessity that motivates users to use a certain product. It essentially answers the question, “Why are we building this product?” Understanding users’ needs is a key step for product teams to avoid investing time and resources into building the wrong thing. The key components of a product need include:

  • Core need: The fundamental problem the user needs to solve

  • Functional requirements: The features, capabilities, and functionalities a product must have in order to solve the need

  • Context of use: The real-world environment in which the user experiences the need

Example: Toyota’s cars are developed to fulfill the customer’s need to travel. 

Product family

The product family represents a group of different problems, targeting different customer needs, but all made by the same company and under the same brand, and using the same core technology.

Example: In order to travel, Toyota’s users could choose to cycle, fly, walk, or catch a train. But Toyota chose cars as their product family. 

Product class

The product class is a broad, industry-wide group of products within a product family. It spans all competing brands in a specific market. Products are grouped into a class by similar features, attributes, and intended uses. Here are a two key characteristics of a product class:

  • Shared attributes: Same-class products typically share a standard set of specifications that make them easy to compare and catalog (e.g., size, material, technical parameters)

  • Interchangeability: Products of the same class closely compete with each other, since answer the same customer need. They should therefore be direct substitutes of each other.

Example: Within the broader automotive family, SUVs are a distinct product class. This places Toyota’s SUVs alongside direct substitutes from competing brands, such as the Honda or Nissan SUVs. Regardless of the manufacturer, all vehicles in this class share standard attributes: higher ground clearance, spacious cargo capacity, and optional all-wheel drive.

Product line

A product line is a group of closely related products within a product class, sold by a single company. They are grouped together by similar characteristics, such as function, target customers, or price range.

  • Shared core function: Items perform a similar primary purpose or solve the same basic problem for the user

  • Unified branding: Products share the same brand name, visual identity, or marketing message

  • Common target audience: Offerings are all designed for the same general customer segment

  • Tiered pricing structure: Items are often staggered across different price points (such as entry-level, mid-range, and premium) to capture varying budgets

  • Shared distribution and production: Products typically move through the same retail channels and rely on overlapping manufacturing or supply chain resources

Example: Within the Toyota SUV family, there are different product lines: Toyota Sequoia, Toyota Highlander, Toyota RAV4, and more.

Product type

A product type is a sub-category of a product line. Items in a product type share a distinct form, format, or specialized configuration. While a product line groups offerings by their broad function and target market, product types break that line down into more granular variations to match specific user preferences, technical requirements, or contexts of use. Here are the key characteristics of a product type:

  • Shared form or format: Items within a product type take the same structural shape, delivery method, or design architecture (e.g., liquid, powder, or pod formats in a laundry detergent line)

  • Specialized use case: Each type is tailored to a specific application or environment within the product line’s broader purpose (e.g., road running shoes versus trail running shoes)

  • Differentiated configurations: Product types are separated from one another by distinct features, ingredients, or technical specs rather than just price tier or branding

  • Direct bridge to individual items: A product type acts as the final grouping layer above individual items or SKUs, which only differ by minor attributes like color, size, or packaging volume

Example: The Toyota Aygo product line includes various product types: Aygo x, Toyota Aygo x-play, Toyota Aygo x-press, and so on. While all of these models share the same compact city-car form and serve the exact same use case (agile urban commuting and easy parking), each type offers a distinct configuration of interior tech, exterior styling, and feature sets.

Product unit

The product unit, also known as the stock-keeping unit (SKU), is the final, most granular level of the product hierarchy, representing a single, distinct version of a product within a product type. It is the exact, purchasable item defined by specific attributes, such as color, size, packaging, or price, that cannot be broken down into any smaller categories. Here are the key characteristics of a product unit:

  • Unique identification: Each unit is assigned its own distinct SKU, barcode, or catalog code for inventory, manufacturing, and sales tracking

  • Specific attributes: Units within the same product type are differentiated by concrete variations like color, finish, size, or minor optional add-ons

  • Fixed price point: Unlike a product line that spans a broad price range, an individual product unit carries a specific, final retail price

  • Direct point of purchase: It is the exact, tangible item a customer selects, orders, and buys

Example: Within the Toyota Aygo x-play product type, a specific product unit would be a Toyota Aygo x-play 1.0 VVT-i with a manual transmission in red. While it shares the exact same features and configuration as every other Aygo x-play, this specific color and drivetrain combination represents a single, distinct SKU that a customer selects and purchases at the dealership.

Applying a product hierarchy to digital products: Google’s example

While the product hierarchy framework originated in manufacturing, it serves digital products just as well, especially in enterprise product organizations, where multiple products are at play. 

Here, the product hierarchy can help organize and rationalize a product range: Does that new product idea really fit with your overall objectives, or is it more of a nice-to-have? It also provides a clear idea of how each of your products fits into the overall strategy and how each one addresses a customer’s need. Additionally, this framework informs marketing campaigns and external communications.

Google is a great example of a large digital organization with many products under its wing. 

  • Product need: Team productivity. The Google Suite was created to support professional teams and to help them collaborate better.

  • Product family: B2B app. The wider context of this need means that teams could also use other applications, as well as offline solutions such as flip charts, diaries, etc. Google Suite’s chosen product family is B2B apps.

  • Product class: B2B productivity tools. Within the B2B app family, Google offers several B2B apps, including a scheduling app, a document-sharing app, a spreadsheet app, and more.

  • Product line: Google Suite. The market-facing name given to this class of products is Google Suite.

  • Product type: Google storage and sharing. Within the Google Suite product line, there are several product types, including Google Drive for document storage and sharing.

  • Product unit: Google One. Google One is the paid version of Google’s storage and file sharing product type. Customers can also opt for a different product unit (e.g., a free version with lower storage space) depending on the size and scope of their professional team.

When we break Google Suite down using the product hierarchy, it’s clear how Google has worked to satisfy the user need right down to the resulting single product unit. 

Having this framework in place gives teams and managers something to refer to at all stages of product development, ensuring that the basic product need is consistently met. 

Six steps to develop a product hierarchy 

Building a product hierarchy requires balancing how your business operates internally with how customers naturally evaluate and buy your solutions. Whether you are structuring a growing SaaS ecosystem or a catalog of physical goods, follow these six steps to create a clear, scalable taxonomy:

1. Anchor the top levels in user needs and market reality

Start from the outside in before organizing your own catalog. Define the core product need you are solving, identify the broader product family, and pinpoint the exact product class you compete in.

For a digital product team, this means, for example, clarifying whether you operate in the broad "team collaboration" space (family) or specifically in "asynchronous video messaging" (class). For physical goods, it means establishing the exact industry category your product occupies alongside direct substitutes.

2. Group your offerings into cohesive product lines

Audit your current or planned portfolio and cluster offerings that share a primary function, target audience, or core value proposition into distinct product lines. Avoid creating a new line just because a feature set is different; a separate line is usually warranted only when a product serves a distinct user persona or solves a fundamentally different workflow.

For instance, a software company might separate its core analytics platform from its standalone customer data pipeline, much like an automotive manufacturer separates compact city cars from commercial vans.

3. Break lines down into product types based on form or specialization

Within each product line, map out your product types by identifying variations in delivery format, technical architecture, or specialized use cases.

Digital product teams often differentiate product types by platform (such as a web app, mobile app, desktop client, or public API) or by tailored editions built for specific verticals (such as a CRM configured for healthcare versus e-commerce). In manufacturing, this step separates items by physical form, trim level, or formulation—such as liquid, powder, or pod detergent.

4. Define the exact purchasable product units

At the bottom of the hierarchy, specify every individual product unit: the concrete configuration a customer actually selects at checkout.

In digital products, units typically correspond to specific subscription tiers (Free, Pro, Enterprise), billing cadences (monthly versus annual), or paid add-on modules. In physical retail and manufacturing, these are your individual SKUs defined by exact attributes like color, size, storage capacity, or packaging volume.

5. Align internal systems and test against user mental models

A product hierarchy only works if product, engineering, marketing, sales, and finance speak the same language. Map your hierarchy directly to your internal infrastructure—such as subscription billing tools, product analytics, and ERP or inventory databases—so reporting stays consistent across departments. Just as importantly, validate the structure with real users through pricing-page reviews or card-sorting exercises to confirm customers can easily compare options without friction.

6. Establish governance rules for future scaling

As teams ship new features and launch new offerings, hierarchies can quickly become bloated. Set clear criteria for how future releases fit into the tree: Decide upfront what qualifies as an update to an existing unit, what merits a new product type, and when a new capability is distinct enough to justify launching an entirely new product line.

A well-structured product hierarchy is never completely static. Revisiting and refining these levels as your user base evolves and your portfolio expands ensures your team can scale cleanly without fragmenting the customer experience.

How to set product hierarchies in airfocus: A step-by-step guide

Within airfocus, a product hierarchy lets you manage items through each level of the product development process.

You decide how items relate to each other across your workspaces. Link parent and child items, choose how you want everything to map together, and plan every level of your product development process. 

Let's take a look at how product hierarchy works in airfocus. If you haven't yet chosen an item type for your existing workspace, go to the General tab under Workspace settings and define the item type that will exist in that workspace.

airfocus portfolio management CTA

Unify all your product hierarchy with airfocus Portfoliio management. Roll each product family, class, line, and unit into a single, high-level view.

How to set product hierarchies in airfocus: A step-by-step guide

Within airfocus, a product hierarchy lets you manage items through each level of the product development process.

You decide how items relate to each other across your workspaces. Link parent and child items, choose how you want everything to map together, and plan every level of your product development process. 

Let's take a look at how product hierarchy works in airfocus. If you haven't yet chosen an item type for your existing workspace, go to the General tab under Workspace settings and define the item type that will exist in that workspace.

Product Hierarchy airfocus
Product Hierarchy airfocus

You can find out more about each item type and its use here.

You do not need to define an item type to use hierarchy, but it is advisable.

Product Hierarchy airfocus

A common hierarchy and item type setup might look like this:

A parent workspace sits above another workspace—for example, initiatives on your roadmap. A child workspace sits below another workspace—for example, opportunities on your product backlog.

A workspace can be both a parent and a child at the same time if it sits between two workspaces, connecting your hierarchy across multiple levels.

In this example, we are setting up our product hierarchy to link initiatives on our roadmaps, opportunities on our backlog, and tasks on our task list. With the item types defined, we can select our parent workspace (portfolio roadmap) from the current workspace where opportunities exist.

Product Hierarchy airfocus

After enabling "Allow hierarchy relations within this workspace", you can set up parent-child relationships within the same workspace. Bear in mind, however, that the recommended setup is to keep hierarchy levels in separate workspaces.

Product Hierarchy

Once your hierarchy is set up, you can add and remove parent and child items from the item panel. If you have access to all workspaces, you can access the parent or child items from the item panel. This opens the linked item in a new tab. 

Product Hierarchy

If multiple parent or child workspaces exist above or below the current item, or if they are linked to items in workspaces without item types defined, they will be displayed as "parents" and "children" on the item panel.

Visualizing product hierarchy in airfocus

To view all connected child items, switch on the "Child items" toggle within Display options:

On the board view

Board view

On the timeline view

When an item has child or parent items, the hierarchy icon will be displayed. Hover over them to reveal details.

Timeline view

On the table view

Product Hierarchy airfocus

Parent items as swimlanes

You can even set your parent items as swimlanes of your views in the display options (temporary solution) or in the default display options (default setup for your view).

Product Hierarchy airfocus

airfocus is used by thousands of teams that use the flexible product management platform to build products, services, and projects that succeed.

Ready to build your product hierarchy?

As we’ve seen in this guide, the product hierarchy model can bring big benefits to product teams.

Not only does it provide a framework for remembering the basic need to build the perfect product portfolio, but it can also enable product managers to boost organizational workflows and improve collaboration between teams. In an industry as ever-changing as product management, it’s comforting to have an exercise as tried-and-tested as the product hierarchy.

Ready to build and visualize your product hierarchy in airfocus?

Explore how airfocus
can support your team.

Book a demo

Share what you learned or ask questions in the community

Tomas Prochazka

Content Marketing Manager @ Usersnap
Tomas is a passionate content strategist with strong knowledge of SEO principles and organic growth models. Over the last years he has been working in various lead content and SEO roles for European companies in the B2B SaaS industry, as currently he leads all content activities at Usersnap.
40 Articles
eBook
The AI maturity gap:
Are product teams keeping up?
Read now

Read also

Product Discovery 11 Nov 2026
How to facilitate a product discovery workshop: Step-by-step guide and template
Why do fast-moving teams still build the wrong features? Align stakeholders on real user problems before coding with a step-by-step product discovery workshop and template.
By Francisca Berger Cabral
Agile 10 Nov 2026
Product backlog vs. sprint backlog: What are the differences?
Why do Agile sprints stall despite endless planning? Discover how balancing your product backlog vs. sprint backlog bridges long-term vision with daily delivery to keep teams shipping value.
By Vishal Chaudhary
Product Management 29 Oct 2026
How to leverage SaaS KPIs for growth
Aspirational OKRs fail when disconnected from reality. Discover how tracking core SaaS KPIs drives sustainable growth, cures strategic drift, and turns raw product data into scalable revenue.
By Vishal Chaudhary
Product Strategy 21 Oct 2026
Product vision vs. company mission: What are the differences, and how to align them
Why do teams pull in opposite directions? Confusing company mission with product vision breeds misalignment. Discover the key differences and how to align them.
By Inês Liberato

Explore how airfocus
can support your team

Book a demo

Top rated
on major platforms
airfocus is where teams build great products. Welcome home 💙

Company

  • Terms of service
  • Privacy
  • Legal
  • Cookie policy
  • Your privacy choices
  • DE
  • FR
All rights reserved. contact@airfocus.com