Product Design Overview

IN THIS LESSON

A Product Sense interview asks you to decide what product should be built or changed, for whom, and why.

The prompt usually gives you very little. You might be asked to design a gardening product for Facebook, improve parking in Google Maps, or create a product for travelers. None of those prompts contains a product decision. You have to create one.

This lesson explains the major parts of a Product Sense answer:

1. Goal
2. Strategy and company context
3. Customers
4. Pain points
5. Solutions
6. Conclusion

There are other useful techniques, but these are the main stages. The point of the structure is to help you make a recommendation that follows from the decisions before it.

What Product Sense is testing

Product Sense is sometimes described as a creativity interview. Creativity helps, but that description is incomplete.

A candidate can think of a good feature by luck, familiarity, or guessing what the interviewer wants. The interviewer needs to understand whether the candidate can repeatedly identify a valuable product opportunity and make a credible choice.

That requires more than an idea. You need to establish:

• What the product should accomplish
• What is true about the company and market that changes the decision
• Which customer matters most
• What that customer is trying to accomplish
• What is preventing them from doing it
• Which product would change that
• Why that product is preferable to the alternatives

The sections are connected. The goal affects which customer is attractive. The customer determines which pain points matter. The pain point defines what a solution has to change. The earlier reasoning gives you a basis for comparing solutions.

A strong answer is therefore not a collection of good observations. It is a sequence of decisions that eventually produces a product recommendation.

Clarifying questions and assumptions

Before beginning the case, make sure you understand the prompt well enough to answer it.

Ask a clarifying question when the answer could materially change your approach. For example, it may matter whether the interviewer wants a consumer product or an internal tool, whether the product is intended for an existing market, or whether a term in the prompt has a specific meaning.

Do not ask questions simply because Product Sense interviews are supposed to begin with questions. Many prompts are intentionally broad. In those cases, make a reasonable assumption and continue.

A useful clarification resolves uncertainty. A weak clarification asks the interviewer to make the product decision for you.

Once the prompt is clear enough, briefly explain how you will approach it. The explanation should give the interviewer a useful map rather than recite headings.

For example:

Gardening can go in several directions. I’ll start with what Facebook should accomplish in this space, use the company context to narrow the opportunity, choose a customer and problem, and then compare a few solutions.

That is enough. You have explained the logic of the answer without spending several minutes describing the framework.

Goal

Start by deciding what result the product should create.

For a broad consumer prompt at an engagement-first company such as Meta, valuable engagement is often a sensible default. Meta’s products and business model depend on people repeatedly doing things they find worthwhile. Another objective may be more appropriate when the company is in a particular strategic position—for example, when acquisition, retention, monetization, safety, reliability, or completion is the more urgent problem.

Choose one primary objective. Saying that the goal is “engagement and retention” usually avoids the decision rather than improving it. These outcomes are related, but the answer should identify which one governs the case and explain how it supports the others.

The goal should connect three things at a high level:

• Objective. The product or business outcome that governs the case. Why it matters: It gives the answer one controlling direction.
• Customer value. The broad improvement people should experience in the domain. Why it matters: It keeps the objective grounded in something customers care about.
• Company fit. The mission, position, or advantage that makes the opportunity appropriate for this company. Why it matters: It explains why the company should pursue the opportunity.

For a Facebook gardening product, a useful goal might be:

The product goal will be to drive engagement in the product and on Facebook as a whole by improving people’s experience of gardening and creating the future of human connection.

The goal is intentionally high-level. It establishes engagement as the objective, a better gardening experience as the customer value, and human connection as the mission fit.

It does not decide whether gardeners need diagnosis, local advice, better planning, stronger communities, easier access to experts, or something else. Those are customer and pain-point questions that should be answered later.

More detail may sound attractive, but premature specificity can quietly embed pain points before they have been assessed. The goal should guide the analysis without deciding the analysis.

Strategy and company context

The company and market context should narrow the product decision.

You do not need to give every Product Sense prompt a full strategy case. You do need to identify the facts that change which customer, problem, or solution is attractive.

Useful questions include:

• Why is this company a credible participant in the space?
• What assets, capabilities, distribution, or customer relationships could matter?
• What would be difficult for competitors to reproduce?
• What constraints or risks should shape the product?
• What strategic need makes this opportunity relevant now?

For Facebook and gardening, the important observation may be that Facebook already contains local communities, social relationships, groups, photos, and people with practical experience they are willing to share. That points toward opportunities where social and local knowledge matters. It does not require you to announce a product idea.

A fact belongs in the answer when you can state what it changes.

Weak:

Facebook has Groups, Marketplace, and a large user base.

Stronger:

Facebook already connects people through local groups and existing relationships, so it has an advantage when the value depends on trusted, location-specific knowledge rather than generic information.

The second statement gives you a decision rule. It will later help you compare customers and solutions.

Keep this section proportional to the case. A few relevant facts are usually more useful than a complete recital of the company, competitors, collaborators, customers, and climate.

Customers

Start by understanding whose demand gives the product or system a reason to exist.

In a simple consumer product, the end customer and direct user may be the same person. In an enterprise product or marketplace, the buyer, user, administrator, supplier, decision-maker, and person affected by the decision may be different. Distinguish those roles only when the distinction changes the product.

Then identify meaningful customer groups.

A good segment predicts a different motivation, pain point, behavior, constraint, or product requirement. Age and income can sometimes matter, but they are often weak substitutes for the real difference.

For a gardening product, possible groups might include:

• New homeowners trying to establish or improve a yard
• Experienced gardeners who enjoy sharing knowledge
• Renters or apartment residents working with limited space
• People growing food to save money or improve what they eat

