5W2H is a structured problem-solving and analysis tool that involves answering seven fundamental questions: What (the issue or task), Why (why it happened), Where (location), When (timing), Who (people involved), How (process), and How Much (cost or impact). It helps systematically identify and address problems.

What industries can 5W2H be applied to?

5W2H is versatile and applies to Manufacturing (analyzing production defects), Customer Service (investigating complaints), Project Management (clarifying objectives), Healthcare (identifying process inefficiencies), and Logistics (troubleshooting delivery delays or supply chain disruptions).

5W2H Method

Solve Any Problem with 7 Questions

The 5W2H Method solves any problem with 7 simple questions: What, Who, Where, When, Why, How, and How Much. This video demonstrates how systematic questioning transforms chaotic situations into structured solutions. Watch a pizza order mix-up get analyzed and solved using the 5W2H framework, revealing root causes that quick fixes miss.

You'll learn: The 7 questions framework • How to identify root causes • Applications for work and daily life

Video Transcript

[00:00] Introduction: Beyond Giving Up

Have you ever been stuck in a situation where you are like, "Okay, this is it. It's the worst. It's over." What if I told you that instead of just giving up or ignoring the problem, you can handle it like a pro and even future-proof yourself from the same issues?

Whether you are a quality manager who wants to reduce quality defects and maximize customer satisfaction, or just someone who's looking for a better way to deal with daily life issues—this video is for you.

[00:25] The 5W2H Method Unveiled

I know you want to jump the gun and have a lot of questions about this mystery method. Ironically, that's the beauty of this method since it's based on seven questions. This 5W2H method forces you to ask key questions regarding the problem.

And when you answer them, you are much more compartmentalized and have a clear shell around which to build your decision.

[00:48] The Seven Questions

Now, let's get into the details of these questions. The next sentence might be a little bit hard to keep track of, but don't worry because by the end of this video, you'll understand them completely.

The seven questions in 5W2H are: What, Who, Where, When, Why, How, and How Much. By asking and answering these questions, you or your team can completely understand a problem or situation, make informed decisions, and even take precautions for the future.

[01:32] Question 1: WHAT

The first question you'll ask is what? And it aims to explain what the problem at hand is. Now suppose you manage a pizzeria and one day a customer calls you and says that they received the wrong order.

So what do you think the answer to "what" would be in this case? That's simple: A customer ordered a pepperoni pizza but got a vegetarian pizza instead.

[01:52] Question 2: WHO

Hopping on to the next question. Who will figure out who is being affected by this problem? In the case of your pizza place, the people who would be in this category would be the unhappy customer, the cashier who took the order, the delivery guy who will have to make another run, and finally you since you'll have to bear a loss.

[02:11] Question 3: WHERE

Next up, we'll answer where to understand the location or the context of the problem. So now we know that the problem took place at the cash counter where the cashier accidentally took the wrong order.

[02:28] Question 4: WHEN

In this game of detectives, the next clue would lie in the answer to when. You see, timing is crucial in problem solving. If you understand the timeline better, you can know at what time the problem emerged and how it evolved.

For our pizza joint, this took place around Friday rush point and it evolved into the customer receiving the wrong order.

[02:49] Question 5: WHY

And when you answer the last W, which is why, you'll finally understand why the issue occurred and what were the factors that led to its development.

In our example, the problem occurred because the cashier selected the wrong item in the register. After all, they were rushing out the orders.

[03:10] Question 6: HOW

Now that we are done with W's, let's answer how. That way, you'll understand the processes, actions, or mechanisms that led to the problem in the first place.

For us, since there was no order confirmation system in place, it led to this problem.

[03:31] Question 7: HOW MUCH

Lastly, we'll answer how much, which focuses on the measurement of the impact of this problem—like how much of this problem exists or how much is it affecting the people we discussed in the "who" section.

When we answer this for our pizza place, the impact would be the cost of a new pizza, the cost of the delivery, the added waiting period for the customer, and the potential for losing a customer.

[03:48] Benefits and Common Pitfalls

You'll be surprised about the benefits of this method. By answering all of these questions, you would have a much more structured approach to solving your problems. You and your team are always focused on the problems, you understand them completely and nothing gets overlooked.

But you should be aware of some common pitfalls because this method isn't perfect. You should remember not to over-complicate things. Stay focused on relevant information and involve the right people.

