Is / Is Not analysis

Status: Folded · Evidence: P · Family: Problem framing and reframing · Verdict: fold (2026-06-03)

Use instead: Problem Restatement

What it is

Is / Is Not analysis sharpens a fuzzy problem by drawing its boundary explicitly: alongside what the problem is, you write down what it is not but plausibly could be. Instead of describing a deviation only by where it shows up, you describe it twice - the cases it covers and the adjacent cases it pointedly does not - and the contrast between the two columns is the product. A problem stated only as “logins are failing” stays vague; stated as “logins fail on the new mobile build (is) but not on web or the prior mobile build (is not), for paid users (is) but not free (is not), since Tuesday’s release (is) but not before (is not)” is suddenly scoped, and the gap between the is and the is-not points at where to look.

The durable cognitive move underneath is boundary specification by contrast: you bound an ambiguous problem along a few dimensions (commonly what, where, when, and extent or magnitude, sometimes who) and for each dimension record both the in-scope value and the nearest out-of-scope value it could have taken but did not. The popular packaging adds a third and fourth column - the distinction (what is different or unusual about the is cases versus the is-not cases) and any change near that distinction - which is the step that turns a scoping aid into a cause-hunting aid: causes are sought where the boundary falls, on the theory that whatever drove the deviation has to fit inside the is and stay out of the is-not.

It is worth separating two things the brand-name write-ups blur. The first is the underlying framing move - tighten a loose problem by stating its complement, “this and not that” - which is a small, general, domain-free way to make a problem statement precise. The second is the fuller Kepner-Tregoe Problem Analysis procedure in which IS / IS NOT is one step, feeding a distinctions-and-changes inference used to diagnose a specific deviation from an expected standard. The famous name attaches to the first move (the is/is-not contrast) even though it was born inside the second.

When it helps / when it misleads

It helps when a problem arrives blurry, over-broad, or as a bare symptom, and the next move is to make it precise before spending effort on it. Forcing the “is not” column is a cheap discipline against a common failure: stating only what the problem covers, never its edges, so the scope silently expands or stays so vague that any cause looks plausible. Naming the nearest non-cases (“it is the paid tier, not free; the new build, not the old”) immediately narrows the search space, and the move pairs naturally with a downstream diagnostic that uses the boundary to locate cause.

It misleads or wastes effort when:

• It is treated as a diagnosis rather than a scoping aid. The is/is-not contrast bounds the problem and suggests where to look; it does not by itself prove a cause. Reading a single distinction as “the cause” skips the confirmation step the full method requires, and a plausible-looking boundary can still mislead.
• The dimensions or the “could be but is not” cases are chosen carelessly. The technique’s value comes entirely from picking relevant contrast cases - things that genuinely could have been in scope but were not. An is-not column filled with irrelevant non-cases (it is not happening on the moon) adds nothing; the discipline is only as good as the adjacency of the comparisons.
• The problem is already well-scoped. If the boundary is already clear, re-running an is/is-not table manufactures ceremony without sharpening anything, the same way over-reframing a clear problem wastes effort.
• It is reached for as a standalone skill when the surrounding work is reframing. As a framing move it is one of several ways to tighten a problem statement, and it lives most usefully inside a reframing pass rather than as a separate ritual - which is exactly the catalog’s verdict below.

What the evidence says

The honest grade for the move - “scope a problem by stating what it is and what it is not” - is P (practitioner).

What the record supports. Is / Is Not is a real, named, long-lived practitioner technique with a clear lineage inside the Kepner-Tregoe Rational Process, taught in operations, IT service management, Six Sigma, and quality curricula for six decades, and carried in mainstream references (for example the AHRQ digital-healthcare workflow toolkit documents the Kepner-Tregoe IS / IS NOT matrix as a recognized method). As a discipline for making a vague problem precise and pointing a cause search at the boundary, the mechanism is plausible and the adoption is genuine and durable. That is the extent of the directly supported claim: a respected practitioner scoping technique.

