The CIRCLES Method: A PM's Guide to Talking About Design

What Is the CIRCLES Method?

The CIRCLES method is a systematic framework designed to help product managers navigate complex product design challenges with clarity and confidence. Rather than jumping straight to solutions, this approach encourages PMs to deeply understand the problem, align with user needs, weigh realistic options, and present well-rounded, thoughtful recommendations.

Developed by Lewis Lin and introduced in his book "Decode and Conquer," this framework has become one of the most trusted approaches for product managers worldwide, particularly valuable in whiteboard interviews and real-world product development alike. The same principles of structured thinking that guide design decisions also inform our approach to user experience design, ensuring every product decision serves clear user needs.

Why Product Managers Need a Structured Framework

In high-pressure environments where deadlines loom and stakeholders have limited time, truly comprehending the situation is easier said than done. The CIRCLES method serves as a memory aid that prevents PMs from skipping critical steps in their analysis.

C - Comprehend the Situation

The first step enables product managers to gain a holistic view of the problem landscape with maximum context, addressing the problem with a more nuanced and comprehensive approach. This step is about asking the right questions before proposing any solutions.

The 5 W's and H Questions

• What is the situation or problem?
• Who is it for? Who are the key stakeholders?
• Why does that person need this solution?
• When is the solution needed or available?
• Where will this solution be implemented?
• How does the solution work or get delivered?

Real-World Example: Google Assistant

Google's development of Google Assistant demonstrates effective comprehension of the situation. By analyzing the broader context--the growing demand for smarter virtual assistants, increasing integration of technology in daily life, and the need for seamless user experiences--Google positioned itself competitively against Apple's Siri and Amazon's Alexa.

Daily Application

• Attend daily standups with cross-functional teams to stay informed
• Join customer service calls to gain first-hand experience with user pain points
• Document assumptions explicitly before moving forward with any solution

I - Identify the Customer

Product managers begin by thoroughly studying their target audience and users to empathetically grasp their needs and preferences. This step involves creating user personas and empathy maps to understand user characteristics, requirements, and aspirations.

Tools for Customer Identification

User Personas encapsulate user characteristics, requirements, and aspirations, emphasizing demographics and distinctive behaviors that influence product decisions.

Empathy Maps provide visual insight into user attitudes and behaviors, helping PMs gain a profound understanding of their users' daily challenges and aspirations.

Real-World Example: Netflix's Audience Segmentation

Product leaders at Netflix excel in identifying their customer base through sophisticated audience segmentation. By analyzing viewing habits, demographic data, and preference patterns, Netflix categorizes users into distinct segments. This deep understanding allows for highly personalized content recommendations, enhancing user satisfaction and engagement across their platform.

Daily Application

• Maintain a customer persona board (physical or digital) with regular updates
• Dedicate one day monthly to deep-dive into the customer world through interviews or observation
• Use survey data and support tickets to continuously refine customer understanding

R - Report Customer Needs

This step distills user personality traits, characteristics, and desires into actionable need statements. Product managers create concise descriptions based on use cases or user requirements, often using the proven user story template.

The User Story Template

"As a [type of user], I want to [perform some task], so that I can [achieve some goal]."**

Real-World Example: Spotify's Personalized Music Discovery

Spotify's ability to pinpoint and cater to unique music preferences demonstrates effective need reporting. Through features like Discover Weekly and Daily Mix, Spotify leverages vast data analytics to curate personalized playlists that resonate with individual tastes. The company understood that users need help discovering new favorites, positioning itself to offer suggestions based on personal listening data in ways traditional music services never could.

Daily Application

• Integrate quick surveys and NPS queries directly into products
• Hold weekly "Voice of Customer" meetings with the team
• Create feedback loops that make providing input as easy as possible for users

C - Cut Through Prioritization

In real-world scenarios, optimizing resource utilization through prioritization is crucial. PMs use established frameworks to identify and focus on high-impact user needs while balancing organizational constraints.

Popular Prioritization Frameworks

RICE (Reach, Impact, Confidence, Effort) scores features based on estimated reach, potential impact, confidence level, and required effort.

Impact vs Effort Matrix plots solutions on a 2x2 grid to prioritize high-impact, low-effort items first.

Custom Matrices tailored to organizational needs considering factors like revenue potential, technical debt, engineering resources, and feasibility.

Real-World Example: Intercom and the RICE Method

Intercom developed the RICE method to evaluate reach and impact of features while balancing confidence in estimates against effort required. When deciding to build their AI Chatbot, they determined that AI chatbots have broad appeal (wide reach), create real effects on client outcomes (high impact), and the effort to build didn't outweigh the benefits--leading to a successful product launch. Their experience demonstrates how structured prioritization aligns product decisions with user needs and business objectives.

Daily Application

