Mete Kilic
-
The 5W2H methodology is a structured and effective way to clearly define and analyse a problem by addressing seven key questions: What, Where, When, Who, Why, How, and How Much. By answering each of these systematically, we ensure a holistic understanding of the issue, which is essential for effective problem-solving. Let’s walk through each element
-
In case of a quality problem from the customer or internal, one of the most challenging steps is “finding the dirty batch,” which is in the early stages of 8D Problem Solving studies. Before going into the point, let’s identify the dirty batch. It is a specific group of products within a production batch that
-
You work in production, in method, or in logistic, maybe in quality ? You don’t know the processes well yet. What would you do at first if someone notified a quality problem that needs to be led by you ? Whether you know the details of relevant process or not, you can still lead a
-
FMEA (Failure Mode & Effects Analysis) was invented by the U.S. Military in the late 1940s to evaluate potential risks in production. Later, NASA used it to assess risks before long space journeys. Today? It is widely used, especially in manufacturing industries, particularly in the automotive sector. What is it? FMEA is a proactive tool
-
The 5W2H method is a widely used framework in problem-solving, quality management, and business analysis. By asking What, Where, When, Why, Who, How, and How Much, we systematically define a problem. However, there is one particular question in that which often leads to confusion: This question is “Why?” Understanding the “Why” in 5W2H At first
-
If you ask most people to guess the second word after “Quality,” they would probably say “Control.” It’s a term closely linked to quality and widely used. But what exactly is Quality Control? Is it simply a process to check whether a product meets quality standards? Quality Control In simple terms, when we produce a
-
IATF 16949:2016, the Automotive Quality Management System (QMS) standard, consists of 10 main clauses, each with multiple sub-clauses. While the standard provides detailed requirements on what needs to be done, it does not prescribe how to do it, leaving the implementation up to organizations. So, how should we structure this system within the organizations? What
-
Identifying root causes requires a huge effort from teams. However, confirming whether the identified root causes are truly the right ones can be challenging. The validation methods may vary depending on the problem type, but there are some fundamental approaches that can be applied in most cases. “So” The Art of Reverse Questioning There are
-
Root cause analysis is a core step in all problem-solving methodologies, including 8D, Six Sigma, A3, and even PDCA. The reason is simple: rather than focusing on the surface-level issue, we go straight to the origin of the problem. If we eliminate this root cause, the issue will be permanently resolved. We use various techniques
-
While the problem is the deviation between the actual status and the expectation, it is essential to identify all relevant data and direct our focus to the correct issue. In this post, we’ll explore how an incorrect problem definition can lead to undesirable outcomes. Real Life Cases Our life consists of problems, which we need
-
Have you ever wondered what “quality” really means? Is it the durability of an item, the taste of a cake, expensive things, or maybe perfection? Indeed, it’s none of those. Quality Is About Meeting Expectations At its core, quality is simply about meeting expectations, more specifically, the customer’s expectations. Think about the last time you
Mete Kilic 