When creating a new workspace, you can define the item type that will exist in that workspace. With different workspaces containing different item types, you can then connect them together through Product Hierarchy.

This will allow you to connect a group of workspaces that are interconnected through parent and child items, with each workspace containing its own set of unique custom fields, views, and even prioritization criteria.

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

A parent workspace is that which sits above another workspace. For example, initiatives on your roadmap.

A child workspace is that which 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 they sit in the middle of two workspaces, connecting your hierarchy across multiple levels.

Below is a list of available item types in airfocus.

Product

Generally, products would be represented and managed as a whole in workspaces, or through a group of interconnected workspaces. However, if you are managing ideas for new products to build, you can select the item type 'product.'

Initiative

An initiative is a project your team is undertaking and generally sits at the top of your product hierarchy as a parent item. Initiatives can be written as outcomes, experiments, or features once you have defined a solution.

Initiatives group a set of opportunities and stories together so you can understand what and why you are working on things and will link back to a set of objectives or goals to achieve.

Project

If your team is not familiar with the term "initiative", you can also just use the term project. Like initiatives, they group together other items and sit at the top of your product hierarchy as a parent item.

Feature

A feature is an aspect of your product that aims to solve a problem.

In airfocus, features can be parent or child items and sit in the middle of your hierarchy:

  • A parent item if expressed as a potential initiative or project (building a feature in order to solve a specific problem.)

  • A child item in your product backlog (as a potential solution to a problem.)

Opportunity

An opportunity is a way to express items in your product backlog.

By naming them opportunities, you open your team up to discovering how a potential problem might be solved, or if it's even worth solving in the first place.

In airfocus, opportunities can be parent or child items and sit in the middle of your hierarchy.

  • They can be parent items to stories.

  • They can be child items to initiatives or projects.

Idea

An idea (like an opportunity) is a way to express items in your product backlog.

By naming them ideas, you open your team up to discovering how a potential problem might be solved, or if it's even worth solving in the first place.

As with opportunities, they can be both parent and child items and sit in the middle of your hierarchy.

Epic

An epic is an item in your product backlog that can be broken down into a number of smaller stories. It is a term largely used in Agile.

Opportunities, ideas, and experiments all often become epics once they reach your development team as a more structured piece of work with specific requirements. If you’d like to keep terminology similar to that of your development team, you can use this item type to define your product backlog.

In airfocus, epics can be parent or child items and sit in the middle of your hierarchy.

  • They can be parent items to stories.

  • They can be child items to initiatives or projects.

Experiment

An experiment is a way to test if an idea or opportunity is viable, and allows your team to understand if you should proceed with solving the problem.

Experiments can be both parent and child items:

  • If using experiments as a way to express discovery on a roadmap item as a purely experiment-driven roadmap, then you can select this item type as a parent item.

  • If using experiments as a way to express discovery on your backlog, then you can select this item type as a child item.

Story

User stories are an Agile technique of defining product functionality and requirements. They focus on telling a story for an action a user will take and what the expectation is when successful. They are expressed as child items within an airfocus Product Hierarchy.

Task

A task is a specific action your team will undertake as part of a larger piece of work.

Tasks can be managed individually in a workspace, or as a child item of an initiative, opportunity, or story in your airfocus Product Hierarchy.

Feedback

Feedback can come from your team, stakeholders, or customers. They're a way to understand potential problems to solve and help support your product discovery work.

In airfocus, feedback sits outside of the product hierarchy as you can connect them to items via the Insights app. Setting things up this way provides two benefits:

  • Understand the impact of your feedback against your product items.

  • Allows you to use the Insights score as a criteria in your prioritization framework.

Did this answer your question?