circles-methodlisted

# CIRCLES Method A 7-step framework (Lewis C. Lin, *Decode and Conquer*) for answering product- design questions completely instead of jumping to a solution. The discipline is that you do not propose solutions until after you've understood the situation, named a specific customer, and prioritized their needs. CIRCLES = **C**omprehend · **I**dentify · **R**eport · **C**ut · **L**ist · **E**valuate · **S**ummarize. ## The seven steps **C — Comprehend the situation** Clarify the question before answering. What is the product/feature? Who's asking and why now? What are the constraints (platform, timeline, business model)? What's the goal — growth, revenue, retention, a new segment? State assumptions explicitly. The classic mistake is answering a question you weren't asked. **I — Identify the customer** Pick a specific customer segment. Not "everyone" — a named persona with a context. If multiple segments exist, list them, then choose ONE to design for this pass and say why (size, strategic value, acuteness of pain). **R — Report customer needs** For the chosen customer, enumerate their needs / jobs / pain points. Frame as the customer's goals, not features. Use user stories: "As a [customer], I want to [need] so that [outcome]." Aim for 5-7; group related ones. **C — Cut through / prioritize** You can't build everything. Prioritize the needs against an explicit criterion — goal-impact, reach, strategic fit, effort. *This is where a prioritization method plugs in* (see `pri