• Hold interactive roadmap sessions where team members can contribute
• Each quarter, identify three "must-win" areas based on strategic goals
• Use consistent scoring matrices to remove bias from prioritization decisions

For teams exploring AI-powered product features, similar frameworks help prioritize which capabilities deliver the most value for users.

L - List Solutions

The fifth step involves finding probable solutions for prioritized user needs. This creative phase generates a range of ideas through structured brainstorming techniques.

Brainstorming Techniques

SCAMPER prompts teams to ask: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse.

Reverse Thinking starts from the desired outcome and works backward to identify necessary steps.

Attribute Method examines each product attribute and considers how it might be changed or improved.

Tip: Generate at least 3 possible solutions for each prioritized need to ensure thorough exploration.

Real-World Example: Amazon Alexa

Amazon's integration of Alexa into household devices transformed ordinary appliances into smart devices, facilitating seamless smart home experiences. By enabling voice commands for controlling lights, thermostats, and security systems, Amazon created convenience in daily routines. This required an extensive ecosystem of integrations--illustrating the comprehensive solution-listing process PMs must undertake to deliver transformative products.

Daily Application

• Utilize techniques like "crazy eights" and mind mapping in brainstorming sessions
• Set aside regular "Prototype Days" focused solely on creating solution mockups
• Encourage out-of-the-box thinking by removing constraints during initial brainstorming

E - Evaluate Trade-offs

Product managers conduct objective analysis of previously discussed solutions by creating comprehensive pros and cons lists. This critical step demonstrates analytical thinking and ensures informed decision-making.

Evaluation Criteria

• Revenue Potential: Expected impact on business revenue
• User Satisfaction: Likely effect on customer experience and satisfaction
• Implementation Complexity: Technical difficulty and resource requirements
• Time to Market: Speed of development and deployment
• Strategic Alignment: Fit with overall company strategy and goals

Trade-off Evaluation Matrix

Real-World Example: Facebook's News Feed Algorithm

Facebook frequently tweaks its algorithm to balance user engagement with content quality. One notable update prioritized content from friends and family over business pages, intending to enhance interaction quality and time spent on the platform. However, this presented significant trade-offs including reduced reach for businesses and news outlets--demonstrating the complex decisions PMs must navigate when balancing competing stakeholder needs.

Daily Application

• Host "Solution Showdowns" where teams pitch and vote on options
• Use customer scorecards with standardized evaluation criteria
• Role-play as customers to evaluate potential solutions from the user perspective

S - Summarize Recommendations

The penultimate step involves summarizing the final recommendation or product proposal and providing convincing, data-driven rationale for adoption. This synthesis demonstrates the PM's ability to connect analysis to action.

Key Elements of a Strong Recommendation

1. Clear Problem Statement: Restate the core issue being addressed
2. Customer-Centric Justification: Link back to user needs identified earlier
3. Trade-off Discussion: Acknowledge limitations and how they're being managed
4. Implementation Path: Outline next steps and success metrics
5. Expected Outcomes: Describe measurable results anticipated

Real-World Example: Microsoft Windows 10 Updates

Microsoft's strategic approach to Windows 10 updates demonstrates effective summarization. Each update cycle introduced features like Timeline for productivity, improved security protocols, and user-friendly design tweaks--all aimed at addressing user needs while advancing OS capabilities. Recommendations highlighted security enhancements, improved user experience, and new functionalities inspired by direct user feedback and emerging technology capabilities.

Daily Application

• Use storytelling techniques to communicate key decisions persuasively
• Create one-pager summaries for easy sharing with stakeholders
• Document the reasoning behind recommendations for future reference and learning

For more on creating effective design recommendations, see our guide on principles of great design craftsmanship.

Alternative Approach: Semi-CIRCLES Method

While the CIRCLES method is comprehensive, its sequential nature can sometimes result in rigid responses. The Semi-CIRCLES method offers a condensed alternative for situations requiring more flexibility.

Semi-CIRCLES: Three Simplified Steps

1. C → Analyze & understand the problem statement
2. IRCLE → Elaborate & assess solutions
3. S → Propose a solution

This 3-step approach provides a condensed, overarching framework that enables more flexible, engaging responses when the full CIRCLES structure feels too constraining.

When to Use Each Approach

Use Full CIRCLES When:

• Preparing for product management interviews
• Tackling complex, multi-stakeholder decisions
• Documenting detailed rationale for permanent record
• Training new team members on structured thinking

Use Semi-CIRCLES When:

• Time is extremely limited
• Stakeholders prefer brief, direct recommendations
• Iterating quickly in fast-moving environments
• The problem is relatively straightforward

Sources

• LogRocket: The CIRCLES Method - A PM's Guide to Talking About Design
• Product School: A Guide to the CIRCLES Framework with Product Examples
• Usersnap: What is the CIRCLES Method? Examples and Alternatives
• Lewis Lin - Decode and Conquer