The CIRCLES Method is a framework that guides a complete and thoughtful response to any product design question. The CIRCLES Method is a framework of best practices that Google uses while interviewing candidates for product manager positions.
Element
Description
Concept Overview
The CIRCLES Method is a problem-solving framework used to analyze and address complex issues or challenges by breaking them down into smaller, manageable components.
Acronym
CIRCLES stands for (1) Clarify the problem, (2) Identify the root causes, (3) Rank the causes, (4) Create solutions, (5) Launch the plan, (6) Evaluate results, and (7) Share lessons learned.
Step 1: Clarify
This initial step involves clearly defining the problem or challenge, ensuring a precise understanding of its scope, impact, and underlying issues.
Step 2: Identify
Identify the root causes of the problem. This phase involves digging deeper to uncover the fundamental reasons behind the issue, looking beyond surface-level symptoms.
Step 3: Rank
Once the root causes are identified, they are ranked or prioritized based on their significance and impact. This step helps focus efforts on addressing the most critical issues first.
Step 4: Create
In this phase, solutions and strategies are generated to address the identified root causes. Creative thinking and problem-solving techniques are employed to develop effective solutions.
Step 5: Launch
The selected solutions and strategies are implemented, putting the plan into action. Effective project management and execution are crucial during this phase to ensure successful implementation.
Step 6: Evaluate
After implementation, the outcomes and results are evaluated against predefined success criteria. This phase involves assessing the effectiveness of the solutions and making any necessary adjustments.
Step 7: Share
Lessons learned and insights gained throughout the process are shared with relevant stakeholders. This step promotes knowledge sharing and continuous improvement within the organization.
Problem Solving
The CIRCLES Method provides a structured approach to problem-solving, helping teams tackle complex challenges systematically and collaboratively.
Root Cause Analysis
Identifying root causes allows organizations to address underlying issues, reducing the likelihood of problem recurrence.
Prioritization
Ranking root causes helps allocate resources efficiently, ensuring that efforts are directed toward addressing the most critical factors contributing to the problem.
Creativity
The method encourages creative thinking during the solution generation phase, fostering innovation and diverse approaches to problem resolution.
Implementation
Effective execution is emphasized, ensuring that solutions are not only devised but also put into action successfully.
Continuous Improvement
The evaluation phase promotes a culture of continuous improvement by learning from both successes and failures, refining strategies, and enhancing problem-solving capabilities.
Collaboration
The CIRCLES Method encourages collaboration and communication among team members and stakeholders, fostering a collective effort to address complex challenges.
Examples
– An IT department may use the CIRCLES Method to address recurring network downtime issues. – A manufacturing facility may apply the method to improve product quality and reduce defects. – A nonprofit organization could utilize the approach to analyze declining donor contributions and devise strategies to increase support.
The popular framework – which has been featured on Business Insider – helps candidates answer production design questions through mental cues.
These mental cues are based on fundamental principles of production design. This allows the candidate to respond in a thoughtful, persuasive, and composed fashion instead of saying whatever comes to mind.
Using the CIRCLES Method, the response will include important aspects of product management, including user empathy, prioritization, and problem definition.
The seven stages of the CIRCLES Method
During the interview, the candidate is encouraged to move through seven stages. Each stage corresponds to a letter which make up the CIRCLES acronym:
C – Comprehend the situation
Begin by considering a few key questions.
Who is the product designed for? Why do customers need it? How does it work? Where and when is it available? How does the business define customer satisfaction? Is satisfaction or another important metric failing to meet targets?
I – Identify the customer
Be prepared and have a list of potential target audiences that will benefit from the product.
Then, in the interview, choose one buyer persona that best supports your argument.
To save time, consider illustrating a buyer persona using a simple matrix that describes user behaviours, needs, goals, and the demographic.
R – Report the customer’s needs
This can be done by creating a user story to delve deeper and understand user needs and their intended benefits.
C – Cut, through prioritization
Narrow the various needs of the customer down to one you feel will have the greatest impact.
Think about how certain needs would be prioritized according to time, money, or other constraints. Here, a prioritization matrix or A/B testing is appropriate.
This stage demonstrates to the interviewer that you can assess the pros and cons of different scenarios and think strategically.
L – List solutions
For the identified need, list several solutions. Many candidates are great at identifying problems but have difficulty solving them.
Brainstorming frameworks such as the Reversal Method and Attribute Method can help the candidate think on the spot.
E – Evaluate trade-offs
Evaluation requires that the candidate be analytical, objective, and thoughtful. Trade-off criteria should be defined to better get your point across. Solutions should be analyzed via a pros and cons list. This stage is important because the ability to critique yourself is important in successfully responding to critique from others.
S – Summarise your recommendation
Depending on how well your idea was presented, this last step may be unnecessary. Having said that, some organizations will want to assess your ability to concisely summarise a product proposal.
In no more than 30 seconds, make a product or feature recommendation and reiterate why it is most beneficial to the user. In closing, clarify why your preferred solution is better than the others.
When to Use the CIRCLES Method:
The CIRCLES Method is valuable in various problem-solving scenarios:
Complex Problems: Use it when dealing with complex or multifaceted problems that require a systematic approach.
Team Collaboration: Employ it in team-based problem-solving efforts to ensure a structured and collaborative approach.
Continuous Improvement: Apply the method to drive continuous improvement by identifying and addressing organizational challenges.
Strategic Decision-Making: Use it to support strategic decision-making processes, especially when faced with strategic challenges.
How to Use the CIRCLES Method Effectively:
To effectively use the CIRCLES Method, follow these guidelines:
Define the Problem:
Clearly define the problem you aim to solve, ensuring a shared understanding among team members.
Identify Components:
Break down the problem into its constituent components, factors, or elements.
Collect Data:
Gather relevant data, information, and insights related to each component of the problem.
Analyze and Evaluate:
Analyze the collected data to assess the impact and significance of each component.
Evaluate potential interconnections and dependencies between components.
Generate Solutions:
Brainstorm and generate potential solutions or strategies for each component.
Prioritize Solutions:
Prioritize the generated solutions based on their feasibility, impact, and alignment with organizational goals.
Implement Solutions:
Begin implementing the selected solutions, starting with those that address critical components.
Monitor Progress:
Continuously monitor the progress of solution implementation and adjust strategies as needed.
Iterate and Refine:
Iterate through the process as necessary, refining solutions and addressing any emerging issues.
Drawbacks and Limitations of the CIRCLES Method:
While the CIRCLES Method offers a structured approach to problem-solving, it also has certain drawbacks and limitations:
Resource Intensity: The method may require significant time and resources, making it less suitable for quick problem-solving needs.
Complexity: In some cases, the method’s structured approach may be overly complex for relatively simple problems.
Dependence on Collaboration: Effective implementation depends on collaboration and the availability of diverse perspectives within a team or organization.
Subjectivity: The prioritization of solutions can be subjective and influenced by individual or group biases.
What to Expect from Implementing the CIRCLES Method:
Implementing the CIRCLES Method can lead to several outcomes and benefits:
Comprehensive Problem Analysis: Expect a thorough and comprehensive analysis of complex problems.
Collaborative Solutions: Foster collaboration and collective problem-solving within teams or organizations.
Informed Decision-Making: Support informed decision-making by breaking problems down into manageable components.
Structured Approach: Implement a structured problem-solving approach that can be applied to various scenarios.
Relevance in Modern Problem-Solving:
The CIRCLES Method remains relevant in modern problem-solving and decision-making, particularly in organizations seeking a systematic and collaborative approach to addressing complex challenges. It aligns well with principles of continuous improvement, data-driven decision-making, and team-based problem-solving.
Conclusion:
The CIRCLES Method is a structured and systematic framework for problem-solving, designed to help individuals and organizations address complex challenges effectively.
By breaking problems down into manageable components, fostering collaboration, and promoting iterative analysis and solution generation, the method supports informed decision-making and continuous improvement efforts.
While recognizing its potential resource intensity and subjectivity, many organizations continue to rely on the CIRCLES Method as a valuable tool in modern problem-solving and decision-making processes.
Case Studies
Apple Inc.:
Comprehend: Apple understands that its products are designed for consumers seeking user-friendly, premium technology.
Identify: They target a wide demographic but often focus on creative professionals and tech enthusiasts.
Report: Apple recognizes user needs for seamless integration, performance, and a reliable ecosystem.
Cut: Prioritizing design and user experience, they allocate resources accordingly.
List: Apple offers various products and models, providing choices to users.
Evaluate: They weigh trade-offs between innovation and maintaining a consistent user experience.
Summarize: Apple recommends products that deliver a blend of aesthetics, functionality, and user satisfaction.
Identify: Their customer base includes diverse groups, from book lovers to tech enthusiasts.
Report: Amazon understands users’ needs for fast, reliable delivery and an extensive product selection.
Cut: Prioritizing logistics and customer experience, they optimize supply chain and delivery services.
List: Amazon offers a vast range of products and services, catering to different customer preferences.
Evaluate: They analyze trade-offs between profitability and customer satisfaction.
Summarize: Amazon recommends products and services that prioritize convenience, choice, and affordability.
Google:
Comprehend: Google’s products are designed for users seeking efficient information retrieval and online experiences.
Identify: Their user base spans across demographics, primarily those searching for information online.
Report: Google recognizes the need for accurate, relevant search results and simplicity.
Cut: They prioritize algorithmic improvements to enhance search quality.
List: Google offers various services, from search and email to cloud storage and productivity tools.
Evaluate: They assess trade-offs between search speed, ad revenue, and user experience.
Summarize: Google recommends products that focus on providing fast, relevant information to users.
Tesla:
Comprehend: Tesla targets environmentally conscious consumers seeking electric vehicles with high performance.
Identify: Their audience includes tech-savvy individuals looking for sustainable transportation.
Report: Tesla understands user needs for electric, energy-efficient cars with advanced technology.
Cut: They prioritize battery technology and electric powertrains.
List: Tesla offers different vehicle models, each catering to specific user preferences.
Evaluate: They analyze trade-offs between range, performance, and affordability.
Summarize: Tesla recommends electric vehicles that combine sustainability, performance, and cutting-edge technology.
Netflix:
Comprehend: Netflix serves entertainment enthusiasts seeking on-demand streaming content.
Identify: Their user base includes viewers of various genres and demographics.
Report: Netflix understands the need for personalized content recommendations and diverse original programming.
Cut: They prioritize data-driven content suggestions and original content production.
List: Netflix offers a wide array of movies, series, and documentaries to cater to different tastes.
Evaluate: They assess trade-offs between licensing costs and exclusive content creation.
Summarize: Netflix recommends content that aligns with users’ viewing history and preferences.
Uber:
Comprehend: Uber’s service is designed for individuals seeking convenient, reliable transportation.
Identify: Their user base includes commuters, travelers, and those looking for an alternative to traditional taxis.
Report: Uber understands user needs for quick, cashless rides and driver ratings.
Cut: They prioritize efficient ride matching and safety features.
List: Uber offers various ride options, such as UberX, UberPool, and UberEats for food delivery.
Evaluate: They assess trade-offs between surge pricing and rider-driver satisfaction.
Summarize: Uber recommends rides that balance convenience, affordability, and safety.
Airbnb:
Comprehend: Airbnb caters to travelers seeking unique and affordable accommodations.
Identify: Their user base includes tourists, business travelers, and adventure seekers.
Report: Airbnb understands user needs for diverse lodging options and trustworthy host reviews.
Cut: They prioritize host quality and property diversity.
List: Airbnb offers a wide range of lodging types, from apartments to castles.
Evaluate: They assess trade-offs between price competitiveness and listing quality.
Summarize: Airbnb recommends accommodations that align with users’ preferences and budget.
Starbucks:
Comprehend: Starbucks serves coffee enthusiasts seeking a premium café experience.
Identify: Their customer base includes coffee lovers, professionals, and students.
Report: Starbucks understands the need for high-quality coffee, cozy ambiance, and loyalty rewards.
Cut: They prioritize coffee sourcing, barista training, and store design.
List: Starbucks offers various coffee blends, seasonal drinks, and food items.
Evaluate: They assess trade-offs between product quality and pricing.
Summarize: Starbucks recommends coffee options and menu items that emphasize quality and comfort.
Facebook:
Comprehend: Facebook’s platform targets individuals seeking social connections and content sharing.
Identify: Their user base spans across age groups and demographics.
Report: Facebook recognizes the need for user engagement, personalized feeds, and social networking.
Cut: They prioritize algorithms that enhance user interactions and content relevance.
List: Facebook offers features like Groups, Marketplace, and Stories.
Evaluate: They assess trade-offs between ad revenue and user satisfaction.
Summarize: Facebook recommends content and connections that foster meaningful interactions.
McDonald’s:
Comprehend: McDonald’s caters to individuals seeking quick-service meals and fast-food convenience.
Identify: Their customer base includes families, students, and on-the-go consumers.
Report: McDonald’s understands the need for consistent menu items, affordability, and efficient service.
Cut: They prioritize fast food preparation and drive-thru efficiency.
List: McDonald’s offers a standardized menu with variations for local tastes.
Evaluate: They assess trade-offs between menu diversity and operational simplicity.
Summarize: McDonald’s recommends meals that provide fast, familiar, and budget-friendly dining options.
Key takeaways
The CIRCLES Method is a framework that guides complete and thoughtful interview answers concerning product development and design.
The CIRCLES Method is based on mental cues that represent fundamental principles of product design. Using the cues, the candidate being interviewed can give reasoned, persuasive, and structured answers.
The CIRCLES Method is based on seven stages that make up the CIRCLES acronym. If the candidate moves through the first six stages with aplomb, the seventh evaluation stage may be unnecessary.
Key Highlights of the CIRCLES Method:
Definition: The CIRCLES Method is a framework used by Google for interviewing candidates for product manager positions. It guides candidates in providing comprehensive and structured responses to product design questions.
Purpose: The framework helps candidates answer product design questions using mental cues based on fundamental principles of product design. It enables candidates to respond thoughtfully and persuasively rather than impulsively.
Seven Stages of the CIRCLES Method:
C – Comprehend the Situation: Understand key aspects of the product, its target audience, purpose, availability, and business goals.
I – Identify the Customer: Choose a specific buyer persona from potential target audiences to support your argument.
R – Report the Customer’s Needs: Create a user story to delve into user needs and benefits.
C – Cut, Through Prioritization: Prioritize customer needs based on impact, considering constraints like time and resources.
L – List Solutions: Generate multiple solutions to address the identified need.
E – Evaluate Trade-offs: Analyze solutions using pros and cons criteria, demonstrating analytical and strategic thinking.
S – Summarize Your Recommendation: Concisely summarize your preferred solution, emphasizing its benefits to the user.
Application:
Structured Interview Responses: The CIRCLES Method helps candidates provide structured, well-thought-out responses during product manager interviews.
Problem Solving: The method assists candidates in brainstorming solutions, evaluating trade-offs, and making recommendations.
Demonstrating Skills: Candidates showcase skills like user empathy, prioritization, problem-solving, and communication.
Benefits:
Structured Responses: Candidates can provide comprehensive answers by following the stages of the method.
Strategic Thinking: The prioritization and trade-off evaluation stages demonstrate candidates’ ability to think strategically.
Effective Communication: Summarizing recommendations concisely highlights candidates’ communication skills.
Adaptation:
The CIRCLES Method is adaptable to various interview scenarios and can be used beyond product management interviews.
It encourages a structured approach to problem-solving and decision-making.
Related Frameworks
Description
When to Apply
Root Cause Analysis (RCA)
Root Cause Analysis (RCA) is a methodical process for identifying the underlying causes of problems or events. It involves asking “why” multiple times to uncover the root cause(s) and address them effectively.
When investigating incidents, failures, or quality issues, understanding systemic problems and preventive measures, or implementing corrective actions to prevent recurrence and improve processes.
Fishbone Diagram (Ishikawa Diagram)
A Fishbone Diagram, also known as an Ishikawa Diagram, is a visual tool used to identify potential causes of a problem or effect. It categorizes possible causes into branches stemming from a central spine, resembling the skeleton of a fish.
When exploring root causes of quality issues, process inefficiencies, or product defects, facilitating brainstorming and group discussion, or visualizing cause-and-effect relationships to guide problem-solving efforts and decision-making.
5 Whys Technique
The 5 Whys Technique is a simple yet powerful method for exploring the root cause of a problem by asking “why” repeatedly. It helps uncover deeper layers of causation beyond surface-level symptoms, leading to more effective solutions.
When probing beneath surface-level issues, uncovering root causes of problems, or facilitating root cause analysis sessions to encourage critical thinking and identify systemic issues for effective problem-solving and prevention.
Failure Mode and Effects Analysis (FMEA)
Failure Mode and Effects Analysis (FMEA) is a systematic approach to identifying potential failure modes in a process, product, or system, assessing their impact and likelihood, and prioritizing actions to mitigate or eliminate risks.
When evaluating potential failures or risks in designs, processes, or systems, identifying failure modes and effects, or developing risk mitigation and prevention strategies to enhance reliability and quality while reducing operational risks.
Pareto Analysis (80/20 Rule)
Pareto Analysis, based on the 80/20 Rule, identifies the most significant factors contributing to a problem or outcome. It prioritizes efforts by focusing on the vital few (20%) that yield the most significant impact, rather than the trivial many (80%).
When determining priorities or allocating resources, identifying critical issues or opportunities for improvement, or optimizing resource utilization and efficiency by addressing key contributors to desired outcomes or problems.
SWOT Analysis
SWOT Analysis assesses an organization’s internal strengths and weaknesses, as well as external opportunities and threats. It helps identify strategic factors affecting business performance and guides decision-making for sustainable growth.
When evaluating business strategies, market positioning, or project plans, assessing internal capabilities and external factors, or identifying strategic priorities and risk mitigation strategies to capitalize on strengths and mitigate weaknesses.
DMAIC is a structured problem-solving methodology used in Six Sigma projects to improve processes by defining, measuring, analyzing, improving, and controlling them. It aims to reduce defects and variations to enhance quality and efficiency.
When improving processes or enhancing quality, reducing defects and variations, or implementing data-driven and evidence-basedimprovement initiatives to optimize performance and sustain quality gains through continuous improvement and control mechanisms.
Kaizen (Continuous Improvement)
Kaizen, meaning “change for better,” is a philosophy focused on continuous improvement in all aspects of life. In business, it involves making small, incremental changes to processes, products, or services to achieve ongoing improvements in quality, efficiency, and effectiveness.
When fostering a culture of continuous improvement, empowering employees to initiate and implement changes, or optimizing workflow and operations through small and incremental improvements to drive long-term success and competitiveness in dynamic markets.
Total Quality Management (TQM)
Total Quality Management (TQM) is a management approach focused on continuous improvement, customer satisfaction, and employee involvement. It emphasizes quality at every stage of the organization’s processes and fosters a culture of excellence and accountability.
When ensuring quality and customer satisfaction, optimizing processes and performance, or promoting employee involvement and continuous learning to achieve organizational excellence and sustain competitive advantage through quality-focused practices and customer-centricity.
Six Sigma
Six Sigma is a data-driven approach to process improvement that aims to minimize defects and variations to achieve near-perfect quality. It employs statistical methods and project management techniques to identify root causes of issues and implement solutions systematically.
When reducing defects and improving efficiency, optimizing business processes and performance, or driving quality and customer satisfaction through data-driven analysis and structured improvement projects to eliminate waste and enhance organizational effectiveness.
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles.
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.
A Gemba Walk is a fundamental component of lean management. It describes the personal observation of work to learn more about it. Gemba is a Japanese word that loosely translates as “the real place”, or in business, “the place where value is created”. The Gemba Walk as a concept was created by Taiichi Ohno, the father of the Toyota Production System of lean manufacturing. Ohno wanted to encourage management executives to leave their offices and see where the real work happened. This, he hoped, would build relationships between employees with vastly different skillsets and build trust.
GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.
As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.
Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.
The PDCA (Plan-Do-Check-Act) cycle was first proposed by American physicist and engineer Walter A. Shewhart in the 1920s. The PDCA cycle is a continuous process and product improvement method and an essential component of the lean manufacturing philosophy.
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle. These are the five stages of a retrospective analysis for effective Agile project management: set the stage, gather the data, generate insights, decide on the next steps, and close the retrospective.
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.
The SMED (single minute exchange of die) method is a lean production framework to reduce waste and increase production efficiency. The SMED method is a framework for reducing the time associated with completing an equipment changeover.
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.
Six Sigma is a data-driven approach and methodology for eliminating errors or defects in a product, service, or process. Six Sigma was developed by Motorola as a management approach based on quality fundamentals in the early 1980s. A decade later, it was popularized by General Electric who estimated that the methodology saved them $12 billion in the first five years of operation.
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.
The Total Quality Management (TQM) framework is a technique based on the premise that employees continuously work on their ability to provide value to customers. Importantly, the word “total” means that all employees are involved in the process – regardless of whether they work in development, production, or fulfillment.
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework.
Gennaro is the creator of FourWeekMBA, which reached about four million business people, comprising C-level executives, investors, analysts, product managers, and aspiring digital entrepreneurs in 2022 alone | He is also Director of Sales for a high-tech scaleup in the AI Industry | In 2012, Gennaro earned an International MBA with emphasis on Corporate Finance and Business Strategy.
Discover more from FourWeekMBA
Subscribe now to keep reading and get access to the full archive.
