Explainer Established Frameworks
CIRCLES — Product Design Framework
Lewis Lin's seven-step structure for "design a product" questions, and how it fits inside your six D's.
Industry standard
A seven-step structure for "design a product" questions ("design an alarm clock for blind people", "how would you improve Spotify?"). Mostly used in PM interviews, but it works on the job too: it forces you to settle who and which need before solutions.
User → need → priority → options → decision.
Origin
CIRCLES: Lewis Lin, Decode and Conquer. Cite it by author when you use it.
7steps
1customer segment
1–2needs prioritized
Interviewsmain use
The seven steps
| C | Comprehend the situation | What the product is, the goal (growth, engagement, revenue), constraints |
| I | Identify the customer | List user types, then pick one segment |
| R | Report the customer's needs | Problems and jobs-to-be-done, often as user stories |
| C | Cut through prioritization | Choose the one or two needs that matter most, and say why |
| L | List solutions | Several options, at least one non-obvious |
| E | Evaluate tradeoffs | Compare on value, effort, and risk |
| S | Summarize your recommendation | What, for whom, why it beats the alternatives, how you'd measure success |
How it's used
| Interviews | The standard structure for product-design questions. Use it without naming it; lead with the user and the goal. |
| On the job | Forces you to settle who and which need before solutions. |
In your frameworks and projects
Your own work, kept separate from the standard above. Your frameworks are the six D's ("Car is IE"), STARTIFY and RADAR.
| Six-D framework | Fits inside Discover → Define → Design. Its "pick one segment" step is the one the six D's don't spell out (a proposed revision). |
| PM decision framework | Same problem-first spine; CIRCLES designs something new, yours makes and defends a call. |