OPEXSTUDIO
← All lessons and training aids OPEX learning notes / Quality tools

Choose the quality tool for the question

State the decision question in ordinary language.. Follow the visual, practise a decision, then check your thinking.

Fictional teaching examples and AI-generated illustrations. Proposed changes and goals are not achieved results. Use the written instructions and check local conditions before applying a method.

Download this exact reviewed edition ↗

Teaching view 1 of 2

Choose the quality tool for the question

Seven question-to-tool matches: consistent recording to check sheet; priority to Pareto; distribution to histogram; paired relationship to scatter; possible causes to fishbone; mixed sources to stratification; time behaviour to control chart. Some seventh-tool lists substitute flowchart or run chart.
Original OPEX teaching diagram. Follow the steps below, then try the practice question. View full size ↗

Choosing a tool starts with the decision, not with a favourite diagram. A check sheet collects observations consistently; a Pareto ranks a stated burden; a histogram displays a distribution; and a scatter plot explores paired variables. A control chart adds time and a baseline model. A fishbone organizes possible causes, while stratification separates sources that pooling may hide. These tools can be used together, but each answers a different question. First write the question in plain language. Then choose the smallest useful display and state what further evidence is needed before acting.

Follow the method

  1. Record consistently
  2. Rank a burden
  3. See a distribution
  4. Explore paired variables
  5. Organize possible causes
  6. Separate mixed sources
  7. Monitor over time

Read the example carefully

Classic seven includes stratification; some lists use flowchart or run chart instead.

The tool selects an evidence view, not a guaranteed conclusion.

Choose the question before the display.

Teaching view 2 of 2

Match the question to the evidence and the decision

Completed selection record distinguishes complaint ranking, paired relationships, distributions, source comparisons and untested hypotheses.
Original OPEX teaching diagram. Follow the steps below, then try the practice question. View full size ↗

Fictional case: Vale Dispatch has delivery complaints, measured packing times and a list of possible causes. Coordinator Lina is asked to produce a quality chart for the weekly meeting. The manager wants to know where to begin, while a technician wants to know whether packing time changes with batch size. These are different questions; one attractive chart cannot answer both.

Follow the method

  1. Where are most comparable complaints?
  2. Does time vary with batch size?
  3. Which explanations should be tested?
  4. Are sources hiding different patterns?
  5. How does behavior evolve?

Read the example carefully

Rebuild the Pareto using documented recovery time for every included category, label hours and retain the original frequency chart separately.

Changing the basis can change the rank. Adding hours to occurrence counts would produce an uninterpretable total.

Apply the method

A pile of records is not yet a question

Turn a vague quality concern into an answerable question, select a suitable evidence display, and state what that display cannot establish.

Fictional case: Vale Dispatch has delivery complaints, measured packing times and a list of possible causes. Coordinator Lina is asked to produce a quality chart for the weekly meeting. The manager wants to know where to begin, while a technician wants to know whether packing time changes with batch size. These are different questions; one attractive chart cannot answer both.

Role: Dispatch coordinator and process analyst

Normal condition

Every proposed display has a stated question, an observation unit, a defined window and an honest limit of inference. Raw records retain their original identities.

The gap

A draft slide mixes complaints, hours and suggested causes into one descending bar chart. Its title says the biggest bar is the root cause.

  • The seven-tool overview is a selection aid, not a compulsory sequence.
  • A severe isolated complaint can require immediate response even when it ranks low by frequency.
Supplied case inputs
Available evidenceWhat it can support
Complaint logCategory, date and shipment identity; counts can be compared within the same window
Packing observationsPaired batch size and packing minutes for each observed job
Cause listThree untested explanations suggested by the team
Measurement historyOrdered packing times with operating context; baseline assumptions not yet assessed
  1. Write the decision first

    Lina separates “Which complaint category contributes most occurrences this week?” from “Do larger batches tend to take longer?” She records the intended user of each answer.

    Why: The question determines the evidence and display. Starting from a preferred graphic invites conclusions that the available records cannot support.

    Evidence: Two written questions, each tied to a decision rather than “make a chart”.

  2. Check the collection unit

    She defines one complaint occurrence and checks duplicates against shipment IDs. For the timing question she keeps each batch-size/time pair together instead of sorting the two columns separately.

    Why: Comparable counts need a consistent category rule. A paired relationship disappears or becomes fictitious if the observations lose their pairing.

    Evidence: Complaint records retain their window; every time has its matching batch size.

  3. Choose the first two views

    She assigns a Pareto chart to complaint frequency and a scatter plot to the paired observations. A check sheet is the next collection method if future categories are inconsistent.

    Why: Pareto ranks a chosen burden; scatter explores association. Neither is a root-cause verdict, and neither replaces the record definitions.

    Evidence: The chart request identifies tool, input and permissible interpretation.

  4. Place other questions deliberately

    A histogram can summarize packing-time distribution; stratification can separate routes or product groups; a fishbone can organize competing hypotheses. Time behavior needs ordered data and an appropriate run/control view.

    Why: These tools reveal different structures. Mixed sources, timing and causal hypotheses should not be folded into an unexplained “quality score”.

    Evidence: A selection record covers all seven roles without claiming that every project must use every tool.

  5. Approve a bounded next step

    Lina asks the manager to prioritize a category for investigation and asks the analyst to assess the paired data. She removes the root-cause title and records the unresolved checks.

    Why: A useful display ends with a defensible decision and the next evidence needed. Restraint about causation is part of using the tool correctly.

    Evidence: The meeting assigns evidence collection, not a causal conclusion from a bar height.