[04:09] Pro Tips for Success

However, if you follow some pro tips, you'll find it to be a real life hack. For example, you should always be precise and specific while asking the questions. You should be open-minded and consider multiple perspectives when formulating the questions.

And lastly, test them with colleagues or team members.

[04:28] Solving the Pizza Problem

For example, now that you've answered these questions, let's see how they help us solve our pizza problem. Since you know that the problem occurred because there was no verification system in place, you'll install one.

Next, you'll train your staff to handle stressful situations like rush hour much better. Lastly, you'll send your customers a free drink so that they remain loyal to your pizza joint.

[04:46] Conclusion: Beyond Work Life

This was just one example of how you can use this method to improve your work life. But the beauty of this method is that it extends to your daily life as well. And you can tackle any problem using this smart approach.

Will you be using this method for yourself or your company? Let us know if you solve any issues using it in the comments below.

Download: 5W2H Method Template

5W2H Method Template Preview

📊 5W2H DASHBOARD

Live KPI Dashboard

Real-time overview of action status, priorities, and completion rates.

🔍 5W2H METHOD

Structured 7-Question Framework

Systematic Who, What, Where, When, Why, How, How Much analysis.

Free Download

Download: 5W2H Method Template

Professional Excel template with structured 7-question framework, live dashboard, and action tracking. Start analyzing problems systematically in minutes.

📄 New to 5W2H Method? Start with the Quick Guide (PDF)

📅 Updated December 2025 – Now with live Dashboard KPIs

Download: 5W2H Method Guide and Quiz

5W2H Method Quick Guide: Get Started Fast

This guide helps you understand and apply the 5W2H method so you can analyze problems faster and make better decisions.

5W2H Method Quiz: Test Your Knowledge

Test your understanding with 10 interactive questions about the 5W2H method. Perfect for reinforcing key concepts and measuring your progress.

What is the 5W2H Method?

5W2H is a method for solving problems and analyzing situations. It stands for What, Why, Where, When, Who, How, and How much.

This method simplifies complex problems into clearer parts by asking these seven key questions. This helps organizations to understand issues better and make smart choices. In quality control, the 5W2H tool is helpful to look at defects or problems in production, which aids in finding and fixing issues more effectively.

The 5W2H method comes from early quality management efforts, especially related to Japanese and American quality movements in the 20th century. It is often used with problem-solving methods like Kaizen, Six Sigma, and Lean to enhance overall efficiency in operations.

Why Use the 5W2H Method

Every hour spent chasing the wrong root cause is wasted money. Teams that jump to conclusions often fix symptoms, not problems—and the issue returns weeks later, costing even more.

The 5W2H method reduces analysis time and prevents repeated failures, because it forces structured thinking before action. Instead of guessing, you systematically capture What happened, Why it matters, Where and When it occurred, Who is involved, How it happened, and How Much impact it caused.

Without it:

Vague problem descriptions, endless meetings, finger-pointing, and solutions that don’t stick. Internal failure costs multiply as the same issues resurface.

With it:

Clear problem boundaries, faster root cause identification, and targeted actions that solve problems permanently.

The 5W2H method is particularly valuable when Cost of Quality runs high—customer complaints, production scrap, rework, and warranty claims add up fast when problems aren’t properly understood from the start.

When to Use the 5W2H Method

Use the 5W2H method when a problem costs time and money, but the full picture isn’t clear yet.

Typical triggers are:

Customer Complaints / Incidents

When a customer reports an issue, 5W2H captures all essential details of the incident: What happened? Where did it occur? When was it noticed? Who is affected? Why does it matter? How was it detected? How much is the impact? This structured approach prevents incomplete documentation that delays resolution.

Quality Alerts

Quality Alerts require a quick, but complete documentation for effective alerting of the supply chain. 5W2H ensures no critical dimension is missed – from the physical location and timing to the business impact and detection method.

8D-Report Step D2

In the 8D-Report, Step D2 requires a precise problem definition. 5W2H provides the framework to transform vague complaints into actionable problem statements.

Process Changes

When implementing process changes, 5W2H documents the current state and expected outcomes, creating a baseline for measuring success.

Project Kick-offs

Before starting any improvement project, 5W2H clarifies scope and boundaries. It aligns team understanding and prevents scope creep by documenting what is – and isn’t – included.

