DOES EVERY PRODUCT EARN ITS PLACE?

How product architecture helps brands create meaningful choices, prevent assortment cannibalization, and build collections around what their customers actually need.

A strong collection isn’t defined by how many good products a brand can design. It is defined by how well those products work together.

As an assortment grows, it becomes easy to evaluate products individually. A jacket is good. A new sweater answers a customer request. Another version of a successful pant seems like a natural extension. Each decision can make sense on its own, yet the collection can become increasingly difficult to navigate. Products begin competing for the same customer, price points overlap, and the distinctions between them become harder to articulate.

This is where product architecture becomes essential.

At The Anecdote, one of the tools we use to build that architecture is a simple product chart. We place the assortment across two axes to understand where products sit in relation to one another, where the collection is becoming crowded, and where meaningful opportunities still exist.

The axes are customized for each brand, but the thinking is consistent. One is consumer-driven, looking at how the customer will actually use and wear the product. The other is merchandising-driven, looking at how the product functions within the business, whether that means good, better, best, entry, core, or elevated.

The chart forces a useful question: What job is each product doing, and is that job meaningfully different from the products around it?

A Product Needs a Reason to Be There

Consider a customer looking for a jacket. A brand offers three options: one zips, one buttons and has a hood, and one has secure pockets.

On paper, there is variety, but variety alone is not a strategy. If the customer cannot understand why she would choose one over another, the brand may have simply created three products competing for the same sale.

Now consider those same jackets through the lens of customer need. One is a lightweight layer designed to be worn over a sweater. Another is a weather-resistant option for transitional conditions. The third is designed for longer days outside, with greater protection and more functional details.

The differences now have meaning. The customer isn’t choosing between three jackets; they are choosing the jacket that best fits the job they need it to do.

This is the fundamental role of product architecture: creating meaningful distinctions within the collection so that products complement rather than cannibalize one another.

More Products Don’t Necessarily Create More Choice

One of the easiest traps for a growing brand is adding products without adding strategy. A founder sees an opportunity, a designer has an idea, a customer requests something new, or a competitor introduces an interesting product. The line expands.

Another jacket. Another pant. Another version of the hero tee. Together, they can create an assortment that feels crowded without actually giving the customer more choice.

Cannibalization happens when products solve essentially the same problem, target the same customer, sit at a similar price, and offer too little meaningful differentiation. The business has invested in two products, but the customer experiences one decision.

A product chart makes these overlaps visible. Just as importantly, it can reveal what is missing.

Perhaps a brand has built a strong sweater business but has no lightweight layer that naturally works over it. Perhaps there is an entry-level pant and an elevated pant, but no compelling middle option. Or perhaps the collection is filled with products designed for one particular use case while the customer needs greater versatility.

The empty spaces matter as much as the crowded ones.

Start With the Business, the Vision, and the Customer

There is no universal product architecture. The right structure depends on where the business is today, where the brand intends to go, and what the customer needs from it.

The first question is the current state of the business. Which products are driving the business? Where are the strongest categories? Where are the gaps? What can the brand realistically support from a design, development, inventory, and financial perspective?

The second is the brand’s vision. Is the business trying to build depth around a hero category? Move into a higher price point? Introduce more technical product? Reach a new customer? The assortment should create a path toward that future rather than simply reflect what exists today.

The third question is the customer. This is the filter that keeps product architecture from becoming an internal merchandising exercise.

Your customer does not care that the brand wants to add three new jackets. They care that they need something to wear over their sweater. They need something lightweight for a cool morning. They need something that can handle rain. They need something that can move from work to the weekend.

Those needs should determine the assortment.

Trading Up Should Mean Something

A good-better-best strategy is often treated as a pricing exercise, but price should be the result of differentiation rather than the only point of differentiation.

If a product costs more, the customer should understand what they are receiving in return. It might be a more sophisticated material, a specialized fit, greater protection, additional functionality, or a level of versatility that the core product does not provide.

The trade-up needs to be visible.

The same principle applies across the collection. Differentiation can come from price, but it can also come from fit, function, style, material, detail, or intended use. The important thing is that the distinction is meaningful enough to justify the product’s place.

This creates a healthier assortment and a clearer value proposition. It also gives the internal team a better filter for evaluating new ideas. Instead of asking only whether a product is good, the team can ask whether it adds something the collection actually needs.

That is a much more strategic decision.

Build the System, Not Just the Products

A product architecture ultimately gives a brand a way to see its assortment as a system rather than a collection of individual decisions.

It allows the team to identify where products are competing, where customers have meaningful reasons to trade up, and where an unmet need represents a genuine opportunity. It also creates discipline around growth. Not every good product idea needs to become part of the collection.

When the architecture is clear, the customer gets options without confusion. The merchandising team gets a framework for making decisions. And the business can grow its assortment without losing the clarity that made the brand compelling in the first place.

The objective is not to fill every possible space. It is to create the right spaces, for the right customer, with enough distinction that every product earns its place.

That is how a collection becomes more than a group of products.

It becomes a system designed around the customer.