Using Company and Market Context in Product Sense

IN THIS LESSON

Once you have established the goal, take a brief look at the strategic environment before you choose a customer.

The purpose of this section is to identify the small number of company, competitor, or market facts that should shape the product decisions that follow. You are not trying to perform a full Strategy interview. You are trying to understand what you need to know in order to achieve the goal credibly.

By the end of this lesson, you should be able to identify the few strategic facts that matter, explain why they matter, and move on without turning Product Sense into a market review.

Use a reduced strategy pass

A useful way to think about this section is as a reduced 5Cs analysis. In practice, the most useful areas are often:

• Company: What strengths, assets, products, constraints, or capabilities should affect what you build?
• Competitors: What are other products already doing, and what does that imply about the baseline, the opportunity, or the credibility of your eventual solution?
• Climate: What important market, technology, regulatory, or behavioral trend changes the environment you are designing for?

You do not need to announce a framework or give equal time to each category. The framework is useful because it helps you search for relevant facts. The interview answer should contain only the ones that actually matter.

For a Meta gardening prompt, this might sound like:

Now that I have the goal, I want to take stock of the strategic environment before choosing a customer. Meta has major strengths in social products, identity, communities, and increasingly AI. There are also existing gardening products and communities, so I want to understand what they already do well rather than assume differentiation is automatically valuable. And gardening is increasingly supported by tools that can identify plants or diagnose problems from images, which may change what customers expect from the experience. I’ll keep those factors in mind as I choose the customer and later evaluate solutions.

That is enough. The section establishes the environment the product has to succeed in without deciding the product in advance.

Every fact needs a reason to be there

Company and market facts are useful only when they affect the argument.

If you mention a competitor, explain why the competitor matters. It may show that customers already value a certain behavior, establish a baseline the product must meet, expose a weakness, or demonstrate that a particular idea is already credible.

If you mention a company strength, explain how it could improve the eventual product. A large user base, a social graph, proprietary data, a trusted brand, distribution, or technical capability is not interesting by itself. It matters because it can change what is feasible, valuable, or defensible.

If you mention a trend, explain what it changes. "AI is growing" is not useful. A useful observation would be that image understanding is becoming cheap and broadly available, which raises the baseline for products that help people diagnose physical problems.

A good test is simple:

What decision later in the answer could this fact change?

If you cannot answer that, leave the fact out.

Competitors help you decide whether to match or diverge

Competitor analysis does not exist to prove that your product should be different.

Sometimes the right answer is to build something similar to what already works. Real companies routinely copy established patterns when those patterns solve the problem well. Other times, a competitor exposes a gap or makes differentiation necessary.

You cannot make either judgment without understanding the market.

So the useful question is not:

How can I make my product different?

It is:

What are customers already getting, what appears to work, and what does that imply about what we should build?

That gives competitor analysis a clear purpose and prevents novelty from becoming a goal by itself.

If you do not know the exact competitor landscape, say so. You can still reason from the category, from adjacent products, or from the company's standard competitors. It is better to be explicit about uncertainty than invent market knowledge.

Let the context inform later choices

The strategic context should influence the rest of the answer without forcing an early conclusion.

You may notice that a company has an unusually strong capability. You may see that a competitor has validated an important behavior. You may recognize a trend that creates a new possibility. Those observations can shape which customers look attractive and which solutions later seem credible.

They should not become an excuse to choose the solution before you understand the customer and pain point.

For example, if Meta has strong AI capabilities, that is worth remembering. It does not mean the product should automatically be an AI assistant. If competitors already use computer vision effectively in gardening, that tells you something about customer expectations. It still does not tell you which customer problem matters most.

The strategic section prepares the later analysis. It does not replace it.

The point

After the goal, identify the few strategic facts you need in order to make credible product decisions. Focus on the company's real strengths, the competitive baseline, and relevant market or technology changes. Explain why each fact matters, then move on to the customer analysis.