Professional Documents
Culture Documents
• New tools work in conjunction with the original seven basic tools
Seven New Tols
• Affinity Diagram
• Relations Diagram
• Tree Diagram
• Matrix Diagram
• Matrix Data Analysis
• Process Decision Program Chart (PDPC)
• Arrow / Activity Diagram
AFFINITY DIAGRAM
Affinity Diagram
ii. Define the task in such a way that the problem is clear.
iii. Collect verbal data about the problem by brainstorming, Surveys etc.
iv. Transfer each data on separate data card (one item per card).
• Avoid abbreviations.
v. Shuffle the cards (to remove any patterns) and spread them out in a
'parking area' so that they can all be seen.
Affinity Diagram
-Construction-
vi. Silently, the group members reads and moves the cards one by
one from the parking area into the organization area, placing
together those that seem to be most closely related. This stage
ends when the movement of cards ceases.
Affinity Diagram
-Construction-
vii. Discuss each group, aiming to identify the common characteristics of
the group. This may result in cards being moved to or from other
groups/Headers. Create a header card to summarize the spirit of the
group (may be from within the group or a new one).
viii. Repeat the process, building up a multi-level tree made up of groups
which contain other groups and individual cards.
ix. The cards and groups may then be documented in a single diagram i.e.
affinity diagram for communication, discussion, etc.
Affinity Diagram
-Advantage-
• Facilitates breakthrough thinking and simulates
fresh ideas
• Permits the problems to be pinned down
accurately
• Considers opinion of entire group - fosters team
spirit
• Raises everyone’s level of awareness
RELATIONS DIAGRAM /
INTERRELATIONSHIP DIAGRAM
Relations Diagram
iii. Define each problem clearly, writing it as a complete, but brief, sentence on
a card. There may be more than one such problem statement.
iv. Produce the set of items to be related in the diagram by using techniques
like Brainstorming, nominal group technique, surveys, inputs from Affinity
Diagram, Cause-Effect Diagram or Tree Diagram. Write each item on a
card, distinguishing item cards from problem cards. Aim for around 15 to
50 cards.
Relation Diagram
-Construction-
v. Put the item cards randomly in a 'parking area' where they may be
vi. Select a card in the organization area and look for a card in the parking area
which answers the question identified in step (ii). For a cause-effect Relations
Diagram this will be a card which is a direct cause of a problem card. Repeat
this step, selecting and placing cards near the problem cards, until all cards
vii. When placing cards, also look for links to or from other cards in the
viii. Review the layout with the team and draw arrows between cards on the
diagram as relationships are agreed.
• Beware of adding arrows for weak relationships, as this can result in
the important link being hidden in a mass of arrows.
• Also avoid two-way arrows; where the relationship is bidirectional,
place the arrowhead to show the most significant direction.
Relation Diagram
-Construction-
ix. Identify and mark key items that are to be addressed further by
x. Review the whole diagram to check that assumed causes are actual
xi. Review the marked changes, update the document accordingly and
tree.
• Each position or node on the tree has one predecessor or parent and one or
more successor nodes, or children
• There is one initial node (or root), which has no parent, and multiple
bottom-level nodes (or leaves) which have no children
Tree Diagram
-Construction-
i. Identify the objective of using the Tree Diagram. Examples of this
include:
• Determine the individual tasks that each person on a project team must carry
out to achieve a known objective.
ii. Assemble a small team of people to work on the diagram. These people
should be of an analytical (rather than creative) nature, and should have
sufficient subject expertise between them to be able to break down the
problem to the required level of detail.
Tree Diagram
-Construction-
iii. Define the top-level 'root' statement so that it can easily
identify its individual sub-components.
iv. Define the process for breaking down each 'parent' statement
into 'child' statements.
ii. Form a team who have the time and knowledge to work on achieving
the objective.
iii. Decide what needs to be compared to achieve the objective. This will
result in two or more lists being identified where the investigation of
their relationships will help to achieve the objective.
v. Decide how list items are to be compared. The most common is the
strong/medium/weak relationship and identify the symbols/no. if any.
Matrix Diagram
-Construction-
vi. Derive the lists
viii. Evaluate the final matrix, looking for items of significance which will
result in specific actions being carried forwards. Things to look for
include:
• Key items which relate to many of the items in the other lists.
• Patterns which strike you as odd, and which may bear further
investigation.
Matrix Diagram
-When to use it?-
chart.
Matrix Data Analysis Chart
(MDAC)
MDAC Example
• when making plans, to help identify potential risks for successful completion.
• when risks are identified, use it to help identify and select from a set of
possible countermeasures.
• It is of best value when risks are non-obvious, such as in unfamiliar
situations or in complex plans, and when the consequences of failure are
serious.
PDPC
-Advantage-
• Facilitates forecasting
Creative Logical
Tree Diagram
Matrix Data
Matrix Diagram
Analysis Chart
Unknown Known
Information
SEVEN BASIC TOOLS
Check sheets
Histogram
SEVEN NEW PLANNING
Pareto Chart TOOLS
Affinity Diagram
Cause and Effect Relationship
Relations Diagram
Scatter Diagram
Tree Diagram
Control Charts (includes run
chart) Matrix Diagram
Flowchart
Matrix Data Analysis Chart
(MDAC)
Process Decision Program Chart
Arrow Diagram
THANKYOU