The CIRCLES Method for Product Sense Questions

CIRCLES is a step-by-step structure, developed by Lewis Lin, for answering product design and product sense interview questions — questions like "design a product for X" or "how would you improve Y." The acronym stands for Comprehend the situation, Identify the customer, Report customer needs, Cut through prioritization, List solutions, Evaluate trade-offs, and Summarize your recommendation — a full sequence for organizing an otherwise open-ended, potentially rambling answer.

Quick facts

• CIRCLES stands for: Comprehend, Identify the customer, Report needs, Cut through prioritization, List solutions, Evaluate trade-offs, Summarize.
• It's a more detailed, step-by-step version of the general structured approach described in Product Sense Interview Questions Explained.
• Created by Lewis Lin, a well-known interview coach in the product management space.
• The framework works best as a mental checklist to guide genuine reasoning, not a script to recite word for word.

The seven steps, explained

Step	What it involves
Comprehend the situation	Clarify the question — what product, what goal, any ambiguity worth resolving upfront
Identify the customer	Define specifically who you're designing for
Report customer needs	Identify the real problems or needs this customer segment has
Cut through prioritization	Decide which need to focus on, and explain why
List solutions	Generate multiple possible solutions for the prioritized need
Evaluate trade-offs	Weigh the pros and cons of your top solution options
Summarize your recommendation	State your final recommendation clearly, with brief reasoning

A full worked example: "Design a product for busy parents"

Comprehend: "To clarify — are we designing a brand-new product, or a feature for an existing one? I'll assume this is a new, standalone product concept."

Identify the customer: "I'll focus on parents of young children, roughly ages 2-8, who are juggling full-time work alongside parenting responsibilities."

Report needs: "Likely needs include: coordinating schedules across school, activities, and childcare; reducing the mental load of tracking many small logistics; and finding brief pockets of quality time despite limited availability."

Cut through prioritization: "I'd focus on reducing the mental load of coordination, since this seems like a frequent, high-friction pain point that affects daily life directly, more so than the other needs identified."

List solutions: "A few options: a shared family calendar with automatic reminders, a delegation tool for splitting logistics tasks between co-parents or caregivers, or an AI assistant that proactively surfaces upcoming logistics conflicts before they become last-minute problems."

Evaluate trade-offs: "A shared calendar is simple to build but is already a crowded space with many existing tools. The AI assistant is more differentiated but harder to build well and requires trust in its proactive suggestions. The delegation tool addresses a specific, less-served need — coordinating between multiple caregivers — with less existing competition."

Summarize: "I'd recommend starting with the delegation tool, since it addresses a specific, underserved need with less direct competition, and could expand toward the AI assistant concept once we have real usage data and trust established with users."

Why the "Cut through prioritization" step matters so much

A common weakness in product sense answers is identifying several plausible customer needs, then trying to design a solution addressing all of them simultaneously — producing an unfocused, sprawling answer. The CIRCLES method's explicit prioritization step forces a candidate to make a real, defensible choice about what matters most, then focus the rest of the answer there — mirroring the real skill product managers need on the job, where focus and prioritization matter more than generating an exhaustive list of possibilities.

How CIRCLES compares to a general structured approach

CIRCLES is essentially a more detailed, explicitly named version of the general structured approach (clarify, identify problems, prioritize, propose solutions, measure success) covered in Product Sense Interview Questions Explained. Some candidates find CIRCLES's explicit seven-step structure easier to remember and apply consistently; others find a looser, more general structure feels more natural and less rigid in the moment. Either approach works — what matters most is genuinely organizing your answer with clear reasoning, not which specific named framework you use.

Common mistakes when using CIRCLES

• Reciting the acronym steps mechanically without genuinely reasoning through each one. Interviewers can tell when a candidate is following a memorized script rather than actually thinking through the specific question.
• Spending too much time on Comprehend and Identify, leaving little time for the more important Cut through prioritization and Evaluate trade-offs steps.
• Skipping the Evaluate trade-offs step entirely, jumping straight from listing solutions to a recommendation without showing the reasoning that led there.
• Treating every step as equally important to spend time on, rather than adjusting emphasis based on what the specific question actually calls for.

FAQ

Who created the CIRCLES method? Lewis Lin, an interview coach well known in the product management interview preparation space, developed and popularized this specific framework.

Should I memorize the CIRCLES acronym before an interview? It can help as a mental checklist to make sure you cover the key steps, but reciting it rigidly or announcing each step by name during the actual interview often feels unnatural — better to internalize the underlying structure and let it guide a genuine, conversational answer.

Is CIRCLES only useful for "design a product for X" questions, or does it work for "how would you improve Y" questions too? It works for both — the same underlying structure (clarify, identify the customer and needs, prioritize, generate and evaluate solutions, recommend) applies whether you're designing something new or improving an existing product.

How is CIRCLES different from just using common sense to structure an answer? CIRCLES formalizes what strong, naturally structured answers already tend to do — it's most useful for candidates who find open-ended interview questions genuinely difficult to organize on the spot, giving them an explicit checklist to fall back on under interview pressure.