What the method is for
I use the CIRCLES method as a prompt for structuring an ambiguous product design conversation. The letters are commonly expanded as Comprehend the situation, Identify the customer, Report the customer needs, Cut through prioritization, List solutions, Evaluate trade-offs, and Summarize.
The value is not reciting the acronym. It is making sure I understand the problem and user before jumping to features.
How I work through it
I clarify the goal, constraints, existing product, and time horizon, then choose a specific user or segment. I describe the user’s job and desired outcome, separating a need from a requested feature. I prioritize using severity, frequency, reach, strategic fit, confidence, and constraints.
Only then do I generate a few distinct solutions. I compare them on value, effort, feasibility, risk, accessibility, and unintended effects. I explain how I would validate the leading option through research, a prototype, or a staged release, then summarize the user, problem, direction, success signal, and next learning step.
I do not force every letter when the conversation moves elsewhere. I avoid invented market numbers and claims of certainty. CIRCLES is a mental checklist that helps me slow the jump to features and show how I would learn.
A practical check
In an interview, I would say what I am assuming and ask one or two clarifying questions. That signals judgment more clearly than racing through a memorized framework. I would also reserve time to discuss trade-offs, because the best solution depends on the constraints.
My bottom line
I use this framework to make the work explicit, not to create ceremony for its own sake. Start with the decision, show the evidence, make ownership visible, and revisit the approach when the product or context changes.
If you are building the fundamentals behind this kind of work, the Product HQ product management certification is a useful next step. I also share practical lessons in the Product HQ newsletter.