The 7 Management and Planning Tools: The "New" Quality Tools Explained

By Linh Ngo · Updated Oct 10, 2026

The seven management and planning tools are a set of visual techniques for organizing ideas, untangling causes, building plans, and heading off risks before a project starts. Also called the seven new QC tools, they are the affinity diagram, interrelationship digraph, tree diagram, matrix diagram, prioritization matrix, process decision program chart (PDPC), and activity network diagram.

If the seven basic quality tools are for analyzing numbers, these seven are for the fuzzy work that comes before the numbers. They help a team decide what the problem really is, break a goal into tasks, pick between options, and think through what could go wrong. Nothing here needs statistics software. You need sticky notes, a big wall, and a group willing to stand up for an hour.

What are the seven management and planning tools?

The seven management and planning tools are language-based (not number-based) planning techniques that teams use to handle complex, ambiguous problems. Where a control chart or histogram works on measured data, these tools work on opinions, ideas, dependencies, and uncertainty, which is what most managers face at the start of a project.

They're often called the "new" quality tools to separate them from the older seven basic tools. The name stuck even though the set is decades old. According to a Brock University summary of the tools that cites Mizuno (1988), the set came out of a Japanese committee working on new quality control techniques, which proposed the tools in 1976. The same page, citing Nayatani and colleagues (1994), says the Committee for Developing New QC Tools was dissolved in 1978 and reconstituted as the Seven New QC Tools Research Group, and that the first symposium on the tools was held in 1979. The English-language reference most people cite is Shigeru Mizuno's edited book Management for Quality Improvement: The 7 New QC Tools (1988).

One quirk is worth knowing before you read other sources. The list isn't perfectly fixed. The original list has matrix data analysis as the fifth tool, a heavy multivariate method that needs statistics rather than sticky notes. This guide covers the simpler prioritization matrix in that slot, as some later lists do, because it's the version a team can run in a meeting. You'll also see the interrelationship digraph called a relations diagram, the tree diagram called a systematic diagram, and the activity network diagram called an arrow diagram.

Key Facts

• The set was proposed in 1976 by a Japanese committee on new QC tools, and the English-language reference book (edited by Mizuno) appeared in 1988 (Brock University summary).
• The tools are language-based, so they work on ideas, causes, and plans rather than measurements.
• The PDPC builds on a tree diagram: the first step in the standard procedure is to start with a tree diagram of the plan (ASQ).
• The tree diagram is meant to move thinking "step by step from generalities to specifics" (ASQ).
• The activity network (arrow) diagram is the tool that gives you the critical path of a project (ASQ).

The seven tools at a glance

If you remember one thing, make it this: the first three tools help you understand the situation, the next two help you decide, and the last two help you execute.

Tool 1: Affinity diagram

An affinity diagram takes a big, messy set of ideas and sorts them into groups based on how they naturally relate. You write each idea on its own note, let the team cluster them in silence, and then name each cluster.

The silence matters. Talking too early lets the loudest person decide the categories. Silent sorting forces people to react to the ideas themselves rather than to each other.

Example: A support team collects 60 comments from a customer survey. Sorted by affinity, they fall into five groups: slow responses, unclear billing, missing features, confusing onboarding, and rude or rushed tone. Now the team has five themes to work on instead of 60 complaints.

Tool 2: Interrelationship digraph

The interrelationship digraph answers a different question: which of these things is causing the others? ASQ describes it as a tool that depicts the relationship among factors in a complex situation, with the main purpose of helping identify relationships that aren't easily recognizable (ASQ).

You place the factors on a page, then draw an arrow from each cause to the thing it influences. Count the arrows. A factor with mostly outgoing arrows is a driver. A factor with mostly incoming arrows is an outcome. Drivers are where you spend your effort, because fixing an outcome without touching its driver just invites the problem back.

It sits close to root cause analysis and works well after you've built a fishbone diagram, since a fishbone lists causes by category but doesn't show how they push on each other.

