V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryKepner-Tregoe
Quality · The complete guide

Kepner-Tregoe

In short

Kepner-Tregoe problem analysis is a structured method that specifies a problem by what, where, when and extent, compares where it is with where it could be but is not, and uses distinctions and changes to test possible causes.

Read the full summary

It sharpens investigations but does not replace evidence.

1,299 words · ~6 min read
Kepner-Tregoe problem analysis: a cross-functional manufacturing team compares is and is-not evidence on a two-column whiteboard
Kepner-Tregoe problem analysis compares where a problem is and is not to narrow down possible causes.
On this page
  1. 01What Kepner-Tregoe means
  2. 02Specify the problem
  3. 03Distinctions and changes
  4. 04Test possible causes
  5. 05Compared with other tools
  6. 06Use in deviation investigations
  7. 07Common pitfalls
  8. 08Inside V5: investigation context
  9. 09Explain it for your operation
  10. 10Situation appraisal first
  11. 11Decision and potential problem analysis
  12. 12Facilitating a good session
  13. 13A practical KT example
  14. 14Running a Kepner-Tregoe session on the shop floor
  15. 15A proportionate implementation plan
  16. 16Internal review questions
  17. 17Records and evidence to retain
  18. 18Questions to ask when evaluating software
On this page · 18 sections
  1. 1What Kepner-Tregoe means
  2. 2Specify the problem
  3. 3Distinctions and changes
  4. 4Test possible causes
  5. 5Compared with other tools
  6. 6Use in deviation investigations
  7. 7Common pitfalls
  8. 8Inside V5: investigation context
  9. 9Explain it for your operation
  10. 10Situation appraisal first
  11. 11Decision and potential problem analysis
  12. 12Facilitating a good session
  13. 13A practical KT example
  14. 14Running a Kepner-Tregoe session on the shop floor
  15. 15A proportionate implementation plan
  16. 16Internal review questions
  17. 17Records and evidence to retain
  18. 18Questions to ask when evaluating software
AI · Explain it for MY operation

How does Kepner-Tregoe apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What Kepner-Tregoe means

Charles Kepner and Benjamin Tregoe described rational processes for situation appraisal, problem analysis, decision analysis and potential problem analysis. In manufacturing, problem analysis is the part most often used for investigations.

It replaces brainstorming with disciplined comparison.

02Specify the problem

State the object and deviation precisely, then answer what, where, when and extent for the problem. Then answer the same questions for what could have been affected but was not.

The is / is-not table often reveals the investigation's sharpest clues.

03Distinctions and changes

For each is / is-not pair, ask what is distinctive about the is side. Then ask what changed in or around those distinctions, and when.

Causes usually involve a change acting on a distinction.

04Test possible causes

Generate possible causes from distinctions and changes, then test each against every row of the specification. A true cause explains both the is and the is-not.

Keep assumptions visible and verify the most probable cause with evidence or experiment.

05Compared with other tools

5 Whys is quick but can follow one chain; fishbone diagrams broaden ideas but do not test them. KT adds a structured test of candidates.

Use the method that fits the problem's complexity.

06Use in deviation investigations

Investigations in regulated plants need documented reasoning. A KT specification records why causes were ruled out, which helps reviewers.

Product impact and CAPA decisions remain with authorised quality personnel.

07Common pitfalls

Pitfalls include vague problem statements, skipping the is-not side, forcing a favourite cause and not verifying.

Facilitators should challenge assumptions and return to the data.

08Inside V5: investigation context

V5 deviation, NCR and CAPA records connect batches, lots, equipment, operators and changes, giving investigators the context for is / is-not comparisons.

V5 does not determine root cause; investigators do.

09Explain it for your operation

Take a recent unresolved recurring problem and build an is / is-not table with the people closest to it.

Test every proposed cause against all rows before acting.

10Situation appraisal first

Before analysing a problem, situation appraisal separates concerns, sets priorities and decides which process each concern needs: problem analysis for unknown causes, decision analysis for choices, and potential problem analysis for planning ahead.

This prevents a team from launching a full investigation into what is really a decision, or vice versa.

11Decision and potential problem analysis

Decision analysis defines objectives, separates musts from wants, weighs alternatives and assesses risks of the preferred option. Potential problem analysis anticipates what could go wrong with a plan, identifies likely causes and sets preventive and contingent actions.

In manufacturing these support choices such as selecting a corrective action or planning a process change.

12Facilitating a good session

Invite people with direct knowledge of the process, write the is / is-not table where everyone can see it, and insist on facts with sources. Park opinions until candidate causes are tested.

Record the table and test results in the investigation record so the reasoning survives beyond the meeting.

13A practical KT example

