Articles

Businesses face all kinds of hurdles slowing progress and threatening success. From grindingly slow workflows to quality glitches, these problems spread damage far if left unaddressed.

But with the right problem-solving styles, companies can pinpoint what’s causing trouble and implement fixes well.

One such method earning its stripes across industries everywhere is “Is/Is Not Analysis”.

It provides a methodical way for teams to sharply define issues while excluding what they’re not.

Doing so eliminates vagueness, prevents scope creep, and guarantees efforts target the actual problem.

Whether handling complex engineering puzzles or streamlining company processes, Is/Is Not Analysis has time and again proven hugely useful in my problem-crushing toolkit.

Key Highlights

• A thorough understanding of what the Is/Is Not Analysis is and how it fits into the broader problem-solving framework.
• The numerous benefits of using this technique, such as enhanced focus and clarity, improved team alignment, effective scope management, better communication, and robust decision-making.
• A step-by-step guide on how to conduct an “Is/Is Not Analysis”, from describing the problem to formulating a concise problem statement.
• Insights into the wide-ranging applications of this analysis across various domains.
• An example demonstrating the application of the Is/Is Not Analysis in a manufacturing context, addressing the issue of machine downtime, and highlighting the process of comparative analysis and problem statement formulation.
• Industry-specific terminology, technical insights, and best practices drawn from my extensive experience working with Lean Six Sigma methodologies.

What is an Is/Is Not Analysis?

The Is/Is Not Analysis is a powerful problem-solving technique that brings clarity and focus to complex situations.

This method is an invaluable asset in my toolkit, enabling me to tackle intricate challenges across a wide range of industries and domains.

Problem-solving technique

The Is/Is Not Analysis is a systematic approach that guides teams through the process of precisely defining the scope of a problem.

Breaking down the issue into two distinct components – what the problem “is” and what it “is not” – allows you to isolate the core elements that require attention while filtering out extraneous factors that may distract or derail your efforts.

Scope definition with Is/Is Not Analysis

One of the primary benefits of this analysis is its ability to establish clear boundaries and parameters around the problem at hand.

By explicitly stating what falls within the scope of the issue and what lies outside of it, you can prevent scope creep and ensure that your team remains focused on the most relevant aspects.

This not only streamlines the problem-solving process but also optimizes the allocation of resources, directing them toward the areas that truly matter.

Structured problem-solving approach

The Is/Is Not Analysis is a structured and systematic approach that follows a well-defined set of steps. It begins with a detailed description of the problem, followed by the identification of what the problem “is” and what it “is not”.

This process involves gathering data, analyzing information, and leveraging templates to facilitate a comprehensive understanding of the situation.

DMAIC

This problem-solving technique seamlessly integrates into the widely adopted DMAIC (Define, Measure, Analyze, Improve, Control) methodology, which is a cornerstone of Lean Six Sigma practices.

The Is/Is Not Analysis plays a crucial role in the “Define” phase, where it helps teams precisely articulate the problem they are addressing, setting the stage for subsequent phases of measurement, analysis, improvement, and control.

Is vs. Is Not Matrix

To facilitate the analysis, a commonly used tool is the “Is vs. Is Not” matrix, which is a tabular representation that contrasts the elements that fall within the scope of the problem (“Is”) with those that do not (“Is Not”).

This visual aid not only enhances understanding but also serves as a reference point throughout the problem-solving journey, ensuring that the team remains aligned and focused on the defined objectives.

Benefits of Using an Is/Is Not Analysis

The Is/Is Not Analysis can have on problem-solving endeavors.

This versatile technique offers a multitude of benefits that not only enhance the effectiveness of the problem-solving process but also foster a more collaborative and efficient team dynamic.

Focus and clarity

One of the primary advantages of the Is/Is Not Analysis is its ability to bring laser-sharp focus and clarity to even the most complex challenges.

By meticulously delineating what the problem is and what it is not, this approach eliminates ambiguity and ensures that all team members are operating with a shared understanding of the issue at hand.

This shared clarity of purpose is a powerful catalyst for efficient and targeted problem-solving efforts.

Team alignment

In my experience, one of the biggest hurdles in tackling complex problems is achieving true alignment among team members.

The Is/Is Not Analysis serves as a unifying force, fostering a collaborative environment where everyone is working towards the same clearly defined objectives.

Scope management

Effective scope management is crucial in any problem-solving endeavor, as it prevents resources from being diluted across irrelevant areas.

The Is/Is Not Analysis excels in this regard, as it establishes precise boundaries around the problem, delineating what aspects fall within the scope and what lies outside of it.

Communication enhancement

Clear and effective communication is the lifeblood of any successful problem-solving initiative. By providing a structured framework for defining the problem, the Is/Is Not Analysis enhances communication within the team and across stakeholder groups.

The visual representation of the problem’s scope, often through the use of matrices or templates, facilitates a common understanding and streamlines the dissemination of information, ensuring that everyone is working towards the same goals.

Problem definition

