What Are the New 7 QC Tools and How Do They Improve Planning?

Quality management has long relied on the original "Seven Basic Tools" for data analysis and problem solving. However, when it comes to planning, organizing complex information, and preventing future problems, a different set of methods is needed. This is where the New 7 QC Tools come in.

Developed and promoted by the Union of Japanese Scientists and Engineers (JUSE), these seven management and planning tools help teams transform verbal data into clear structures, prioritize actions, and design robust plans before problems occur.

What It Is

The New 7 QC Tools (also known as the Seven Management and Planning Tools) are a set of diagram-based techniques designed to organize qualitative data, clarify complex relationships, and support strategic decision-making. Unlike the original QC tools, which focus on numerical data and process control, these tools are used primarily in the planning phase to:

• Organize unstructured ideas
• Identify root causes and relationships
• Sequence tasks and dependencies
• Anticipate and mitigate risks

The official JUSE set consists of the following seven methods:

1. Affinity Diagram – Groups large amounts of verbal data into natural clusters.
2. Relations Diagram – Clarifies cause-and-effect relationships among factors.
3. Tree Diagram – Breaks down broad goals into specific, actionable tasks.
4. Matrix Diagram – Shows the strength of relationships between two sets of items.
5. Matrix Data Analysis – Uses numerical data within a matrix to prioritize (often with a prioritization matrix).
6. Process Decision Program Chart (PDPC) – Maps possible outcomes and countermeasures for a plan.
7. Arrow Diagram – Schedules tasks with dependencies, similar to a PERT/CPM chart.

How It Works: Steps and Logic

Each tool has a specific purpose, but they are often used sequentially in a planning workflow:

• Affinity Diagram: Collect ideas (e.g., from brainstorming), write each on a card, and sort them into groups based on natural affinity—no forced logic.
• Relations Diagram: Draw arrows between factors to show which ones are causes and which are effects. Count arrows to identify the most influential drivers.
• Tree Diagram: Start with a goal on the left, then ask "What is needed to achieve this" at each level, moving from means to ends until tasks are concrete.
• Matrix Diagram: Create a two-dimensional grid (e.g., requirements vs. solutions). Use symbols like ◎ (strong), ○ (moderate), and △ (weak) to rate relationships.
• Matrix Data Analysis: When the matrix contains numeric scores, multiply weights and ratings to calculate a weighted total for each option.
• PDPC: Draw a flow from the current state to the desired outcome. For each step, ask "What could go wrong" and branch off with countermeasures.
• Arrow Diagram: List all tasks, determine precedence (what must finish before what starts), and draw nodes and arrows to find the critical path.

A Worked Illustrative Example

Example data (illustrative only). A small team wants to improve customer satisfaction. They use three tools in sequence.

Step 1 – Affinity Diagram: They brainstorm 20 complaints and group them into three clusters: "Response Speed," "Product Quality," and "Staff Attitude."

Step 2 – Relations Diagram: They place the three clusters plus "Complaint Volume" on a board. Arrows show that "Response Speed" and "Product Quality" both drive "Complaint Volume," and "Staff Attitude" influences "Response Speed." Counting arrows, "Response Speed" has the most outgoing arrows, so it is the primary driver.

Step 3 – Tree Diagram: The goal "Reduce Response Time" is broken into: "Hire one more support agent," "Create a ticket-routing script," and "Train staff on escalation rules." Each task is now specific and assignable.

Step 4 – PDPC: For the task "Hire one more agent," the team asks "What if we cannot recruit in time?" The countermeasure is "Cross-train two existing staff as backup." This branch is added to the plan.

Step 5 – Arrow Diagram: The team lists tasks: A (write job description), B (post ad), C (interview), D (train new hire). They find that A→B→C→D is the critical path of 6 weeks, while staff training (E) can run in parallel.

Common Pitfalls

• Using the wrong tool: Do not use an affinity diagram when you already have clear categories; use a tree diagram instead.
• Forcing relationships: In relations diagrams, draw arrows only when a genuine cause–effect link exists, not to make the diagram look complete.
• Skipping the "why" in PDPC: The PDPC is only useful if the team seriously considers failure modes at each step.
• Ignoring the critical path: In arrow diagrams, resources should be allocated to tasks on the critical path first.

Closing

The New 7 QC Tools are not a replacement for the original seven—they are a complementary set designed for the messy, verbal, and forward-looking work of planning. Whether you are designing a new process, launching a product, or reducing risk, these JUSE-endorsed methods give your team a structured path from vague ideas to concrete action.

To get started with ready-made templates and step-by-step guidance, try the free New 7 QC Tools application at: https://www.6sq.com/tools/new_qc7/