Unclear Issues and Entangled Relationships? —— When and How to Use the New QC Seven Tools, Explained in One Article
The most common awkward situation in quality meetings is not the lack of data, but the fact that even with data plastered all over the walls, everyone still argues without reaching a conclusion: customer complaints have clearly increased, but sales blame quality, quality blames design, design blames suppliers, and after going around in circles, the problem remains unresolved. The old seven tools—check sheets, stratification, Pareto charts, fishbone diagrams, histograms, scatter diagrams, and control charts—are adept at handling "visible data," but many quality issues are stuck on "unclear relationships": What are the various demands behind customer complaints? What is the root cause of inter-departmental disputes? What failure points need to be addressed before a new project goes live? These questions don't have precise numbers to calculate, yet they genuinely determine the direction of quality management.
The new QC seven tools—affinity diagrams, relations diagrams, system diagrams, matrix diagrams, matrix data analysis, process decision program charts (PDPC), and arrow diagrams—are designed for such issues. They don't aim for precise calculations but rather organize vague, scattered, and intertwined verbal information into visible structures. When used correctly, a quality meeting can transform from "two hours of arguing" to "half an hour of decision-making."
1. Division of Labor Between the Old and New Seven Tools: One for Data, One for Relationships
The old seven tools address "occurred and quantifiable" issues: how many nonconformities, which process has the most defects, whether the process is stable—the answers are hidden in the numbers. The new seven tools, on the other hand, address "unclear and planning-related" issues, characterized by three features:
- Information is verbal rather than numerical. Customer complaint texts, employee improvement suggestions, and lists of audit findings are all scattered sentences that need to be categorized before analysis.
- Factors are intertwined. Behind a problem, there may be seven or eight causes, each influencing the others, making it impossible to draw a clear single chain.
- Goals are future-oriented. It's not about investigating what has already gone wrong but about preventing risks and planning for what hasn't started yet.
In short, the old seven tools answer "what happened," while the new seven tools answer "what is the relationship between these issues and what should be done next." They are not substitutes but complements—first, use quantification tools to confirm the facts, then use structured tools to clarify the relationships. This is the most practical way to use the new seven tools.
2. Understanding the Seven Tools in One Table
The new seven tools may sound intimidating, but each tool addresses a specific problem:
| Tool | One-Sentence Purpose | Typical Scenario |
|---|---|---|
| Affinity Diagram | Categorize scattered opinions into several themes | Collecting customer complaints and employee suggestions, categorizing dozens of opinions into four or five themes |
| Relations Diagram | Clarify causal chains among multiple factors, identify the root cause | A problem with seven or eight intertwined causes |
| System Diagram | Break down goals into specific actions | Expanding "reduce customer complaints" into actionable strategies |
| Matrix Diagram | Match two sets of elements to find key intersections | Aligning customer needs with product characteristics to identify key control items |
| Matrix Data Analysis | Quantitatively rank multiple indicators to highlight the main conflict | Evaluating multiple solutions based on multiple criteria to select the best one |
| PDPC | Simulate potential issues in a process and prepare countermeasures | Risk simulation before the launch of new processes, production lines, or projects |
| Arrow Diagram | Sequence activities and identify the critical path | Project schedule management to determine which lines cannot be delayed |
Remember a simplified mnemonic: Use an affinity diagram for unclear issues, a relations diagram for tangled causes, a system diagram for unexpanded goals, a matrix diagram for unmatched elements, PDPC for fear of errors, and an arrow diagram for fear of delays. In daily quality management, the affinity diagram and the relations diagram are used most frequently. Master these two first, and you can cover 80% of the scenarios.
3. An Example: Customer Complaints Double, How to Move from "Arguing" to "Deciding"
In an electronics company, customer complaints doubled within a month. During the quality meeting, each department had its own take: sales blamed unstable quality, quality blamed poor packaging, logistics blamed rushed deliveries, and after two rounds of arguments, no conclusion was reached. The quality manager did not rush to take sides but led the team through three steps.
Step 1: Categorize with an affinity diagram. Copy each of the sixty-plus customer complaints from the past two months onto cards, without editing or judging, and group them by content similarity. The complaints were finally categorized into four themes: delayed delivery, damaged packaging, poor communication, and functional defects. Sixty-plus complaints were instantly reduced to four themes, making the focus of the debate clear for the first time.
Step 2: Clarify causal relationships with a relations diagram. Write the four categories of problems along with scheduling, logistics, packaging standards, inspection, and order information transmission on the diagram, and connect them with arrows to show causal relationships. During the connection process, everyone discovered that "lack of packaging standards" was behind both damaged packaging and functional defects, and "order information transmitted by phone without system records" was behind both delayed delivery and poor communication. The two root causes became evident, making it clear who was responsible and what needed to be changed.
Step 3: Assign responsibilities with a matrix diagram. Use a "problem—responsible department" matrix to confirm each task: the technology department to establish packaging standards within two weeks, the planning department to launch an order information sharing form within a month, and the quality department to add pre-shipment packaging checks. After using these three diagrams, the meeting shifted from mutual blame to task assignment, and customer complaints dropped by 60% two months later.
4. Five Steps to Implementation
Step 1: Determine whether to use the new tools. Are you dealing with numerical data or verbal information? Is the issue about investigating what has already happened or preventing what might happen? The new seven tools are only appropriate for the latter. Don't use an affinity diagram to handle issues that a Pareto chart can clarify.
Step 2: Start with two diagrams. Master the affinity diagram for categorization and the relations diagram for causal relationships before expanding to the system diagram and matrix diagram. Use PDPC and arrow diagrams when you encounter project scheduling.
Step 3: Use cards and whiteboards, draw first, then revise. The value of the new seven tools lies in the discussion process itself, not in getting it right the first time. Cards can be repositioned, and arrows can be redrawn. Making mistakes is normal, and the process of drawing is a way for the team to align.
Step 4: Use in conjunction with the old seven tools. First, use Pareto charts and fishbone diagrams to lock in data facts, then use relations diagrams and matrix diagrams to clarify relationships, and finally, use system diagrams to expand strategies. Combining the old and new tools is essential to move from "identifying the problem" to "solving the problem."
Step 5: The diagram is just a process; action is the goal. After discussing each diagram, it must be converted into an action plan: what to do, who is responsible, when to complete, and how to verify. Diagrams that do not lead to action are merely decorative.
5. Three Common Misconceptions
Misconception 1: Using all seven tools at once. The value of the new seven tools lies in selecting the right one, not in using all of them. Overloading a meeting with three diagrams will inevitably lower the quality of the discussion; addressing one core issue at a time is the correct approach.
Misconception 2: Treating the diagram as the deliverable. The most common pitfall is archiving the diagram while the problem remains unsolved. The output of the diagram must be tied to specific actions and responsible individuals; otherwise, it becomes another round of "form-filling."
Misconception 3: Pre-assigning groups in the affinity diagram. Categorization should be based on the content similarity of the information, not on departmental positions or leadership intentions. Pre-assigning categories will distort the subsequent diagrams.
The essence of the new seven tools is to move scattered information from the minds of a group onto a single diagram, making relationships visible and responsibilities clear. Data issues are handled by the old seven tools, and relationship issues by the new seven tools—selecting the right tool is key to moving quality meetings from "arguing" to "deciding."
The old seven tools handle data, the new seven tools handle relationships; categorize first, then connect, and finally assign responsibilities. Selecting the right tool is more important than using all of them.
Knowledge code: 5.2.4
Version: v20260822
Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic knowledge, methodologies, and practical tools for quality management professionals, helping enterprises continuously improve their quality capabilities.