At the heart of the Is/Is Not Analysis lies a robust problem definition process.

By breaking down complex issues into manageable components and identifying the specific characteristics and boundaries of the problem, this technique lays a solid foundation for comprehensive problem-solving efforts.

A well-defined problem statement is a critical first step towards finding effective solutions.

Boundary setting

In addition to defining the problem’s scope, the Is/Is Not Analysis also plays a crucial role in setting boundaries for the problem-solving effort.

By explicitly stating what falls outside the scope of the issue, this technique helps teams avoid getting sidetracked by tangential or irrelevant factors, ensuring that their focus remains unwavering on the core problem at hand.

Risk identification

Another valuable benefit of the Is/Is Not Analysis is its ability to identify potential risks or areas that might otherwise be overlooked.

This proactive approach allows for the development of effective risk mitigation strategies, enhancing the overall success of the initiative.

Decision-making

Informed decision-making is a critical component of any successful problem-solving effort. The Is/Is Not Analysis supports this process by providing a clear and comprehensive picture of the situation.

By understanding what is within the scope and what lies outside of it, teams can make well-informed decisions regarding resource allocation, action prioritization, and appropriate solutions.

Continuous improvement

The Is/Is Not Analysis is not a one-time exercise but rather a continuous improvement tool. As teams gain insights and lessons learned throughout the problem-solving journey, they can refine and update their understanding of what the problem “is” and “is not”.

This iterative process allows for ongoing optimization and ensures that solutions remain relevant and effective over time.

Documentation

Finally, the Is/Is Not Analysis provides a documented record of the problem’s scope and boundaries. 

This documentation serves as a valuable reference not only for the current problem-solving initiative but also for future projects or audits.

It ensures that the rationale behind decisions and the parameters of the problem are captured, facilitating knowledge transfer and enabling continuous learning within the organization.

How to Conduct an Is/Is Not Analysis

While the specifics may vary depending on the nature of the problem and the industry, there is a well-established framework that has proven effective time and time again.

Describe the problem

The first step in any successful Is/Is Not Analysis is to provide a detailed description of the problem at hand. This involves more than simply stating what the issue is; it requires a comprehensive understanding of the symptoms, consequences, and impact of the problem.

During this stage, it is crucial to gather as much relevant data and information as possible, ensuring that the problem is thoroughly documented and free from assumptions or proposed solutions.

Identify the “Is”

With a clear understanding of the problem in place, the next step is to identify what the problem “is”.

This involves documenting the specific characteristics, actions, behaviors, or outcomes that are considered problematic.

Template-based analysis with Is/Is Not Analysis

To facilitate this process, I often recommend the use of templates or matrices that allow teams to visually organize and contrast the “Is” and “Is Not” elements.

One popular approach is the “Is vs. Is Not” matrix, which provides a tabular representation that delineates the problem’s scope.

These templates enhance understanding and serve as a reference point throughout the analysis, ensuring consistency and alignment among team members.

Identify the “Is Not”

Once the “Is” elements have been defined, it is equally important to identify what the problem “is not”.

This step involves considering what one would expect to happen in the absence of the problem, as well as determining the locations, timeframes, and conditions where the issue does not occur.

Compare and contrast

With the “Is” and “Is Not” elements clearly defined, the next step is to compare and contrast the information collected.

This comparative analysis can reveal patterns, inconsistencies, or discrepancies that may point to potential root causes or contributing factors. It is during this stage that the true value of the Is/Is Not Analysis becomes apparent, as teams can begin to pinpoint the areas that require the most attention.

Data analysis with Is/Is Not Analysis

Throughout the Is/Is Not Analysis process, data plays a crucial role in informing and guiding the team’s efforts.

Narrow down the scope

Armed with the insights gained from the comparative analysis and data analysis, teams can begin to narrow down the scope of the problem.

This may involve discarding certain aspects that are not central to the issue or focusing on areas that have the most significant impact.

The goal is to create a refined view of the problem that can be effectively addressed through targeted solutions.

Formulate the problem statement with Is/Is Not Analysis

The culmination of the Is/Is Not Analysis process is the formulation of a concise and well-defined problem statement. This statement should incorporate all relevant “Is” and “Is Not” factors while being specific, measurable, and verifiable.

A clear problem statement sets the boundaries for what will (and will not) be addressed in the subsequent problem-solving efforts, ensuring that teams remain focused and on track throughout the journey.

Applications of Is/Is Not Analysis

This versatile technique has proven its value time and again, transcending boundaries and demonstrating its applicability in numerous contexts.

Project management

The Is/Is Not Analysis is an invaluable tool in the realm of project management.

By clearly defining the scope of a project and delineating what tasks and objectives are included (and excluded), this technique ensures that resources are allocated effectively and that efforts remain focused on the most critical elements.

Whether managing large-scale initiatives or smaller-scale endeavors, the Is/Is Not Analysis provides a structured framework for aligning stakeholders, setting boundaries, and mitigating the risk of scope creep.

Business analysis