Example: A software team lists seven reasons releases keep slipping: unclear specs, late design changes, too few testers, flaky test environments, big batch sizes, context switching, and low morale. The digraph shows that "unclear specs" has five outgoing arrows and almost nothing pointing at it. That's the driver. Low morale has the most incoming arrows. It's a symptom.

Tool 3: Tree diagram

A tree diagram starts with one goal and keeps asking "what has to happen to make this true?" until you reach tasks someone can actually do. Each answer becomes a branch, and each branch gets the same question again.

ASQ's procedure includes a "necessary-and-sufficient" check at each level: are all the items at this level necessary for the one above, and would they be sufficient if all were done? That test catches both padding and gaps.

Example: The goal is "cut order-to-delivery time." Level two: faster order entry, faster picking, faster shipping. Level three under picking: re-slot fast movers near the dock, batch small orders, add a second pick shift on Mondays. Now you've got three things you can assign.

Tool 4: Matrix diagram

A matrix diagram is a grid. Put one group of items down the side, another across the top, and mark where they connect. ASQ defines it as a tool for analyzing and displaying the relationship between data sets, showing the relationship between two, three, or four groups of information, and notes six shapes are possible: L, T, Y, X, C, and roof-shaped (ASQ).

The L-shaped matrix, with two groups, covers most everyday uses. A RACI chart is a matrix diagram. So is the central grid in quality function deployment, which links customer needs to design features and has a roof-shaped matrix on top.

Example: An HR team puts five onboarding tasks down the side and four roles across the top, then marks who is responsible, who approves, and who is only informed. Gaps and double-ownership show up immediately.

Tool 5: Prioritization matrix

The prioritization matrix ranks a list of options against criteria that you weight first. It's a close cousin of the decision matrix, which ASQ describes as evaluating and prioritizing a list of options by first establishing a list of weighted criteria and then evaluating each option against them (ASQ).

The sequence is the point. Agree on the criteria and their weights before anyone scores an option. Otherwise people reverse-engineer the weights to justify the option they already liked.

Example: A finance team has six process improvements on the table. The criteria are savings, effort, risk, and time to benefit, weighted 4, 3, 2, 1. Each option gets a 1 to 5 score per criterion, multiplied by the weight and summed. The winner is rarely the one the loudest manager proposed, and that's usually the reason to do it.

Tool 6: Process decision program chart (PDPC)

The PDPC is the "what could go wrong?" tool. ASQ defines it as a tool that systematically identifies what might go wrong in a plan under development, then develops countermeasures to prevent or offset those problems (ASQ). You either revise the plan to avoid the problem or arrive ready with the best response.

The standard procedure starts from a tree diagram of the plan. For each task on the third level, the team brainstorms what could go wrong, drops the improbable or trivial, then adds countermeasures and marks each one practical or impractical. ASQ suggests using it before implementing a plan, especially when the plan is large and complex, when it must finish on schedule, or when the price of failure is high.

If you know FMEA, the idea will feel familiar. FMEA scores failure modes of a product or process by severity, occurrence, and detection. PDPC is lighter and earlier: it's a planning-stage pass with no scoring, built for a project rather than a part.

Example: A retailer plans a warehouse move over one weekend. The PDPC flags a delayed truck, a mislabeled pallet, and a system cutover that overruns. Each gets a response: a backup carrier on call, a label check at loading, and a rollback plan with a cutoff time.

Tool 7: Activity network diagram

The activity network diagram (also called the arrow diagram) shows the order in which tasks must happen and how long each takes. ASQ describes the arrow diagram as showing the required order of tasks in a project, the best schedule for the entire project, and potential scheduling and resource problems, and says it lets you calculate the critical path, the flow of critical steps where delays can affect the timing of the entire project (ASQ).