The rule: If you can’t answer all seven questions clearly, you don’t understand the problem well enough to solve it.

Where to Apply the 5W2H Method

The 5W2H method is a useful tool in many business areas such as planning, finding problems, describing problems, and making processes better:

Planning:

5W2H ensures, that all parts of a project are looked at closely, from goals and resources to timeframes and expenses. This leads to practical plans that can be acted on.

Finding problems:

5W2H provides a simple way to identify issues by breaking down symptoms, areas affected, and how big the issue is, creating a clear view of the problem.

Describing problems:

5W2H goes further into details, adding measurable facts, main causes, and those impacted, which changes broad problem statements into useful insights.

Improving processes:

5W2H helps teams examine every part of a process, uncovering problems and guiding specific changes to make workflows better.

Planning

The 5W2H method changes unclear ideas into clear plans by looking at each important part of starting and carrying out a project.

In planning, “What” makes clear goals and what needs to be done, “Why” explains the project’s reason and benefits, “Who” points out team members and others involved along with their roles, “Where” finds places for activities, “When” sets up schedules and key dates, “How” describes methods and steps to take, and “How Much” figures out the budget and needed resources.

This all-inclusive method makes sure the planning is complete and answers all vital questions, which helps lower mistakes and boosts the chances of the project succeeding.

Finding Problems

In problem identification, 5W2H works as a tool that helps teams find the issues.

This method starts by figuring out who is affected by the problem, what the problem is and its symptoms, where it happens in the organization, when it shows up, why it exists (looking at main causes), how it affects operations, and how much it costs the organization in resources, time, or money. This organized method stops premature conclusions and makes sure problem identification is thorough and based on evidence.

Differences to Problem Description:

- This is phase before the problem description: the initial discovery and recognition phase where you detect that something is wrong or needs improvement
- Focuses on recognizing the existence and general nature of an issue
- Often involves noticing symptoms, anomalies, or deviations from expected outcomes
- May be triggered by data analysis, observations, complaints, or performance metrics
- Answers the basic question “Is there a problem?“
- Example: Identifying that customer complaints have increased significantly or noticing that production output is below target

Describing Problems

When describing problems, 5W2H gives a simple way to share important details clearly.

A good problem description using this method would explain who found the problem, what signs or issues were seen, where in the system or process the problem occurred, when the problem started and how often it happens, why it is seen as a problem (effect on operations), how it’s different from usual operations, and how much it affects productivity, quality, or costs. This organized way of describing problems helps all involved parties understand the issue, making it easier to solve the problems.

Differences to Problem Identification:

- This is the detailed characterization and documentation phase that follows identification
- Focuses on creating a complete and precise picture of the identified problem
- Involves gathering specific data, documenting evidence, and quantifying the issue
- Requires systematic analysis and clear communication of all problem aspects
- Answers the question “What exactly is the problem and what are its characteristics?”
- Example: Documenting that customer complaints increased 35% in the past quarter, primarily regarding delivery delays, affecting specific regions and product lines.

Improving Processes

To make processes better, 5W2H is a useful tool for both looking at current processes and creating better ones.

It helps teams figure out who is in the process and who needs to be, what steps are done and what results are wanted, where each step happens, when things are done and in what order, why each step is needed and its importance, how tasks are done now and how they might be improved, and how much time and resources are used versus what could be saved by improvements. This clear analysis finds problems, unnecessary steps, and chances for better efficiency, leading to processes that work better and are simpler.

How to Conduct a 5W2H Analysis

The 5W2H problem-solving process provides a systematic approach to tackle challenges through six key steps, from identifying the issue to monitoring solutions.

1. Identify the Issue

Before starting with 5W2H, make sure to pinpoint the issue you are facing. This might involve a complaint from a customer, a flaw in production, or a lack of efficiency in a process.

Clearly stating the issue will help you use the 5W2H framework better.

Example: A customer got the incorrect pizza with their delivery.

2. Split the Issue with 7 Questions

Next, apply the 5W2H questions to divide the issue into smaller parts. Answer every question step by step, making sure to collect relevant details.

Below is a guide on addressing each question:

2.1. What (What is the problem?)

Begin by stating the problem clearly. What was the mistake? Be exact and concentrate on the primary issue.

Example: The customer asked for a pepperoni pizza but was given a vegetarian pizza.

