Target Granularity Review¶
Ritual — instantiates Boundary-Cost Coarsening Management
A recurring review that asks whether the current number and scale of units still match the system's purpose.
Metrics and counterforces are inert without a standard that says how many units the system should have and when to worry. Target Granularity Review is the recurring deliberation that sets and updates that standard: it asks whether the current number and scale of units still fit the system's purpose, fixes a target granularity range, and defines the coarsening-pressure trip-wire at which the system should intervene. Its defining nature is that it is a periodic act of judgment — not a live meter and not an automatic trigger. It decides what the numbers should be, leaving measurement to the dashboard and enforcement to the rules. Its output is a policy, not a reading and not an action.
Example¶
Every quarter, an engineering leadership group reviews how many teams and services the organization runs against what it is actually building. This cycle they notice two opposite drifts: the platform group has quietly absorbed three formerly independent teams (coarsening), while the mobile area has splintered into eight tiny teams that now spend more time in cross-team meetings than shipping (over-fragmentation). The review fixes neither on the spot. It sets policy: a domain should be owned by four to eight teams of five to nine engineers; escalate for intervention when any single team's cross-team dependencies exceed a set count, or when a domain drops below three teams. That target range and that trip-wire become the standard the Size-Distribution Dashboard is read against and the standard the split and reseed mechanisms act on. Nothing was merged or split in the room — a target was agreed.
How it works¶
- Restate purpose. What does this system need from its granularity now — responsiveness, resilience, diversity, low coordination cost? Purpose drifts, and last cycle's answer may be wrong today.
- Set the target range. Fix both a floor (below which the system is brittle or captured) and a ceiling (above which it is wasteful and slow) on unit count and scale.
- Define the coarsening-pressure threshold. Name the merger rate, attrition, skew, or dependency level that should trigger a response — the early-warning line, distinct from routine variation.
- Re-baseline rather than inherit. Because coarsening is dynamic, the review updates the target each cycle instead of ratifying whatever number it inherited.
Tuning parameters¶
- Cadence — how often the review runs. Too rare and the target lags reality; too frequent and it thrashes, feeding a reorg treadmill.
- Range width — how tight the target granularity band is. Narrow bands trigger constant intervention; wide ones tolerate drift.
- Threshold sensitivity — how much coarsening pressure trips a response. Sensitive lines catch drift early but cry wolf.
- Purpose weighting — how much weight resilience and diversity carry against coordination cost; shifting it moves the whole target.
- Authority — whether the review sets binding policy or advisory guidance, which decides whether its target actually constrains anyone.
When it helps, and when it misleads¶
Its strength is that it supplies the missing standard, turning raw metrics into "too coarse / about right / too fine" and giving every other mechanism a target to serve — and it keeps that target current as the system's purpose changes.
Its failure mode is that a review is only as good as its cadence and honesty. Run too rarely, it merely ratifies whatever coarsening already happened; run as an empty ritual, it rubber-stamps last year's number; and a target set by whoever benefits from consolidation drifts steadily toward "bigger is fine." Because a system's structure tends to mirror the communication structure of the organization that builds it — Conway's Law[n1] — the right granularity is a design choice that must be chosen, not a fact to be discovered once. The guarding discipline is to tie the target to stated purpose and to independent metrics from the dashboard, never to the preferences of the units that stand to grow, and to re-derive it each cycle rather than inheriting it.
How it implements the components¶
target_granularity_policy— the agreed target range (floor and ceiling on unit count and scale) is the policy the review produces.coarsening_pressure_threshold— the trip-wire the review defines: the level of merger rate, attrition, or skew at which intervention is warranted.
It sets the standard but neither measures nor enforces it. It does not chart the live population via size_distribution_profile — that is Size-Distribution Dashboard — and it does not itself split oversized units via diseconomy_limit_guardrail — that is Capped-Growth or Split Rule, the automatic trigger to the review's periodic judgment.
Related¶
- Instantiates: Boundary-Cost Coarsening Management — sets the target granularity every other mechanism serves.
- Consumes: Size-Distribution Dashboard — supplies the live population metrics the review judges against purpose.
- Sibling mechanisms: Size-Distribution Dashboard · Interface-Cost Accounting · Anti-Coarsening Inhibitor Protocol · Capped-Growth or Split Rule · Reseeding or Nucleation Program · Controlled Consolidation Gate
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Target Granularity Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a recurring review that asks whether the current number and scale of units still match the system’s purpose.
Independent corroboration: The frozen evidence defines Target Granularity Review as 'A recurring review that asks whether the current number and scale of units still match the system’s purpose', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Communication, Facilitation & Learning — Target Granularity Review includes features of a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Systems Thinking & Cybernetics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: The defining operation is: A recurring review that asks whether the current number and scale of units still match the system’s purpose. In the systems_cybernetics lineage, that operation is specifically evidenced by authoritative or primary work that formalizes feedback regulation, requisite variety, thresholds, stability, and the rate at which a regulator can absorb change. This makes systems_cybernetics the best historical origin, while the retained alternates document contributing methods and later applications rather than being mistaken for coequal origins.
Related originating lineages:
- Engineering & Design — engineering_design supplies a historically relevant parallel or contributing practice for the defining operation—A recurring review that asks whether the current number and scale of units still match the system’s purpose—but the evidence does not make it the best primary lineage.
- Operations Research — Operations research, optimization, and queueing analysis supplies a parallel or contributing lineage for the mechanism's defining operation: a recurring review that asks whether the current number and scale of units still match the system’s purpose.
- Organizational & Management Science — organizational_management supplies a historically relevant parallel or contributing practice for the defining operation—A recurring review that asks whether the current number and scale of units still match the system’s purpose—but the evidence does not make it the best primary lineage.
- Statistics & Experimental Design — Statistics' measurement, sampling, inference, and experimental-design tradition provides a formative adjacent lineage for the same target granularity review operation.
Review resolution: The blind reviewers disagree on primary lineage (engineering_design versus organizational_management), so I adjudicated the mechanism rather than inheriting either label. The defining operation is: A recurring review that asks whether the current number and scale of units still match the system’s purpose. In the systems_cybernetics lineage, that operation is specifically evidenced by authoritative or primary work that formalizes feedback regulation, requisite variety, thresholds, stability, and the rate at which a regulator can absorb change. This makes systems_cybernetics the best historical origin, while the retained alternates document contributing methods and later applications rather than being mistaken for coequal origins. The cited Ashby, An Introduction to Cybernetics directly supports the mechanism-specific operation and its disciplinary lineage. I retain all independently explained historical alternates without a numeric cap. origin_mode=cross_disciplinary_synthesis records how the mechanism arose; domain_reach=universal separately records how broadly it can now be applied.
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:
Notes¶
[n1] Conway's Law observes that systems come to mirror the communication structure of the organizations that design them, so the number and boundaries of teams effectively fix the number and boundaries of the artifact. It is why a granularity target is a deliberate design decision worth reviewing, not an emergent given. ↩