Conflict Matrix¶
Conflict-mapping artifact — instantiates Antagonism Screening and Separation
Displays conflicting roles, rules, incentives, policies, or dependencies so antagonistic combinations can be excluded, redesigned, or routed for review.
A Conflict Matrix lays a system's elements against themselves and marks, cell by cell, which pairings pull against each other — and how badly — so the whole field of destructive combinations is visible at once and each one can be given a disposition: forbid it, rework one side of it, or send it to review. Its defining move is that it is a display and router, not a control: it makes the set of antagonisms and their severities legible and assigns each a fate, but it runs no test and enforces nothing by itself. That is what separates it from a live screen or an enforced barrier — the matrix is the map the controls are read off, the shared object that turns scattered "those two clash" lore into one gradeable, routable picture.
Example¶
A national retailer runs dozens of concurrent promotions — percentage-off coupons, buy-one-get-one, loyalty-point multipliers, clearance markdowns, an employee discount, and a price-match guarantee. Each is sensible alone, but some combinations are destructive: a 30%-off coupon stacked on already-below-cost clearance sells at a loss; a loyalty multiplier layered on a manager markdown double-discounts the same margin; a price-match plus a coupon can be gamed into near-zero. The pricing team builds a conflict matrix with the promotions on both axes. Each antagonistic cell gets a graded severity (from mild margin bleed up to sold below cost) and a disposition: never stack for the catastrophic pairs, rework the terms for the ones worth keeping (add an exclusion clause to the coupon), route to review for the borderline cases. That single grid then feeds the promotions engine's stacking configuration and the exceptions queue — everyone works from one picture instead of re-arguing each clash at the register.
How it works¶
The elements go on both axes; every antagonistic pairing gets a cell drawn from a small, fixed vocabulary so the grid reads consistently. What makes it this mechanism is the discipline in each filled cell: a severity grade so attention and control strength can be proportioned, and a disposition — exclude, redesign, or review — so the cell is a routed decision, not just a color. The matrix is versioned, because verdicts age; and it is explicitly a display, so a cell marked "never" changes nothing until some downstream control (an engine rule, a policy, a schedule) actually enforces it.
Tuning parameters¶
- Axis grain — individual elements versus families/classes. Fine grain catches specific clashes but explodes combinatorially; coarse grain stays readable but hides intra-class exceptions.
- Severity resolution — a binary clash/no-clash versus a graded scale. Grades let you triage and proportion controls, but each grade is another judgment to make and maintain.
- Disposition vocabulary — how many routing outcomes a cell may take (exclude / redesign / review / monitor). More outcomes route more precisely but complicate the grid.
- Directionality — symmetric cells versus directional ones where A undermines B but not the reverse.
- Refresh cadence — one-shot versus reviewed on a schedule and on incident feedback, so the grid tracks a changing system rather than freezing.
When it helps, and when it misleads¶
Its strength is whole-field visibility: it forces every "these two shouldn't go together" into the open alongside how badly and what to do about it, so conflicts can be prioritized by severity and each given an owner. It is the reference a stacking engine, a role design, or a schedule can all be built from without re-litigating the underlying clash.
Its central trap is that it is a map, not the territory[1] — a cell painted "prohibited" prevents nothing until a real control acts on it, yet the authoritative-looking grid invites the belief that documenting a conflict has resolved it. It is also pairwise by construction, so three individually-fine elements that are jointly toxic leave no warning in any cell; and an un-versioned matrix quietly rots as the system moves. The classic misuse is filling it in after the fact to rationalize a layout already chosen. The discipline that keeps it honest is to date and source every cell, wire each disposition to an actual enforcing control, and review on a cadence rather than treating the grid as standing truth.
How it implements the components¶
antagonistic_combination_set— the axes enumerate the elements and every filled cell names a specific hostile pairing; the matrix is the enumerated set of combinations under review.interaction_severity_rating— each conflict cell carries a graded severity, so downstream controls can be sized to the harm rather than applied uniformly.redesign_option— a cell may be dispositioned "rework one side" rather than merely blocked, flagging pairings whose value warrants reshaping an element instead of banning the combination.
The matrix displays and grades but neither tests nor enforces: it does not run a live compatibility test (compatibility_check — Drug Interaction Screening), catch a conflict automatically as it forms (co_activation_detector — Dependency Conflict Detection), or hold antagonists apart (separation_boundary, sequencing_rule, buffer_or_shield — Material Incompatibility Rule and Schedule Conflict Prevention). Its nearest look-alike is the already-authored Compatibility Matrix, which registers whether physical constituents may share a spatial domain against condition and evidence; the Conflict Matrix instead grades antagonisms among rules, roles, and incentives and routes each cell to exclusion, redesign, or review.
Related¶
- Instantiates: Antagonism Screening and Separation — it supplies the shared, gradeable picture of conflicts the whole screen is operated from.
- Sibling mechanisms: Dependency Conflict Detection · Drug Interaction Screening · Material Incompatibility Rule · Schedule Conflict Prevention · Separation-of-Duties Review · Compatibility Matrix · Quarantine or Isolation Protocol · Conflict-of-Interest Check · Policy Conflict Review
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Displays conflicting roles, rules, incentives, policies, or dependencies so antagonistic combinations can be excluded, redesigned, or routed for review, making its operative form a non-executable information artifact that externalizes static or prospective structure.
Independent corroboration: The frozen evidence defines Conflict Matrix as 'Displays conflicting roles, rules, incentives, policies, or dependencies so antagonistic combinations can be excluded, redesigned, or routed for review', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Organization and change-design practice established square matrices that lay practices or organizational elements against one another, mark competing interactions, and turn the resulting whole-system map into redesign decisions.
Related originating lineages:
- Engineering & Design — Compatibility and hazard matrices supply pairwise severity grading and routing to exclusion or redesign.
Review resolution: MIT's Matrix of Change explicitly instructs change teams to place practices in a triangular matrix and identify complementary and competing interactions. MIT's Design Structure Matrix provides the older square-matrix representation of system elements and their interfaces and dependencies. The mechanism synthesizes those lineages, with organizational change management closest to its conflict-and-disposition purpose.
Attribution caveat: Engineering design structure matrices established the general pairwise dependency representation, while MIT's Matrix of Change adds competing practices and redesign routing; organizational management is primary because conflict and disposition, not dependency alone, define this mechanism.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- MIT Center for Coordination Science: Matrix of Change—Identify System Interactions
- MIT Industrial Liaison Program: The Design Structure Matrix
Notes¶
The Conflict Matrix is the linchpin of this archetype's family: most of the other mechanisms consume it. It records where antagonisms live and how bad they are; the screens, protocols, schedules, and role designs are where those verdicts become enforced. Keeping the register separate from the enforcement is what lets the grid be corrected — a re-graded cell, a new pairing — without disturbing every control that reads from it.
References¶
[1] Korzybski, A. Science and Sanity: An Introduction to Non-Aristotelian Systems and General Semantics. 1st ed., International Non-Aristotelian Library Publishing Company (1933). Supports the caution that a representation is not the reality it represents. registry ↩