2.2. Why (Why did it happen?)

Find the reasons for the problem. This is important for figuring out the main cause. Ask why the issue happened and look at different factors that helped.

Example: The mistake happened because the cashier chose the wrong pizza in the system, picking a vegetarian pizza rather than a pepperoni one.

2.3. Where (Where did it occur?)

Identify where the issue took place. This might mean a particular place, team, or procedure where the problem arose.

Example: The issue happened at the cashier’s order-entry section in the restaurant’s POS (point-of-sale) system.

2.4. When (When did it happen?)

Identify the time or event when the issue took place. When was the problem first seen, and when did it begin?

Example: The error occurred when the order was made on a hectic Friday night, and it was spotted when the customer got the package.

2.5. Who (Who is involved?)

Find the people or groups linked to the issue. This should cover both those who caused the mistake and those who are influenced by it.

Example: The cashier who processed the order, the kitchen team that prepared the pizza, the delivery person who delivered the wrong item, and the customer who got the incorrect pizza.

2.6. How (How did it happen?)

Explain the steps or factors that caused the issue. How did the mistake happen, and why was it not detected at various points?

Example: The cashier picked the incorrect pizza in the POS system, and there was no checking system to identify the error before the pizza was prepared and sent out.

2.7. How Much (How much impact did it have?)

Assess the problem level. What is the issue costing in time, money, or happiness of customers? Look at both the short-term and long-term effects.

Example: The short-term cost involves making and sending the right pizza, along with the risk of losing the customer if their unhappiness is not resolved.

3. Examine the Answers

After answering all seven questions, review your answers to fully grasp the issue. Identify patterns, main reasons, and places where processes might have failed.

Advice: Utilize methods such as Root Cause Analysis (RCA) or the 5-Whys technique to explore the “Why” and “How” aspects if the issue is complicated.

4. Create Practical Solutions

Once the problem is analyzed with 5W2H, create solutions that tackle the main issues. Make sure the solutions are practical and can be acted upon, aiming to stop the problem from happening again.

Example:
Establish an order check step so that the cashier verifies the customer’s order before finishing it. Include a double-check method in the kitchen where staff confirm the pizza type before delivery.

5. Focus on Tasks and Execute Answers

Certain answers might need attention quicker than others. Focus on the effect and difficulty of execution. Tackle the most important problems first and make a schedule for working on longer-term answers.

For instance:
Now: Say sorry to the customer, give compensation, and redo the pizza with faster delivery.
Next: Begin a process to confirm orders at the register.
Later: Provide improved training for workers to avoid mistakes in order entry.

6. Monitor and Check

After solutions are put in place, keep an eye on things to make sure the problem is fixed. Check the steps now and then to find any new problems or spots that can be better.

Advice: Take input from customers and staff to improve processes and secure lasting success.

How to Combine 5W2H with Other Tools

The 5W2H works well with other quality methods :

Is-Is-Not Analysis

After 5W2H captures the basic facts, Is-Is-Not Analysis deepens the investigation by comparing where the problem occurs versus where it doesn’t. This contrast reveals patterns and narrows down possible causes.

Ishikawa Diagram

5W2H defines WHAT the problem is. The Ishikawa (Fishbone) Diagram then explores WHY it happens by brainstorming potential causes across categories like Man, Machine, Method, Material, Measurement, and Environment.

5-Why Analysis

Once 5W2H establishes the problem boundaries, 5-Why drills down to the root cause by repeatedly asking “Why?” until the fundamental issue is uncovered. Clear 5W2H input leads to focused 5-Why questioning.

PDCA Cycle

5W2H fits into the Plan phase of PDCA, where understanding the current situation is essential. The structured questions ensure comprehensive planning before Do, Check, and Act phases.

Action Management

After analysis, 5W2H answers translate directly into action items: Who will do What, by When, and How? This ensures corrective actions are specific and trackable.

SIPOC Diagram

For process-related problems, start with SIPOC to map Suppliers, Inputs, Process, Outputs, and Customers. Then use 5W2H to investigate specific issues within that process context.

Principles of the 5W2H Method

The 5W2H principles focus on asking questions and analyzing information well:

Ask the Right Questions

5W2H works well when we ask the seven important questions clearly:

What: State what the issue or problem is.

