OPEXSTUDIO
OPEX learning notes / System chapters

Operational Problem Solving: From a Gap to Verified Change

Connect protection, problem definition, evidence, causal testing and sustained change. The labelled map shows Protect now, Define the gap, Choose the approach, Collect and separate, Test explanations, Try a countermeasure, Verify the effect, Standardize and revisit.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗
← All lessons and training aids

Operational problem solving starts with an observable gap and ends with evidence that the work improved. Use this chapter to distinguish an immediate response from an investigation, choose the next learning step and connect tested causes to countermeasures and follow-up.

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.

Published by OPEX Studio, a Prometheus Platforms product. Read the method sources and their scope.

On this lesson
Teaching view 1 of 3

Move from a problem to verified learning

Protect people and customers when exposure requires an immediate response, while keeping containment distinct from permanent correction. Define the expected and actual condition before selecting a method. Different problems need different depth: an urgent restoration, a recurring gap, a target-condition experiment and open-ended innovation are not the same. Collect evidence using stable definitions and meaningful strata. Fishbone branches and why-chains organize hypotheses; they do not prove causes. Test alternatives, predict the effect of a countermeasure and verify relevant outcomes and unintended effects. Effective changes need ownership, learning and later review. An ineffective test should return the team to the evidence.

Follow the method

  1. Protect now: Contain immediate exposure when needed
  2. Define the gap: Expected versus actual in a stated scope
  3. Choose the approach: Match urgency, complexity and uncertainty
  4. Collect and separate: Operational definitions and meaningful strata
  5. Test explanations: Hypotheses, alternatives and discriminating evidence
  6. Try a countermeasure: Prediction and controlled test
  7. Verify the effect: Relevant outcome and unintended effects
  8. Standardize and revisit: Ownership, competence and later checks

Read the example carefully

A hypothesis map is not proof of root cause.

Containment may continue while causal investigation and validation proceed.

The method choice depends on the problem; the map does not require every problem to use every tool.

Try it before revealing the answer

A team’s fishbone contains many plausible causes. What makes it ready to choose a permanent action?

Reveal the answer and reasoning

It is not ready from the diagram alone. Choose discriminating observations or tests, examine alternatives and connect any proposed action to supported causal evidence.

Teaching view 2 of 3

Turn clues into discriminating causal tests

Connect useful data collection with hypotheses, alternatives and cause verification. The labelled map shows Operational problem, Collect consistently, Stratify the evidence, Prioritize the question, Map hypotheses, Design a test, Observe the result, Update the explanation.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗

Useful evidence begins with a clear problem and stable operational definitions. Preserve denominators and time order, and stratify where populations or conditions differ. A Pareto comparison can prioritize a question on a declared basis; it does not prove a cause. Fishbone diagrams and why-chains help organize possible mechanisms and alternative explanations. A scatter relationship is another clue, not proof of causation. Choose an observation or test that would distinguish the alternatives. Retain contrary and incomplete evidence instead of forcing a neat story. Update the explanation only to the strength supported, and refine the problem scope when the evidence requires it.

Follow the method

  1. Operational problem: Expected, actual, where and when
  2. Collect consistently: Definition, denominator and time order
  3. Stratify the evidence: Separate relevant conditions and populations
  4. Prioritize the question: Magnitude, risk and declared comparison basis
  5. Map hypotheses: Fishbone or why-chain with alternatives
  6. Design a test: What observation would distinguish explanations?
  7. Observe the result: Preserve contrary and incomplete evidence
  8. Update the explanation: Supported cause or further investigation

Read the example carefully

Raw counts can mislead when exposure denominators differ.

A ranked category, correlation or fishbone branch does not establish causation.

A why-chain may branch; stop where evidence stops instead of inventing a fifth answer.

Try it before revealing the answer

One shift has more defects but produces ten times as many units. What should be checked before blaming that shift?

Reveal the answer and reasoning

Compare compatible defect definitions, exposure denominators, product mix, timing and measurement conditions. A higher count may coexist with a lower rate. Use the stratified evidence to choose a causal test, not a blame statement.

Teaching view 3 of 3

Keep protection active until change is verified

Distinguish containment, correction, corrective action and verified closure. The labelled map shows Define exposure, Contain, Restore the condition, Investigate causes, Select corrective action, Verify effectiveness, Authorize closure, Sustain the change.
AI-generated system teaching illustration. Follow the steps below, then try the practice question. View full size ↗

Containment protects against current exposure; correction restores the immediate condition; corrective action addresses a supported cause of recurrence. These decisions can overlap in time but should not be confused. Investigate both occurrence and escape where relevant. A restored machine or a relabelled record does not alone establish that affected output is acceptable or that recurrence is prevented. Verify the appropriate condition and outcomes, keep containment active while evidence is inadequate, and use the designated authority for disposition and exit. Carry effective learning into controls, training and later review. This relationship map complements 8D and NCR routines without claiming that their formal gates are identical.

Follow the method

  1. Define exposure: Affected work, product and time boundary
  2. Contain: Protect customers while uncertainty remains
  3. Restore the condition: Authorized correction of the immediate issue
  4. Investigate causes: Occurrence and escape mechanisms
  5. Select corrective action: Address supported recurrence mechanism
  6. Verify effectiveness: Relevant outcomes and unintended effects
  7. Authorize closure: Disposition and containment exit by evidence
  8. Sustain the change: Control, training, ownership and later review

