Eight Management & Planning Tools

Eight Management & Planning Tools (CSSGB BoK II.D — Apply)

Quick Answer: The management and planning tools help teams structure messy problems, prioritize work, and plan robust actions. Use affinity for idea grouping, interrelationship digraphs for cause drivers, trees for hierarchical breakdown, prioritization/matrix tools for criteria-based choice, PDPC for risk contingency, activity networks for schedules, and SWOT for strategic context. Green Belts select the tool that matches the decision situation—not every tool on every project.

BoK II.D is at the Apply level: recognize each tool, know when it fits, and interpret a simple diagram or matrix in a project scenario. These tools complement (they do not replace) SIPOC, process maps, FMEA, and statistical analysis.

Why Planning Tools Matter in Define and Beyond

Early project work often floods teams with sticky notes, stakeholder opinions, and competing “must-fix” items. Without structure, meetings stall or jump to solutions. The classic seven management and planning tools (also called the New Seven Quality Tools) plus SWOT give Green Belts a shared visual language for organizing input, ranking options, and planning implementation.

Affinity Diagrams

An affinity diagram organizes a large number of ideas, facts, or opinions into natural clusters based on similarity. Typical steps: silent brainstorming onto cards; silent sorting into groups; labeling each group with a theme header; discussing and refining.

When to select it: You have many unstructured items (often 15+) and no agreed categories yet—VOC complaint phrases, kaizen ideas, or risk list fragments. Affinity is a grouping tool, not a ranking tool.

Exam tip: If the stem says “sort sticky notes into themes” after a brainstorm, choose affinity—not a prioritization matrix.

Interrelationship Digraphs

An interrelationship digraph (relations diagram) maps cause-and-effect linkages among related issues. Team members draw arrows: “A drives B.” Issues with many outgoing arrows are drivers (root influencers); issues with many incoming arrows are results (symptoms or outcomes).

When to select it: Multiple issues seem connected and the team cannot agree which one to attack first. Digraphs surface system drivers better than a linear list.

Green Belt use: After affinity themes exist, place the themes (or key causes) in a digraph to identify the few drivers that unlock the rest—then feed those into root-cause analysis or project scoping.

Tree Diagrams

A tree diagram breaks a broad objective into successive levels of increasing detail (goal → means → tasks, or need → drivers → CTQs). Unlike affinity (which clusters freeform ideas), a tree is hierarchical and directed.

When to select it: You need a complete breakdown of how a goal will be achieved, or you are cascading high-level requirements into measurable leaves. CTQ trees and work-breakdown style planning both use tree logic.

Prioritization Matrices

A prioritization matrix scores options against weighted criteria (impact, effort, risk, strategic fit, cost). Multiply scores by weights, sum, and rank.

When to select it: Several viable options compete and stakeholders need a transparent, multi-criteria decision—not a pure popularity vote. Use after affinity or tree work has produced a short list of candidates.

Simple example: Three countermeasures scored on Impact (weight 0.5) and Ease (weight 0.5). Option A: Impact 5, Ease 2 → score 3.5. Option B: Impact 4, Ease 4 → score 4.0. Option B ranks first even if A has higher raw impact.

Matrix Diagrams

A matrix diagram displays relationships between two (or more) sets of items—rows vs. columns—using symbols or scores (strong/medium/weak, or numeric). Common shapes: L-shaped (two sets), T-shaped, and roof-style matrices used in QFD-style thinking.

When to select it: You must show which Xs link to which Ys, which process steps affect which CTQs, or which teams own which deliverables. Matrices clarify cross-functional handoffs without forcing a schedule.

Affinity vs. matrix: Affinity groups one pile of ideas; a matrix relates two structured lists already known.

Process Decision Program Chart (PDPC)

PDPC extends a tree of planned actions by asking, at each step, “What could go wrong?” and “What countermeasure will we take?” It is a contingency planning tool—closer to proactive risk thinking than to statistical process control.

When to select it: Before a pilot, go-live, or complex change where failure modes are foreseeable but not yet fully FMEA’d, or when you need a visual “if this fails, then do that” plan for the team and Champion.

Exam tip: PDPC = plan + potential problems + countermeasures. FMEA scores severity/occurrence/detection; PDPC emphasizes branching contingency paths.

Activity Network Diagrams

An activity network diagram (arrow or precedence diagram) sequences tasks with dependencies, durations, and often earliest/latest start-finish times. The longest path is the critical path—delaying any task on it delays the project.

When to select it: Implementation has many dependent tasks and you need finish dates, parallel work, and float. Complements Gantt charts (timeline view) with true logic of what blocks what.

Green Belt use: Build a network for Improve/Control rollout tasks (training, system change, pilot, validation) so tollgate commitments are realistic.

SWOT Analysis

SWOT inventories Strengths, Weaknesses (internal) and Opportunities, Threats (external). Strengths and weaknesses are controllable organizational factors; opportunities and threats come from market, regulation, technology, or competitors.

When to select it: Framing whether a project aligns with strategy, deciding among deployment options, or briefing leadership on project context. SWOT is strategic framing, not a substitute for process data or capability analysis.

Pairing tip: Use SWOT to justify why this project now; use prioritization matrices to rank which project or solution; use PDPC/activity networks to plan how we execute safely and on time.

Selection Cheat Sheet for the Exam

Common mistakes: Using multivoting when multi-criteria trade-offs matter (use prioritization matrix); calling a digraph a process map; treating SWOT as proof of root cause; building an activity network before the action list exists (tree or WBS first).

Master tool selection first: on Apply-level items, matching the tool to the situation scores points even when you never draw the diagram in the exam room.