Why: Look into why the issue is happening (possible main causes).

Where: Find out where the issue is occurring (exact place or process).

When: Figure out when the problem happened or was observed.

Who: Identify who is involved or affected by the issue.

How: Examine how the problem appears or the process connected.

How Much: Evaluate the impact of the problem (cost, time, resources).

Benefits of the 5W2H Method

Focused and Fast Decision-Making

5W2H helps teams to concentrate on important information, resulting in faster and more effective decision-making.

By going through the seven questions carefully, this method limits the reasons and fixes, cutting down on lost time and work in solving problems.

Complete Problem Solving

The 5W2H method makes sure every aspect is considered. By looking at different sides of a problem, it promotes a complete way to find solutions.

This idea ensures the main issue is found, and fixes are thorough, not just quick solutions.

Understanding with Organized Questions

5W2H helps to make things clear by dividing problems into smaller parts. By inquiring What, Why, Where, When, Who, How, and How much, it offers a simple way to grasp every part of a situation.

This organized questioning improves communication and allows for a fuller insight into the problem.

Flexibility for Different Issues

The 5W2H method is flexible and can be used in many fields and situations. It works well whether dealing with product flaws, customer issues, or process problems. This approach meets the specific needs of the issue and gives teams a straightforward way to move ahead.

Preventive Thinking

5W2H is not only about solving present problems; it also promotes a preventive thinking by pushing for a detailed look at “Why” issues happen. This results in finding root causes and creating answers that stop similar problems from happening again.

Team Work and Involvement

5W2H promotes participation from all important parties. By addressing each question from various angles, it supports teamwork among groups and sections. This participation leads to a more complete solution, utilizing different skills and viewpoints.

Limitations of the 5W2H Method

Takes Time

The 5W2H method can take a lot of time, especially when there is a lot of data to collect and look at. If not handled well, teams may get stuck in the details, making decisions slower and pushing back the solution rollout. This is more common with complicated problems where each of the seven questions (What, Why, Where, When, Who, How, and How Much) needs a lot of digging and checking.

To fix this, it’s important to focus on the key parts of the problem, make data collection easier, and keep the process well-organized to prevent extra delay.

Needs Experience

The success of 5W2H relies heavily on the team’s knowledge and skills. Skilled professionals who know the method can quickly ask good questions and understand the answers well. But teams with less skill might only do a surface-level analysis or not look deeply into the issue. New users may find it hard to see the details of root cause analysis or not correctly link each “W” and “H” to the problem.

To fix this issue, organizations should provide training to help team members learn the method better and use it well. Also, having experts involved in the process can improve the analysis quality.

Subjectivity

Even though 5W2H tries to give clear insights by highlighting main facts, the responses can still be shaped by the views of the participants in the analysis. Various team members might see questions such as “Why is this happening?” or “Who is in charge?” differently based on their roles, experiences, or biases. This subjectivity can cause mixed interpretations of the main issue, making it hard for the team to agree on what the real problem is.

To tackle subjectivity, it is crucial to make sure that the data and evidence collected are as objective as possible. Promoting open talks, involving diverse team members, and focusing on factual details can help reduce this issue. Implementing additional tools like data analysis or root cause analysis methods (like 5 Whys or Fishbone diagrams) can also decrease bias in the evaluation.

Risk of Making Things Too Complicated

Another drawback is the chance of making the analysis too complicated. The 5W2H framework promotes being thorough, but there is a risk of diving into unneeded details. This can create a big analysis that loses sight of the main points, making it harder to see the key parts of the issue. Overcomplication can divert the team from important matters and cause decision paralysis, where having too much information leads to confusion instead of understanding.

To prevent overcomplication, it’s vital to keep a clear focus on the specific issue. Teams should highlight the most important problems and simplify the process by focusing on relevant data and facts.

Lack of Detail in Complex Issues

Sometimes, the 5W2H method may not fully address the complexity of certain problems. Although it serves as a decent initial step for analysis, it often requires additional methods like Root Cause Analysis (RCA), Failure Mode and Effects Analysis (FMEA), or statistical methods to grasp complicated issues completely. Using only 5W2H for complex problems can result in partial findings or inadequate solutions.

For intricate issues, using 5W2H along with other approaches provides a stronger and more thorough evaluation.

Challenges in Scaling

