Directed Relation Matrix¶
Relational mapping model — instantiates Directed Asymmetry Mapping and Calibration
Lays the two sides of each relation on a grid and records which way influence, dependence, and control actually run — turning a vague "they're unequal" into an oriented map.
Before you can decide whether to treat two sides the same, you have to see which way the relation actually points. The Directed Relation Matrix is the mapping step: it puts each pair of parties on a grid and records, for the relation between them, which direction the leverage runs — who depends on whom, who can walk away cheaply, who sets terms. Its one defining move is orientation: every cell carries an arrow, not just a magnitude, so a relation that looks like a balanced "partnership" is forced to declare whether it is genuinely two-way or an 80/20 dependency wearing symmetric language. Where the archetype's other tools score, judge, or govern an asymmetry, this one is the primitive that makes the asymmetry visible and directed in the first place.
Example¶
A mid-size electronics maker wants to know how exposed it really is across its supplier base. It builds a matrix: rows are its top dozen suppliers, and for each it marks the direction of dependence — could we replace them cheaply, could they replace us, who owns the design IP, who names the price. Filling it in, three relationships the sales deck calls "strategic partnerships" turn out to have arrows pointing almost entirely one way: the specialty-chip vendor needs the maker far less than the maker needs the vendor.
The output is not a ranking but an oriented picture: most connector and cabling relations are roughly mutual (arrows both ways, short), while two supplier cells are long one-way arrows. That picture is what tells the firm exactly where to invest in dual-sourcing — not the biggest suppliers, but the most asymmetrically depended-on ones — and it is the input every later step (scoring, obligations, monitoring) reads from.
How it works¶
- Enumerate the relations, not just the parties. A row is a pair and the thing being mapped is the edge between them, so the unit of analysis is the relationship, not either side alone.
- Mark direction per cell. Each relation gets an arrow (A→B, B→A, or mutual) and a rough weight, capturing who leans on whom rather than only how big each party is.
- Read the reciprocity boundary off the grid. Mutual, short-arrow cells are the reciprocal region; long one-way arrows mark where reciprocity stops — the boundary that later mechanisms must decide to preserve, offset, or constrain.
Tuning parameters¶
- Dimension set — which axes of leverage you score (dependence, exit cost, information, control, exposure). More axes catch subtler one-way relations but dilute the picture; too few collapse distinct asymmetries into one blur.
- Direction resolution — binary arrows (one-way / mutual) versus graded direction. Graded is more faithful but invites false precision on relations you barely understand.
- Aggregation level — map individual counterparties or whole classes of them. Coarser cells are legible; finer cells catch a single dominant relation hiding inside an "average."
- Refresh cadence — a one-time snapshot or a re-drawn map as relations shift, since direction can reverse when a party gains or loses alternatives.
When it helps, and when it misleads¶
Its strength is that it converts an intuition — "they've got us over a barrel" — into an explicit, directed object the whole team can point at, and it exposes the specific trap the archetype exists for: a relation described in unordered language ("our partner," "the other party") whose leverage in fact runs one way. Naming who-depends-on-whom is the classic move of resource-dependence analysis, and the matrix is its lightweight instrument.[1]
Its failure modes are those of any map. Arrows are only as honest as the evidence behind them, and the matrix is easily run backwards — drawn to confirm a dependence story someone already believes rather than to test it, with the convenient arrows pressed darker. It also freezes a moment: direction that looks fixed can reverse the day a party finds a substitute. The discipline that guards against this is to source each arrow from something checkable (a real switching cost, a real alternative) and to re-draw the map when the underlying options change, rather than treating the first sketch as the territory.
How it implements the components¶
The Directed Relation Matrix fills the archetype's mapping slots — the ones a representation, not a judgment or a policy, can fill:
oriented_relation_map— its core output: the grid of relations with a direction on every edge.reciprocity_boundary— by distinguishing mutual cells from one-way ones, it locates where reciprocity actually holds and where it stops.
It does not score how large each asymmetry is (asymmetry_dimension_inventory, side_specific_metric_pair → Asymmetry Dimension Scorecard), track the direction-sensitive metrics over time (asymmetry_drift_monitor → Direction-Sensitive Metric Dashboard), or decide what obligations each side then carries (role_specific_obligation_map → Role-Specific Policy Table).
Related¶
- Instantiates: Directed Asymmetry Mapping and Calibration — the matrix supplies the oriented map every later step reads from.
- Sibling mechanisms: Direction-Sensitive Metric Dashboard · Side-Swap Test · Relevant Asymmetry Test · Role-Specific Policy Table · Asymmetry Dimension Scorecard · False Symmetry Review
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Directed Relation Matrix operates as a non-executable information artifact that externalizes static or prospective structure because it lays the two sides of each relation on a grid and records which way influence, dependence, and control actually run — turning a vague 'they're unequal' into an oriented map.
Independent corroboration: The frozen evidence defines Directed Relation Matrix as 'Lays the two sides of each relation on a grid and records which way influence, dependence, and control actually run — turning a vague 'they're unequal' into an oriented map', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Organizational resource-dependence analysis cohered mapping power by the direction of dependence on controlled, hard-to-substitute resources.
Related originating lineages:
- Sociology & Anthropology — Relational sociology supplied broader accounts of asymmetric power embedded in social ties.
Review resolution: Both current reviews place directed_relation_matrix primarily in organizational_management; the reconciled classification retains only lineages that materially shaped the mechanism and keeps breadth of origin separate from reach.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The matrix is deliberately descriptive: it says which way the relation points, not whether that is acceptable. Whether a long one-way arrow is a problem is a question for the Relevant Asymmetry Test and the Side-Swap Test; keeping mapping separate from judgement is what lets a team improve the map without re-litigating every remedy.
References¶
[1] Pfeffer, J., & Salancik, G. R. The External Control of Organizations: A Resource Dependence Perspective. Harper & Row (1978). Develops a resource-dependence perspective for analyzing who controls resources needed by organizations. registry ↩