In the dynamic world of business, organizations often face complex challenges that require a deep understanding of the underlying issues.

The Is/Is Not Analysis is a powerful ally in this regard, enabling business analysts to define precisely the scope of a problem or opportunity.

Product development with Is/Is Not Analysis

Whether developing tangible products or crafting innovative services, the Is/Is Not Analysis can play a crucial role in defining requirements and setting boundaries.

Quality management

By defining what constitutes quality (and what does not), this technique provides a solid foundation for developing effective quality control processes and procedures.

Whether assessing the quality of a product, service, or process, the Is/Is Not Analysis ensures that efforts are targeted and that resources are allocated appropriately, ultimately driving continuous improvement and customer satisfaction.

Requirements gathering

Effective requirements gathering is critical to the success of any project or initiative, and the Is/Is Not Analysis is an invaluable tool in this regard.

Root cause analysis and Is/Is Not Analysis

When faced with complex problems, identifying the root cause is often the most challenging and critical step.

The Is/Is Not Analysis provides a structured approach to unraveling these intricacies, by systematically separating the core issues from peripheral factors.

Environmental impact assessment

Companies must carefully consider the potential impact of their operations and projects on the natural world.

The Is/Is Not Analysis can be a powerful tool in this regard, enabling teams to clearly define the scope of an environmental assessment and delineate what factors should be considered.

Conflict resolution

Conflicts, whether interpersonal or organizational, often stem from a lack of clear understanding and alignment.

The Is/Is Not Analysis can be a valuable asset in resolving such conflicts by providing a structured framework for defining the issues at hand and separating them from extraneous factors.

By clarifying what the conflict “is” and what it “is not”, teams can focus their efforts on addressing the core points of contention, facilitating effective communication, and paving the way for resolution.

Goal setting with Is/Is Not Analysis

Whether setting personal or organizational goals, the Is/Is Not Analysis can be a powerful tool for ensuring clarity and focus.

Defining what goals should be pursued (and what should be excluded), individuals and teams can align their efforts and allocate resources effectively.

Personal development

Beyond its applications in professional settings, the Is/Is Not Analysis can also be a valuable tool for personal growth and development.

This structured approach can help individuals prioritize their efforts, overcome obstacles, and achieve their desired outcomes more effectively.

Lean Six Sigma

This technique aligns perfectly with the core tenets of these philosophies, such as continuous improvement, waste elimination, and data-driven decision-making.

An Example of Is/Is Not Analysis for Machine Downtime

To illustrate the practical application of the “Is/Is Not Analysis”, let us consider a real-world example from the manufacturing sector.

In this scenario, a company is grappling with the issue of unexpected machine downtime, which is negatively impacting productivity and delivery times.

Problem description

The initial step in the Is/Is Not Analysis is to provide a detailed description of the problem. In this case, the issue is unscheduled machine downtime, which results in machines stopping unexpectedly and requiring maintenance.

This downtime is reported to occur specifically on Line 1, which handles a portion of the production process.

“Is” analysis

Next, the team identifies the “Is” elements of the problem. They note that the machine downtime is occurring on Line 1, particularly during the third shift (11 PM to 7 AM).

“Is Not” analysis

In contrast, the team observes that the downtime is not occurring on Lines 2 and 3, indicating that the issue may be isolated to factors unique to Line 1, such as equipment, personnel, or processes.

Comparative analysis

By comparing and contrasting the “Is” and “Is Not” elements, the team can start to pinpoint potential root causes.

For instance, the fact that the issue is specific to Product A and not Products B or C could indicate that the problem is related to the machinery’s configuration, the complexity of Product A, or the raw materials used.

Problem statement formulation

Armed with these insights, the team can formulate a concise and well-defined problem statement:

During the third shift, Line 1 experiences an increase in machine downtime, specifically when running Product A, leading to production delays.

This issue does not occur during the first or second shifts, nor does it affect Lines 2 and 3 when running Products B or C”.

Next steps: Root cause analysis

With a clear problem statement in place, the team can now proceed to a focused root cause analysis, investigating potential factors such as:

• Specific differences in the setup for Product A versus Products B and C
• Environmental and operational conditions of Line 1 during the third shift
• Training, expertise, and fatigue levels of third-shift staff compared to other shifts

Conclusion

Is/Is Not Analysis has proven its worth across countless industries and uses. Whether handling complex engineering puzzles, smoothing company workflows, or fueling constant upgrades, it provides an organized style framing issues while distinguishing main problems from extra factors.

As you start leveraging “Is/Is Not Analysis”, remember to embrace an organized, fact-based method. Foster teamwork and agreement between all involved. Also, stay committed to constant learning and perfecting your approach.

With determination and truly grasping this mighty technique, you too can break into new levels of problem-solving success. You’ll power transformative change within your work or personal goals.

My hope is you feel equipped to maximize every tool in your toolkit. With Is/Is Not Analysis helping sharpen your problem-solving focus, countless opportunities now come clearly into view. Take what you’ve learned and change the game!