Completed question-to-tool record
QuestionChosen viewBoundary
Where are most comparable complaints?Pareto of complaint occurrencesPriority by frequency, not proven cause
Does time vary with batch size?Scatter of paired jobsAssociation only
Which explanations should be tested?Fishbone plus test recordBranches remain hypotheses
Are sources hiding different patterns?Stratified viewsKeep denominators and uncertainty
How does behavior evolve?Ordered monitoring viewCheck baseline/model before control conclusions

The manager changes the basis

The manager now asks which complaint type consumes the most recovery hours.

Rebuild the Pareto using documented recovery time for every included category, label hours and retain the original frequency chart separately.

Changing the basis can change the rank. Adding hours to occurrence counts would produce an uninterpretable total.

A revised request names recovery hours and the same declared reporting window.

Select evidence for three different decisions

New fictional case: a clinic has appointment-delay minutes, delay categories and two proposed explanations. The supervisor asks for a distribution, the largest time burden and a way to test explanations.

Changed practice inputs
RequestAvailable record
Typical spreadTwenty ordered delay measurements
Largest burdenDelay category and minutes for each event
ExplanationTwo staff suggestions; no tests yet

Your task

  1. Choose a view for each request and identify the input it needs.
  2. State one conclusion that would be unjustified from each view.
  3. Explain why a category with fewer events could lead a time-based ranking.

Prepare your worksheet

  • Decision question
  • Unit and window
  • Chosen tool
  • Permitted conclusion
  • Next evidence
Reveal the answer and reasoning

Use a histogram for distribution while retaining order elsewhere, a Pareto of summed delay minutes for the burden, and a hypothesis/test record informed by a fishbone for explanations.

A histogram does not establish stability; a time Pareto does not prove cause; a fishbone does not verify a branch. A rare long delay can contribute more minutes than many short delays.

Worked answer record
RequestDefensible selectionRequired boundary
DistributionHistogram of delay minutesNo stability claim
Time burdenPareto of minutes by categoryOne comparable basis
ExplanationCompeting hypotheses and testsZero causes verified initially

Check these interpretations

  • The familiar 80/20 phrase is not a result to impose on the data.
  • Tool names do not replace an operational definition.

Check your work

  • Match each question to a suitable view.
  • Preserve time/pair/source information needed for later analysis.
  • Separate prioritization from causal proof.

Run a practice session

Materials

  • Blank question-to-tool sheet
  • Three evidence cards
  • Answer kept separately
  1. Frame the meeting request · 4 minutes

    What decision is hidden inside “make a quality chart”?

  2. Match and challenge · 8 minutes

    Defend a tool, then name what it cannot tell us.

  3. Complete the clinic exercise · 10 minutes

    Which unit belongs on each axis or total?

  4. Debrief transfer · 5 minutes

    What raw information must survive the display?

Debrief

  • Accept alternative suitable tools when the question and boundaries are explicit.
  • Challenge any claim of a cause based only on ranking or consensus.

Individually write each request as a question before looking at the seven-tool overview.

Transfer into the work

Owner: Process analyst with the record owner

Record: Question, collection definition, selected display and interpretation note

Review: At the next evidence review

Evidence: A colleague can reproduce the display and distinguish findings from hypotheses

Return to data definition or collection when the requested conclusion exceeds the evidence.

Build on reliable methods

Sources and further reading

  • ASQ: Seven basic quality tools ↗

    The classic seven include fishbone, check sheet, control chart, histogram, Pareto, scatter and stratification; some lists substitute flowchart or run chart.

    Public primary-source summary; underlying paid standards/forms are not reproduced.
Free learning resources

Take the lesson into your team.

Read the lessons online or use these PDFs to prepare, practise and review with your team. No sign-in needed.

Facilitators and team leads

Facilitator guide

Case objectives, demonstration plans, debriefs, common mistakes and application checks across all 81 workplace cases and method lessons.

Download Facilitator guide PDF · 166 pages · 65.1 MB
Learners and improvement teams

Learner workbook

Printable case worksheets, blank observation records and five calculation exercises; answers are separate.

Download Learner workbook PDF · 169 pages · 10.7 MB
Learners after practice and facilitators

Answer key and coaching notes

Reasoned sample responses, worked calculations and coaching guidance; fictional examples are clearly labelled.

Download Answer key and coaching notes PDF · 105 pages · 8.5 MB
Practitioners and facilitators seeking detailed worked methods

Method and application reference

The native method mechanisms and worked applications for all 68 detailed lessons, in a separate bookmarked portrait reference.

Download Method and application reference PDF · 141 pages · 10.2 MB
Self-study learners and workshop groups

Illustrated systems atlas

Five illustrated system chapters: 15 Flare concept maps and 26 original workplace teaching cards, with links to all 81 supporting cases and method lessons.

Download Illustrated systems atlas PDF · 69 pages · 55.8 MB
Connect the methods

Use the next tool for the next question.

  • A defined decision question
  • An identified observation source
Explore all chapters and detailed lessons →