An introduction to Product Systems

In the dynamic landscape of Product and Product Management, new challenges continuously emerge. The environment is increasingly fast-paced, with products not only growing in size but also in complexity.

This growth brings a complex web of interconnected dimensions, encompassing outcomes, metrics, insights, opportunities, designs, user experiences, implementations, collaborations, dependencies, and more.

It becomes increasingly difficult to maintain a comprehensive representation of these multifaceted dimensions across all levels, from the overarching macro perspective down to the intricate micro details.

At OpenClassrooms, we are exploring the Product System concept, a systemic and holistic approach that views a product not as an isolated entity, but as a dynamic network of interconnected components and layers.

A Product System is a holistic representation of a product, gradually revealing its components in a layered structure where every part is intrinsically linked to the whole, forming a unified, systemic portrayal.

Rather than viewing a product as an isolated entity, a Product System perceives it as a network of interconnected components, levels, and dimensions.

A Product System not only captures the product’s current state but also its potential future paths, thereby generating a dynamic representation that continually evolves over time.

The objectives of a Product System are:

• To connect the macro to the micro, aligning the mission, the vision and the strategy with the detailed implementation.
• To link various product dimensions, like user outcomes, metrics, business outcomes, capabilities, and timelines.
• To serve as an effective communication tool, delivering the right information, at the right level of detail and complexity, to the appropriate individuals, at the optimal time.
• To represent the product’s lifecycle, mapping out what exists, what’s on the horizon, and the long-term vision.
• To stand as a single source of truth, compiling all essential information in one place.
• To collect and integrate valuable user, market and data insights.

From General to Specific: The Hierarchical Tree Structure

A product can be envisaged as a hierarchical collection of elements, spanning from the most general to the minutest specifics. From broad to detailed.

This tree-like structure forms a cornerstone of product systems, serving several fundamental purposes:

• It outlines a layered structure for the products.
• It determines the granularity and the scope of a particular product segment.
• It interconnects various elements.
• It provides a navigation mechanism through the product elements.

Example of an ecommerce Product Tree

The granularity of the elements and the depths of this tree may vary based on the type and the size of product scope.

Pattern of Product Dimensions — The leaves

There’s a multitude of dimensions that can be used to describe a product, and the nature of these dimensions could be applied to each element. Some of these dimensions include:

• The Mission / Vision / Strategy direction
• The Outcomes
  - User / Product Outcomes
  - Traction Metrics
  - Business Outcomes
• The Experience overview and the child elements
• The Plan (Roadmap, Release Plans)
• The Insights (User, Market, Data)

A core principle of the product system is to establish a generic pattern for these dimensions that can be applied to each element within the hierarchical tree.

Additional dimensions that could potentially be incorporated include:

• Market Segment
• Priorities
• Quality Status
• Teams
• Owner
• Stakeholders
• Etc.

Patterns can vary by element. Some aspects, like ‘Market Insight,’ may be less relevant at lower levels. Formats also differ, with ‘Roadmaps’ at the top and ‘Release Plans’ lower down. This adaptability ensures that each component is finely tuned to its respective level.

Combining the scale and the Product Dimensions

The keystone of the product system concept is the intertwining of scale and the dimensions pattern. For each dimension, the definition and granularity adjust to the breadth and granularity of the tree layer, moving from general and broad to specific and detailed.

For instance, at the top of the tree, which represents the overall product, user outcomes will be broad and loosely defined, providing a general direction of the overall value we aim to deliver to customers. However, as we move down the tree, closer to individual user stories, these outcomes become more specific, detailing precise user goals.

The same principle applies to the plan dimension. At the top of the tree, it could encapsulate a broad vision with a long-term timeframe. In contrast, at the bottom, it might correspond to a specific release plan with a shorter timeframe.

This concept can also be related to people managing product elements: it ranges from the entire product team at the top, to stream-aligned teams in the middle, and further down to specific individuals.

The Product System — The fusion of the tree and the dimensions patterns

Consequently, the product system embodies a Hierarchical Tree Structure that encapsulates all product elements. Each element is defined by a pattern of product dimensions, with the granularity of these dimensions flexing to align with the corresponding layer of the tree.

First Takeaways

We began the implementation of our Product System in the closing months of 2022. To date, we’ve navigated through the upper tiers and have also made progress into some deeper layers. However, this marks merely the start of our journey.

Our primary goals were to create a unified place with a simple standard Product Representation, to facilitate easy access to information and align our teams from broad vision to everyday tasks. The product system has been effectively serving these purposes. We are increasingly incorporating it into our communication as a reliable source of truth, and the feedback so far has been positive. It has also become an efficient hub for insights, tying together the insights from both the User Research, Product Marketing and Data teams.

But of course, there’s no magical solution. We’ve faced challenges along the way. We’ve sometimes wrestled with determining the right granularity. Certain branches demanded more effort, not necessarily to describe within the product system, but because those elements were not clearly defined or incomplete. This underlines a key benefit: the product system reinforces best practices at every level for each element. Yet, like all systems, the Product System demands a certain degree of rigor and diligence.

I suppose some Product organizations might encounter hurdles when implementing a Product System. It may not be a one-size-fits-all solution for every product, methodology, or mindset. Furthermore, its success is intimately connected to the organization’s structure and the implications of Conway’s law.

However, we firmly believe that the benefits far outstrip these challenges. We’re convinced of its value and will continue to invest increasingly in it.

Stay tuned, as we’ll be sharing more about Product Systems soon!

Thanks to the PXT teams and all the individuals who contributed their valuable insights through reviewing this article.