Relationship Cleanup Review¶
Review ritual — instantiates Graph Pruning
A recurring review that judges each relationship, partnership, or commitment on its merits and decides whether to keep, restrict, merge, or end it.
A Relationship Cleanup Review is a recurring human ritual in which someone accountable convenes, looks at each relationship, partnership, membership, or standing commitment on its merits, and decides to keep, restrict, merge, or end it. Its defining idea is judgment: unlike an automatic timer, it weighs the particulars of each tie — including the low-frequency ones whose value is real but easy to overlook — and can consciously preserve a weak tie as an exception edge. It is periodic and deliberative, owned by a person or team rather than run by a policy engine, and its output is a set of considered decisions about a portfolio of relationships rather than a mechanical cut.
Example¶
A mid-size company has accumulated 140 active vendor relationships over a decade — overlapping SaaS tools, dormant suppliers, a handful of genuinely strategic partners. Procurement owns an annual Relationship Cleanup Review. It inventories each relationship with its spend, usage, strategic value, risk, and age, then applies criteria weighing value against cost, risk, and overlap. Most decisions are easy: twelve overlapping SaaS vendors are marked for consolidation, twenty dormant ones for exit, three risky ones for tighter terms.
The interesting work is the exceptions. A tiny, low-spend supplier is the only qualified source for a critical component; a dormant partnership is worth keeping warm for a market the company plans to enter. The review preserves these as documented exception edges rather than cutting them for low activity — precisely the ties a spend-ranking would delete. The convening owner records each decision and the reasoning. The outcome is a leaner, clearer relationship portfolio in which the retained ties have reasons to exist and the valuable weak ties survive on purpose.
How it works¶
- Convene on a cadence. An accountable owner runs the review as a scheduled cycle, so relationships are judged periodically rather than left to accrete.
- Inventory each tie. List every relationship with spend, usage, strategic value, risk, and age — the record that turns a vague sense of sprawl into inspectable edges.
- Judge on the merits. Apply value-versus-cost/risk/overlap criteria, deciding keep, restrict, merge, or end for each — a human call, not a threshold trip.
- Protect exceptions deliberately. Flag weak-but-valuable ties as documented exceptions to be rechecked next cycle, not cut for low activity.
Tuning parameters¶
- Cadence — annual, quarterly, or event-triggered. More frequent reviews keep the portfolio tight but consume attention and goodwill.
- Criteria weights — how value, risk, and overlap trade off. Weighting toward overlap drives consolidation; toward risk drives exits.
- Exception bar — how strong a justification a weak tie needs to survive. A high bar prunes hard but risks losing rare-value ties; a low bar preserves optionality but lets sprawl persist.
- Owner and participants — who convenes and who is in the room. The owner's incentives shape which ties get defended.
When it helps, and when it misleads¶
Its strength is periodic hygiene with human judgment: it catches accreted obligations and duplicative relationships that no automatic rule would question, while consciously keeping the strategic weak ties a mechanical cut would sever. This is where Granovetter's strength of weak ties[1] bites — the infrequent, low-intensity tie is often the one that bridges to novel information or a future need, so it must not be pruned on frequency alone.
Its failure mode is reviewer bias and ritual decay. A review run by an interested owner tends to keep favorites and cut the unglamorous-but-load-bearing tie; scored purely on recent transaction volume, it severs the dormant partner needed in the next crisis; and repeated often enough without stakes, it hardens into a rubber stamp that changes nothing. The guarding discipline is an explicit exception register with recorded reasoning and a weak-tie awareness that treats low activity as a question, not a verdict — so a quiet tie is examined for latent value before it is cut.
How it implements the components¶
edge_inventory— the periodic listing of each relationship with spend, usage, value, risk, and age.edge_criteria— the value-versus-cost/risk/overlap test applied by human judgment to decide each tie's fate.exception_edge— the deliberate retention of weak-but-valuable ties as documented, rechecked exceptions.accountable_pruning_owner— the person or team who convenes the review, judges, and records the decisions.
It does not implement edge_expiration_policy, pruning_rule, or staged_removal_window — the default expiration timer, automatic lapse action, and grace window that retire ties without a meeting belong to Stale Edge Expiration; this review judges each relationship on the merits rather than letting it lapse on a clock.
Related¶
- Instantiates: Graph Pruning — the review applies criteria, exceptions, and ownership to a relationship graph on a cadence.
- Sibling mechanisms: Stale Edge Expiration · Access Revocation Pass · Least-Privilege Review · Channel Consolidation · Unsubscribe / Filtering · Dependency Pruning Workflow · Integration Decommissioning Runbook · Link Decommissioning Plan · Graph Sparsification Pass
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Relationship Cleanup Review operates by periodically evaluates every relationship's value, use, risk, and age before recommending retention or exit. That concrete deployed or enacted form is Assessment, Review & Assurance under the frozen taxonomy.
Nearest alternative: Decision, Gate & Allocation — Although Decision, Gate & Allocation can support this mechanism, the frozen evidence makes its operative form the act that periodically evaluates every relationship's value, use, risk, and age before recommending retention or exit; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Historically ambiguous
Present-day reach: Multi-domain
Rationale: Periodic portfolio reviews that continue, defer, or terminate low-value commitments are established management practice, while relationship commitment and dissolution supply the interpersonal analogue.
Related originating lineages:
- Psychology — psychology contributes behavior, memory, commitment, reactance, and social cognition to the mechanism’s formative or independently convergent form; that contribution does not displace the primary organizational_management lineage.
Review resolution: The blind reviewers disagreed on primary lineage; authoritative research supports organizational_management over the competing primary. Periodic portfolio reviews that continue, defer, or terminate low-value commitments are established management practice, while relationship commitment and dissolution supply the interpersonal analogue. The cited GAO: Best Practices for Major Investment Portfolio Management provides direct evidence for that defining form. Alternates are retained only where they contributed an independent formative tradition, while domain_reach=multi_domain records later transfer separately from historical origin.
Attribution caveat: The mechanism deliberately spans institutional partnerships and interpersonal relationships, so no single named disciplinary instrument owns its full form.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
References¶
[1] The strength of weak ties — Mark Granovetter, "The Strength of Weak Ties," American Journal of Sociology (1973): infrequent, low-intensity relationships often bridge otherwise-separate clusters and carry novel information and opportunity unavailable through strong ties, which is why they must not be pruned on frequency alone. registry ↩