These groups are useful because they want different things and face different constraints. They could plausibly lead to different products.

Qualify the groups before choosing. Explain why each belongs in the decision set, then compare them using criteria that follow from the goal and company context.

For example, new homeowners may have strong motivation, recurring questions, and a clear need for local advice. Experienced gardeners may create valuable supply, but their activity matters because it helps other people succeed. Apartment gardeners may have substantial constraints, but the opportunity may fit Facebook’s local-community advantage less directly.

Then choose one group and state the decisive reason.

I’d start with new homeowners. They care a lot about getting the yard right, they face repeated decisions they do not feel equipped to make, and local experience could materially improve the outcome.

The purpose of segmentation is not to demonstrate that you can invent categories. It is to identify the customer whose needs create the strongest product opportunity.

Pain points

Once you have selected the customer, understand what that person is trying to accomplish and what is blocking them.

A useful pain point contains both parts:

• A meaningful motivation
• A specific obstacle that prevents or weakens progress

“Gardening is inconvenient” tells you almost nothing. “New homeowners do not know which plants will work in their soil, light, and climate, so they delay decisions or spend money on choices that fail” is much more useful.

The second version explains:

• What the customer wants
• What information is missing
• Why the problem matters
• What a solution would need to change

You may use a journey to find the problem, but the journey is not the output. The output is one prioritized pain point.

Consider where the customer starts, what they try, where uncertainty or effort accumulates, what alternatives they use today, and what happens when the problem is not solved. Look for pain that is specific enough to guide the product and important enough to affect behavior.

The problem should also connect to the goal. A real customer frustration may still be a weak product opportunity if solving it would not create the intended outcome.

By the end of this section, the answer should be able to state:

This customer is trying to accomplish X, but Y prevents them from doing it, and solving Y would materially advance the goal.

For the gardening case:

New homeowners want to make confident decisions about their yard, but generic advice does not tell them what will work in their exact conditions. The uncertainty causes delay, wasted money, and repeated failure.

That gives the solution section a clear job.

Solutions

Generate several ways to address the selected pain point, then present a small set of credible alternatives.

You may think of product ideas at any point in the case. Keep early ideas in mind, but do not let them determine the customer and pain-point analysis. The interviewer should encounter the recommendation after the relevant problem has been established, not as the destination announced at the beginning.

Private ideation can be messy. You may think of weak, repetitive, or incomplete ideas before reaching better ones. The interview does not need a transcript of that process.

A practical target is about three credible alternatives. The exact number is less important than having enough breadth to create a real choice without filling the interview with feature inventory.

For each solution, explain:

• What the customer would do
• How the product would work
• Which part of the pain point it changes
• Why the company can credibly provide it

Take a moment to picture the experience before presenting it. A title such as “AI garden assistant” is not yet a product. What information would the customer provide? What would the product return? Why would the response be more useful than the alternatives available today?

Possible solutions for the new-homeowner problem might include:

1. A local garden-planning tool that uses photos and neighborhood conditions to suggest suitable plants
2. Neighborhood gardening circles where homeowners can ask questions and receive advice from nearby gardeners
3. A project journal that helps users document what they planted, track results, and learn from similar yards over time

Each idea should be presented credibly. Do not include obviously weak options merely to make the preferred one look better.

Then choose criteria that follow from the case. In this example, useful criteria might include confidence of advice, fit with Facebook’s advantage, likelihood of participation, and ability to create recurring value.

Apply the same criteria to the alternatives and explain why one wins. A scorecard can help you think, but the spoken answer should describe the tradeoffs rather than narrate High, Medium, and Low ratings.

For example:

I would choose neighborhood gardening circles. The planning tool could provide faster answers, but it would need reliable data about very specific local conditions. The journal could create long-term value, but it helps after the homeowner has already made the difficult decisions. The circles address the uncertainty directly, use Facebook’s existing local communities, and give experienced gardeners a reason to contribute.

The recommendation should emerge from the comparison. The strongest alternative should receive enough credit that the choice demonstrates judgment.

Conclusion

The conclusion should make the answer easy to recover.

Restate:

• The customer
• The important pain point
• The product you would build
• The decisive reason it should achieve the goal
• The most important tradeoff, when it materially affects the recommendation

A conclusion to the gardening case might sound like this:

I’d start with new homeowners who want to improve their yard but do not know what will work in their local conditions. I’d build neighborhood gardening circles where they can share a photo or question and get advice from nearby gardeners with relevant experience. I prefer that to a generic planning tool because local knowledge is the main gap, Facebook already has the communities that can provide it, and the exchange gives both new and experienced gardeners a reason to participate repeatedly. The main risk is answer quality, so I would begin with structured questions and lightweight reputation signals rather than an open feed.

The conclusion is not a second solution section. It should state the decision and the reasoning that most clearly supports it.

Use the structure according to the case

The major stages remain stable, but they do not always deserve equal time.

A prompt with a clearly defined customer may require little segmentation. A product with several actors and conflicting incentives may require more customer-system analysis. A safety-sensitive product may require more discussion of risk before a solution is credible.

Spend time where the case contains a consequential decision. Do not expand a section simply because the framework contains it.

The same principle applies to details inside the answer. A major decision deserves explanation. An important technique may deserve a paragraph. A useful caveat may need only a sentence. True but irrelevant material should be left out.

Signposting should explain why the next stage follows from the previous one.

Instead of:

Now I will discuss customer segments.

Try:

Now that the goal and Facebook’s relevant advantage are clear, I’m going to choose the customer whose problem gives us the strongest opportunity to use them.

The framework should make the reasoning easier to follow. It should not become the subject of the interview.