5W2H is good for certain specific issues, but using it across many departments or locations can be hard. Big problems that have many parts need better systems to manage the seven questions. Also, getting different teams or stakeholders from various areas to have a common view on the issue can be tough.

In bigger companies, it’s usually important to use 5W2H alongside other problem-solving methods that can scale well, and to keep communication clear when working with several teams.

Best Practice of the 5W2H Method

To get the most from the 5W2H tool, keep in mind these tips and tricks to make your analysis easier and lead to better results:

5W2H Method Example: Pizza Delivery

Issue:

A client calls to say they got the wrong pizza in their delivery. Here is how the 5W2H method can be used to look into and fix the problem:

1. What (What is the problem?)

The customer wanted a big pepperoni pizza, but got a vegetarian pizza instead.

Analysis:

The problem is that what the customer asked for does not match what was sent. This shows there was a mistake in taking the order or making the pizza.

2. Why (Why did it happen?)

After looking into the issue, it was found that the mistake happened due to poor communication between the cashier and the kitchen team. The cashier entered the wrong type of pizza into the system by mistake. Consequently, the kitchen staff made the order based on this wrong input.

Analysis:

The main cause of the issue is the wrong pizza type entry, which resulted in the wrong order being made. This also suggests there might be insufficient checks before the order is processed for preparation.

3. Where (Where did it occur?)

The mistake occurred at the order entry point, when the cashier wrongly chose the vegetarian pizza instead of the pepperoni pizza in the POS system. This error was not found until the customer got their delivery.

Analysis:

Identifying the problem in the order entry process allows for correcting actions to ensure orders are taken and checked correctly.

4. When (When was the problem noticed?)

The problem was seen when the customer got the pizza and opened the box to see the incorrect order. The customer quickly called the restaurant to tell them about the error.

Review:

The mistake was not detected during the stages of making or delivering the order, which shows there was no system to confirm that the right pizza was prepared and sent.

5. Who (Who is involved?)

The cashier that took and put in the order.
The kitchen workers that made the pizza from the wrong order.
The delivery driver that brought the wrong order to the buyer.
The customer that got the wrong pizza.

Review:

The mistake includes several stages in the process, but the main duty falls on the cashier who put the order in the system incorrectly.

6. How (How did the issue happen?)

The problem happened due to the cashier picking the incorrect pizza in the POS system. There was no method established to confirm the order information before it was forwarded to the kitchen. Furthermore, both the kitchen staff and the delivery driver failed to check the order against what the customer asked for.

Analysis:

The absence of an order confirmation system let the error slip through different phases, from entering the order to delivering it.

7. How Much (How much impact did it have?)

- Customer Reaction: The customer feels annoyed and unhappy, which might result in a bad review or loss of future sales.
- Internal Effects: The restaurant has to create and send out the right pizza again, which means extra costs for ingredients, staff, and delivery.
- Expenses: Fixing the problem will involve paying for a new pizza and its delivery, likely costing between $15 and $30, based on where it is and what kind of pizza it is.

Review:

Even though the expense of fixing this issue seems small for one time, making mistakes like this often can hurt the restaurant’s image and raise costs in the long run.

5W2H Method in Pizza Production

Summary of Action

From this 5W2H analysis, the restaurant can take these steps to fix the current issue and avoid it later:

1. 1. Immediate Action:

Say sorry to the customer, make the right pizza, and give them a free item or a discount for their next order to make up for the problem. Make sure the new pizza gets to them fast.

2. Process Improvement:

- - - - Order Confirmation:

Set up a way for the cashier to check the order details with the customer before it’s confirmed in the POS system, either by talking in person or sending a confirmation for online orders.

- - - - Kitchen Verification:

Start a system in the kitchen where staff check the printed order with the pizza being made.

- - - - Final Check:

Have the delivery driver or a staff member review the order before it leaves the restaurant to confirm it matches what was ordered.

3. Training:

Teach staff to slow down during busy times and focus on taking orders correctly. This can include stressing the need to double-check orders at each step of the process.

5W2H Method – Real-World Examples

1. Pizza Production

Wrong Pizza

Complete 5W2H method example from the pizza industry. This filled-out template demonstrates how to analyze a customer complaint about receiving the wrong pizza order, including all 7 questions (What, Why, Where, When, Who, How, How Much) and a corrective action plan with preventive measures.