What the record does NOT support. I can locate no controlled or comparative study that isolates the IS / IS NOT move itself - “does writing the is-not column produce better problem definitions or faster correct diagnoses than not?” - and tests it against an alternative. The Kepner-Tregoe literature is overwhelmingly of two kinds, and neither grades this move upward: practitioner case narratives published by the firm and its trainers (the Apollo 13 problem-analysis account, recurring-defect blog cases), which demonstrate use and not measured effect; and teaching write-ups that describe the matrix without evaluating it. There is one nameable empirical paper that is honest to flag - Kunifuji and colleagues’ “A group problem solving system based on the Kepner-Tregoe program,” which reports experiment-based confirmation of a software coordinator-support implementation - but it evaluates a particular group-support system built on the program, not the bare is/is-not contrast, and is not a controlled test of the technique in general. The method’s own origin story is also worth stating plainly as an evidence limit: Kepner and Tregoe found that “good” and “poor” decision-makers could not articulate any difference in how they reasoned, which is what motivated their codification, but a codification motivated by that observation is not the same as a measured improvement over it.

Excluded figures (required). The diffuse claim, common in consulting and blog write-ups, that the Kepner-Tregoe approach “demonstrates effectiveness through empirical evidence” never resolves to a named author, year, effect size, or comparison group; it circulates as a reputational assertion, not a citable result, so under this library’s evidence rule it is excluded as fact and does not lift the grade. No traceable “Is/Is-Not improves outcomes by N%” figure exists to quote, and none is invented here.

Transfer caveat (required). All of the adjacent evidence is from human practitioners in management, engineering, IT, and quality settings. None of it studies Is / Is Not (or Kepner-Tregoe Problem Analysis) performed by or with an AI agent. The evidence is transferred from human contexts and is not validated for AI-augmented use, which is a second reason the conservative governing grade is P and not higher.

Why it is / is not a skill here

Verdict: Fold into problem-restatement (shipped as think-problem-restatement, registry slug problem-restatement).

The Build burden is to name one distinct, durable cognitive move that no shipped skill already produces. Is / Is Not fails that burden because its framing move - tighten an ambiguous problem by stating its complement, what it explicitly is and what it explicitly is not - is already one of the named moves inside the shipped problem-restatement skill. That skill’s instructions generate restatements by distinct moves and list “is / is not (what the problem explicitly is and is not)” as one of them; its quality checklist even requires that at least one restatement be an inversion or an is/is-not, so the move is not merely available in the skill, it is an enforced part of the artifact. Running think-problem-restatement on a vague problem produces the is/is-not boundary as a first-class line of the frame set, which is the whole of what the standalone candidate offers as a framing technique. The overlap is therefore far above the roughly 20 percent ceiling a Build requires, and the fold target resolves cleanly: problem-restatement is status: shipped, and its own registry reasoning already names this entry (“Absorbs How-Might-We, Is/Is-Not, and Frame-storming”).

A fair objection is that the full Kepner-Tregoe Problem Analysis is more than a framing move - it carries an inference engine (read the distinctions between is and is-not, look for a change near a distinction, hypothesize that change as cause, confirm it). That richer cause-tracing procedure is real, but it is not what the famous “Is/Is-Not” label is reached for in practice, and the part that is separable from problem-framing - using a boundary to drive a cause search - is decomposition-and-diagnosis territory the catalog already covers with issue-tree (decompose by cause, prune to what matters). So the candidate splits cleanly into a part that is already a problem-restatement move and a part that is already issue-tree-shaped; nothing is left over that needs a third skill of its own. That is a fold, not a build.