Read the example carefully

Containment does not prove a permanent cause has been removed.

Correction must restore the actual required condition, not merely change a label.

Containment exit and closure require defined authority and effectiveness evidence.

Try it before revealing the answer

An overdue gauge has received a new label, but no authorized calibration or verification record exists. Can the NCR be closed?

Reveal the answer and reasoning

No. Remove the overdue gauge from service as required, complete authorized calibration or verification and restore correct status records. Assess suspect measurement/output exposure and verify the scheduling-system corrective action before closure.

Build on reliable methods

Sources and further reading

  • LEI: Problem Solving Resource Guide ↗

    Troubleshooting, gap from standard, target condition and open-ended innovation

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI LeanTech: Prompting for Problem Solving ↗

    Analysis method must fit problem; model must not default blindly to 5 Whys

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: 5 Whys ↗

    Cause chain, not exactly five repetitions; gap-from-standard focus

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • ASQ: Fishbone diagram ↗

    Organize possible causes of a defined effect for investigation; the diagram structures ideas rather than proving them.

    Public primary-source summary; underlying paid standards/forms are not reproduced.
  • PRI: Root cause corrective action ↗

    RCCA investigates causes, implements and verifies corrective actions, and supports appropriate Nadcap NCR responses.

    This teaching workflow is not the official NCR response form or an accreditation decision.
  • ASQ: Check sheet ↗

    Define the observed event, collection period and recording fields; pilot the form before repeated use.

    Public primary-source summary; underlying paid standards/forms are not reproduced.
  • ASQ: Pareto chart ↗

    Rank category totals on one stated measurement basis; cumulative percentages are optional and end at100%.

    Public primary-source summary; underlying paid standards/forms are not reproduced.
  • ASQ: Stratification ↗

    Separate observations by relevant source categories so aggregated data do not conceal patterns.

    Public primary-source summary; underlying paid standards/forms are not reproduced.
  • ASQ: Scatter diagram ↗

    Plot paired numerical observations to examine association; an apparent relationship alone does not establish causation.

    Public primary-source summary; underlying paid standards/forms are not reproduced.
  • Toyota Virtual Plant Tour: Production System ↗

    Andon response, stopping on abnormality, mistake prevention

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • LEI: Andon ↗

    Abnormality signal summons response; fixed-position process stop differs from emergency stop

    Method reference; original OPEX scenario and diagram are synthetic teaching content, not source case results.
  • AIAG/Plexus: APQP and control plan overview ↗

    Control plans link process risks and controls, with explicit reaction ownership, containment and return-to-control actions.

    Public overview only. Do not reproduce licensed forms or infer a universal sampling frequency or safe-launch exit period.
Put this lesson to work

Start with the resource for this topic.

Read online without signing in, or take this lesson into your next team conversation.

Topic pack · 17 pages · Reviewed teaching edition.

Explore the full workbooks and facilitator collection
Free learning resources

Resources for a wider learning programme

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

Practise the methods in this system.

  • Connect protection, problem definition, evidence, causal testing and sustained change.
  • Connect useful data collection with hypotheses, alternatives and cause verification.
  • Distinguish containment, correction, corrective action and verified closure.
Explore 44 more connected methods
  • Conflict cloud: challenge assumptions

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Choose the quality tool for the question

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Record defects without changing the denominator

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Rank problems on one declared basis

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • See the distribution without losing the sequence

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Test a relationship without declaring a cause

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Unmix the data before blaming a shift

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Turn fishbone branches into testable hypotheses

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Close an NCR with verified action against recurrence

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Stop the recurring leak

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make referrals ready

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Send the right shipment

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make the morning easier

    Primary teaching mechanism belongs to problem solving and verified change. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Jidoka and andon: detect, respond, verify restart

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Poka-yoke: prevention versus detection

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Select a chart from the data and sampling plan

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Separate control limits from specifications

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Read spread before the subgroup average

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Monitor one reading at a time

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Chart nonconforming units with the right denominator

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Chart nonconformities per exposure

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Respond to a signal with a defined owner

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Check stability before capability

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Separate part variation from measurement variation

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Check inspection agreement and escape risk

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Link a process risk to an executable control plan

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make the station check and reaction inseparable

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Build PFMEA from a failure chain to verified action

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Use APQP gates to expose launch risk early

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Distinguish PPAP evidence from production authorization

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Trace one suspect lot through split, merge and rework

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Audit whether critical controls are actually followed

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Control special processes through qualified conditions and records

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Prepare a Nadcap audit with scope-linked evidence

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Locate the applicable automotive requirements

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Distinguish a feedback controller from statistical monitoring

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Connect calibration to a defensible measurement result

    Primary teaching mechanism belongs to quality control and dependable evidence. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Gemba: observe work, ask, follow through

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Leader standard work supports problem solvers

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Daily board: measure, respond, learn

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Hoshin: align strategy through catchball

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Improvement and coaching kata

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Job instruction: steps, key points and reasons

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

  • Make tomorrow ready

    Primary teaching mechanism belongs to leadership and daily learning. Supporting links identify application dependencies; they do not make the methods interchangeable.

Explore all chapters and detailed lessons →

Apply the learning to your own work

Ask OPEX Guide how to apply this learning to your situation. Describe the expected condition, the gap and the evidence you have. Review its suggestions with the people doing the work before deciding on a change.

Explore your question with OPEX Guide →