For each task you ask three questions: what must happen before it, what can happen at the same time, and what comes right after. Then you add durations and trace the longest path from start to finish. Any slip on that path moves your end date. Slips off that path may not.

Example: A product launch has copy, design, legal review, a landing page build, and a press list. Legal review depends on copy, the landing page depends on design and approved copy, and the press list is independent. The longest chain runs copy, legal, landing page. That's the one to protect. The press list has slack.

How the seven tools chain together

The tools were built to be used as a sequence, though you'll rarely need all seven. A typical run looks like this:

1. Gather and group. Brainstorm the issue, then use an affinity diagram to turn the pile into themes.
2. Find the drivers. Feed the themes into an interrelationship digraph to see which ones cause the rest.
3. Break it down. Pick the key driver or goal and build a tree diagram of actions.
4. Connect and choose. Use a matrix diagram to link actions to owners or needs, and a prioritization matrix to decide which actions to fund first.
5. Stress-test. Run a PDPC on the chosen plan.
6. Schedule. Put the survivors into an activity network diagram and protect the critical path.

ASQ's own guidance reflects this chaining. Its tree diagram page suggests using the tool after an affinity or interrelationship diagram has uncovered key issues, and its interrelationship page suggests using that tool after generating an affinity, fishbone, or tree diagram.

Seven new tools vs the seven basic tools

They're complements, not rivals. A team might use the management tools to decide where to focus and the basic tools to prove the focus worked. Both families belong to the wider total quality management toolkit.

How to use the tools in a planning session

You don't have to run all seven. Use this step-by-step approach to pick the right ones.

1. Name the situation in one sentence. Is it a pile of ideas, a tangled problem, a goal without a plan, a choice between options, a risky plan, or a scheduling puzzle? The wording tells you where to start.
2. Choose the entry tool. Pile of ideas: affinity. Tangled problem: digraph. Goal without steps: tree. Many options: prioritization matrix. Plan that worries you: PDPC. Dependent tasks with a deadline: activity network.
3. Set the room up. Use sticky notes and a wall, not slides. Invite people who see different parts of the process. Keep the group to five to eight so everyone can touch the wall.
4. Work silently first. Have people write ideas or place notes alone before discussing. It stops the first speaker from anchoring the group.
5. Move the output into the next tool. Don't leave a finished diagram on the wall. Take its result (themes, drivers, tasks, scores) and carry it forward.
6. Capture it. Photograph the wall, transcribe the result, and give each action an owner and a date.
7. Revisit it. Plans change. Check the PDPC risks and the critical path at each milestone.

Ready-to-copy planning sequence template

Copy this table into a doc or spreadsheet and fill it in as you go. One row per tool you actually use.

Examples by business function

Do's and don'ts

Do

• Start with the tool that matches your situation, not with the first one on the list.
• Weight your criteria before you score any option.
• Run the necessary-and-sufficient check on every tree diagram.
• Use the tools in a group. They're built for shared thinking.
• Carry each output into the next step instead of redrawing it.

Don't

• Don't use them for a question that data can answer. If you can measure it, reach for a basic tool such as a run chart.
• Don't let one person fill in the wall. The value is in the group's separate views.
• Don't treat the PDPC as a one-time exercise. Review it when the plan changes.
• Don't skip the final step. A diagram with no owner and no date is a poster, not a plan.
• Don't run all seven on a small problem. Two well-chosen tools beat seven rushed ones.

Common mistakes

Drawing the digraph as a flowchart. The arrows mean "influences," not "happens next." If you're drawing sequence, you want the activity network diagram.

Stopping the tree too early. If a box at the bottom still says "improve quality," it isn't a task. Keep asking until someone could start on Monday.

Scoring before agreeing on criteria. This is the most common way a prioritization matrix gets gamed, and it's easy to prevent.

Where to go next

If your team is stuck on a messy problem, start with an affinity diagram and follow the chain. If you've already got data and a stable process, jump back to the seven quality tools and the root cause analysis methods that go with them.