Why fold rather than reject. A reject would be less useful than a fold. The move is real, widely taught, and worth locating for a reader who arrives searching the famous name, so the honest service is to point them to where it already lives - run think-problem-restatement and use the is/is-not move it ships, and for the cause-tracing extension reach for issue-tree. The learning value of the NO: a famous, genuinely useful technique is not automatically a distinct skill. Is / Is Not is one good way to sharpen a problem statement, and a library that ships distinct cognitive moves rather than re-skinned versions of the same move documents it and folds it instead of shipping a second problem-restatement under a more recognizable name.

A trademark note belongs here too. “Kepner-Tregoe” is a brand and the name of the consultancy that owns the Rational Process materials and trainings. “Is / Is Not analysis” as a generic phrase is in common practitioner use and is not the trademark; this entry documents the generic move descriptively and credits Kepner and Tregoe as its origin, without using or implying any branded certification.

Lineage and who to read

The technique descends from Charles H. Kepner (1922-2016) and Benjamin B. Tregoe (1927-2017), two social scientists who met at the RAND Corporation in the mid-1950s while working on the decision processes of the U.S. Strategic Air Command. They observed that effective and ineffective problem-solvers could not describe any difference in how they reasoned, and set out to make the implicit sequence explicit. They left RAND to found Kepner-Tregoe, Inc. in 1958 and codified the method in their book The Rational Manager (McGraw-Hill, 1965), where IS / IS NOT appears as the specification step of Problem Analysis: a deviation is bounded along what, where, when, and extent by contrasting what it is against what it could be but is not, and the distinctions between those columns drive the search for cause. The later edition, The New Rational Manager (1981/1997), carries the same machinery.

For the practice, read Kepner and Tregoe directly, and for a neutral institutional description of the matrix read the AHRQ Digital Healthcare Research workflow toolkit’s Kepner-Tregoe matrix entry, which lays out the is / is not / distinction / change columns across the what, where, when, extent, and who rows. For the honest evidence limits, note that the firm’s own case material (the Apollo 13 problem-analysis story; recurring-defect case blogs) demonstrates use, not measured effect, and that the one nameable empirical paper studies a software implementation of the program rather than the bare technique. Where the framing move lives in this repo: the shipped skill think-problem-restatement and its evidence dossier at skills/think-problem-restatement/evidence/dossier.md.

Named sources

• Charles H. Kepner and Benjamin B. Tregoe, The Rational Manager: A Systematic Approach to Problem Solving and Decision Making (McGraw-Hill, 1965). The foundational text; introduces Problem Analysis with the IS / IS NOT specification (what, where, when, extent) and the distinctions-and-changes path to cause. Foundational / practitioner. (P)
• Charles H. Kepner and Benjamin B. Tregoe, The New Rational Manager (Princeton Research Press, 1981; updated 1997). The revised codification carrying the same is/is-not machinery; the standard modern reference for the method. Practitioner. (P)
• AHRQ Digital Healthcare Research, “Kepner-Tregoe Matrix” (Workflow Assessment for Health IT Toolkit). Neutral institutional description of the is / is not / distinction / change matrix across what, where, when, extent, and who. Practitioner reference, not an effectiveness study. (P)
• Susumu Kunifuji et al., “A group problem solving system based on the Kepner-Tregoe program: experiment-based confirmation of effectiveness as coordinator support facilities” (ResearchGate, publication 296493329). Evaluates a software coordinator-support system built on the KT program; the one nameable empirical paper, but it tests a particular implementation, not the bare is/is-not move. Empirical, narrow scope. (P)
• Kepner-Tregoe, Inc., “Apollo 13: An Abbreviated Use of Problem Analysis” (client success story). A practitioner case narrative demonstrating the method in use; illustrative, not evaluative. (P, case narrative)

Excluded under the evidence rule: the unattributed consulting and blog claim that the Kepner-Tregoe approach is “grounded in empirical evidence” or “demonstrates effectiveness” never resolves to a named author, year, comparison, or effect size, and is excluded as fact; it does not influence this entry’s grade. No traceable quantified outcome figure for the is/is-not move exists, and none is asserted here.