Defining the Ecosystem

IN THIS LESSON

Before you segment customers, understand how value is created in the market and which user population you should analyze.

Every product depends on supply. Netflix needs content. Airbnb needs homes. A medical marketplace needs doctors. Facebook needs people willing to create content. The useful distinction is whether that supply participates as a user side of the product you are reasoning about.

For the Netflix consumer product, viewers use the product and consume the value. Studios and publishers supply the content, but they are not necessarily users of the consumer product. There may be separate partner tools or business processes for them, but those do not need to become part of the customer analysis unless they matter to the prompt.

Many technology products expose both sides directly. Facebook is an easy example: some users are consuming content while others are creating it, and the same person can play both roles at different times. In a medical marketplace, the roles may be more cleanly separated, with patients seeking care and doctors supplying it.

Ecosystem definition should answer three questions:

1. Who is the demand side receiving the value?
2. Who supplies what that demand side needs, and does that supply participate through the product?
3. Which user population should I segment for this case, and why?

This is usually a short section. The purpose is to show that you understand how value is realized, choose the right population to analyze, and move on.

What this task proves about you

Product managers often have to reason about markets they have never worked in before. One of the first things they need to understand is who creates the value, who consumes it, and how those roles fit together.

Defining the ecosystem gives the interviewer evidence that you can make sense of that structure. You are showing that you can identify the important user roles, explain how value moves among them, distinguish demand from supply, and choose the population that is most relevant to the problem.

This is a causal reasoning task. Naming participants is not enough. You need to understand why each side participates and how one side's behavior affects the value received by the other.

Identify demand and supply

Start with the demand side. This is the population consuming the product, service, content, inventory, care, information, or other value the system ultimately exists to provide.

Then identify the supply required to create that value. Supply might be content, homes, rides, professional services, expertise, labor, inventory, data, or another input.

The important next question is whether the supply side is itself a user population of the product in the case.

For Facebook, it is. Content creators use Facebook to provide content, while other users consume it. For a medical marketplace, doctors and patients may both interact directly with the marketplace. For Netflix's consumer experience, the content studios are certainly part of the supply chain, but they are not a user population you need to segment simply because they supplied the shows.

This distinction keeps the ecosystem analysis tied to the product instead of expanding into every organization or process required to make the business exist.

If there is a third user role that materially changes the value exchange, include it. Do not add additional sides merely because more stakeholders exist.

Explain how value is realized

For each relevant side, explain what it contributes and why it participates.

On Facebook, consumers get entertainment, information, and connection from content. Creators provide that content and may receive an audience, interaction, expression, status, or another form of value in return.

In a medical marketplace, patients receive access to care. Doctors supply the care and receive access to patients and compensation for providing the service.

The point is not to find perfect labels. It is to demonstrate that you understand why the market works at all.

A useful ecosystem explanation makes the value exchange clear enough that your choice of customer population has a reason behind it.

Demand is the usual place to start

Demand is the stronger default because it is the source of value in the market. Available supply is necessary, but supply only becomes useful when somebody wants what is being supplied.

For that reason, unless the prompt explicitly asks you to solve a supply-side problem or the case gives you a compelling reason that changing supply is the best way to improve demand-side value, you should generally expect to segment and solve for demand.

That is guidance for your reasoning, not something you can cite as the reason for your choice. You still need a case-specific explanation.

If you are asked to improve Airbnb broadly, for example, you might focus on guests because the goal is ultimately to improve the travel experience they receive. If the prompt asks how to improve hosting, hosts are clearly the relevant population. You might also choose hosts in a broader case if you can establish that a supply constraint is materially limiting guest value.

The choice should follow from the case.

Choose the user population you will segment

Ecosystem definition ends when you state which user population you will segment next and why.

For a product where only the demand side is relevant to the product experience, this can be very short:

Viewers are the demand side here. Netflix obviously depends on content supply, but for this consumer-product question the users I need to understand are viewers, so I'll segment them next.

For a product with multiple user sides, you may need a few more sentences:

Facebook has a demand side consuming content and a supply side creating it, although the same person can play both roles. For this prompt I'm going to focus on consumers because the goal is to improve the experience people get from using Facebook. I'll segment the consumer side next.

A supply-side choice should be equally explicit:

Patients are the demand side and doctors supply the care, but this prompt asks us to improve the physician experience. I'm going to segment doctors because they are the users whose workflow the product is meant to improve, while keeping the effect on patient access and care quality in view.

You have not segmented the population yet. You have decided which population belongs in the segmentation analysis.

Demand-side scope does not make supply disappear

Choosing a demand-side customer does not mean the eventual product can ignore supply.

A solution for consumers may require new behavior or functionality on the supply side. If so, you can acknowledge that dependency when you define the solution. A demand-side feature may need creators to provide a new kind of content, hosts to supply better information, or experts to respond to requests.

That does not require you to reopen customer segmentation or turn the answer into two parallel product cases. Keep the primary solution scoped to the customer you chose, while noting the additional supply-side capability when it is necessary for the product to work.

Keep it proportional

This section should be as short as the case allows.

Identify demand, identify the relevant supply, determine whether supply participates as a user side of the product, choose the user population you will analyze, and explain why. Spend more time only when the ecosystem itself is genuinely ambiguous or important to the product decision.

The goal is to check the box with real understanding. The interviewer should be able to see that you understand how value is created and that you deliberately chose the population you are about to segment.

The point

Every product has supply, but not every supply source is a user side of the product you are designing. Define demand, identify the relevant supply and user roles, explain how value moves among them, choose the population you will segment for a reason grounded in the case, and move on.