Label skew appears on line 2 but not line 1, only on the 500 ml bottle, only since Tuesday and on about 5 percent of units. Line 2's distinction is a different labeller head; the change on Tuesday was a new bottle supplier lot with slightly different shoulder geometry.

The candidate cause explains every is and is-not. A controlled trial confirms it, and the team adjusts the labeller setting and notifies the supplier under change control.

14Running a Kepner-Tregoe session on the shop floor

A problem analysis works best when the people who saw the problem are in the room and the records are open in front of them. A facilitator writes the deviation statement as one object and one defect, such as "label misprint on line 3 cartons", before anyone suggests a cause.

  1. Specify IS and IS NOT for what, where, when and extent, using batch records, shift logs and inspection results rather than memory.
  2. List the distinctions: what is true only of the IS side, such as one printer head, one roll supplier or one shift.
  3. List changes in or around each distinction, with dates, such as a firmware update, a new label stock lot or a cleaning change.
  4. Derive possible causes only from those distinctions and changes, then test each one against every IS and IS NOT line.
  5. Confirm the most probable cause with an observation, a trial or a measurement before closing the investigation.

Record the worksheet with the deviation so a reviewer can see why other causes were rejected. If no cause survives the test, the specification is usually incomplete and the team should go back to the facts rather than force a conclusion.

15A proportionate implementation plan

  1. Confirm the applicable requirement, product scope and decision owner.
  2. Map the current method and the records already available.
  3. Define terms, responsibilities, evidence and exception handling in the approved procedure.
  4. Pilot the method on one representative process and challenge a difficult exception.
  5. Train affected roles, approve the change and monitor whether the method works as intended.
  6. Review after significant change and retain a transparent history of decisions.

Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.

16Internal review questions

  • Can a reviewer identify the source, owner, method and current approved version?
  • Do summaries reconcile to original records and include unfavourable or missing evidence?
  • Are exceptions visible, assessed and linked to the affected material, product or process?
  • Are actions assigned, overdue items escalated and effectiveness reviewed?
  • Have changes in product, supplier, equipment, method or regulation triggered reassessment?
  • Does the record distinguish system support from the decision an authorised person made?

17Records and evidence to retain

  • Approved scope, definitions and responsibilities for Kepner-Tregoe Problem Analysis.
  • Source records and identifiers that let a reviewer reconstruct the work.
  • Methods, assumptions, calculations, exclusions and any data-quality limitations.
  • Exceptions, investigations, decisions, approvals and resulting actions.
  • Version history showing when the approach changed and why.

Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.

18Questions to ask when evaluating software

  • Can users trace every summary value back to its source record and version?
  • How are roles, permissions, signatures and corrections recorded?
  • Can the workflow reflect our approved procedure without inventing a universal rule?
  • What happens during an outage, and how are later entries distinguished?
  • Can we test the highest-risk exception with realistic data before committing?
  • Which decisions remain explicitly assigned to an authorised person?

Frequently asked questions

Q.What is Kepner-Tregoe Problem Analysis?+

Kepner-Tregoe problem analysis is a structured method that specifies a problem by what, where, when and extent, compares where it is with where it could be but is not, and uses distinctions and changes to test possible causes. It sharpens investigations but does not replace evidence.

Q.Is Kepner-Tregoe Problem Analysis required in every operation?+

The applicable product rules, market, risk and approved quality system determine what is required. The method should be justified for the operation rather than copied without context.

Q.Can software make the final decision?+

No. Software can organise records, calculations and workflow, but authorised people remain responsible for planning commitments, scientific, quality and disposition decisions.

Q.How should a site start?+

Choose one bounded process, define the decision and evidence, test the method with real records, correct gaps, then expand under change control.

Q.What evidence should be retained?+

Keep the approved method, source records, assumptions, exceptions, review, decision, approval and any resulting action with enough context to reconstruct the work.

Q.How long should a Kepner-Tregoe problem analysis take?+

A focused session on a single deviation often takes one to two hours once the records are gathered. Complex or recurring problems may need several sessions as new facts are collected and causes are tested.

Primary sources

  • Kepner-Tregoe — Problem solving and decision making
  • ICH Q10 — Pharmaceutical Quality System
  • ASQ — Root cause analysis
Talk to us about Kepner-Tregoe

Want to see how Kepner-Tregoe could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
PharmaceuticalMedical DevicesChemicals
Inside V5
  • → 21 CFR Part 11 — signatures and audit history your team can validate.
Example reports
V5Ultimate

Sample report

Compliance Readiness Assessment

Quality system

Compliance Readiness AssessmentView on screen or print
V5Ultimate

Sample report

Validation Support Pack

Quality system

Validation Support PackView on screen or print
→ All example reports
Regulatory anchors
  • ICH Q9
Related terms
  • → Root Cause Analysis
  • → 5 Whys
  • → Fishbone / Ishikawa
  • → 8D
  • → FMEA

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC