Local Overmatch Ratio Dashboard¶
Monitoring dashboard — instantiates Sequential Local Superiority
Continuously compares committed capacity against a chosen segment's resolution threshold so focus is never mistaken for genuine local superiority.
Choosing where to concentrate is one thing; knowing whether the concentration is actually enough is another, and it is the one teams flatter themselves about. Local Overmatch Ratio Dashboard puts a single live number in front of the decision-makers: the ratio of the capacity committed to the current segment against the capacity that segment's resolution actually demands — and it holds that number up against the clock, because a ratio above 1.0 means nothing if it only arrives after the surrounding field can reinforce. Its defining move is measurement of one already-chosen segment over time, not comparison across candidates. It answers "are we really strong enough here, right now, and will we still be before the window closes?" — and it is built precisely to expose the overmatch illusion, the habit of equating being busy and focused with being locally superior.
Example¶
A security operations center is running incident response on a multi-region intrusion. Leadership has already decided the compromised identity-provider cluster is the decisive segment. The dashboard tracks the overmatch ratio for that cluster only: senior responders assigned versus the estimated responder-hours the containment actually needs, refreshed hourly. It reads 0.7 — under-matched — and, critically, it overlays a window estimate: telemetry suggests the attacker is beginning lateral movement that will couple this cluster to the payments environment within roughly a day, after which the two can no longer be fought separately.[n1] The two numbers together say something a status meeting never would: not merely "we're a bit short-staffed," but "we are short-staffed and the clock is running out, so either we cross 1.0 in the next several hours or this stops being a local fight." That reframes the escalation call from a judgment of nerve into a reading of the gauge.
How it works¶
- Define the threshold for this segment. Estimate what "resolved" demands — people, skill, information, authority — and set it as the denominator. This is a per-segment number, not a global one.
- Meter committed capacity as the numerator. Count what is actually on the segment now, discounting nominal assignments that are not really available.
- Render the ratio against the recombination window. Plot overmatch over time next to the estimated time until the field can reinforce or couple, so an adequate ratio that arrives too late reads as red, not green.
- Alarm on divergence, not just level. A ratio trending toward the threshold from above is a warning even while still above 1.0.
Tuning parameters¶
- Threshold conservatism — how much margin above 1.0 counts as "safe." Set it at parity and normal variance will sink you; set it too high and you never commit anywhere.
- What counts in the numerator — raw headcount versus effective, skill-weighted, actually-available capacity. Generous counting is the fastest route back to the overmatch illusion.
- Refresh rate — hourly telemetry versus daily standup. Faster catches erosion sooner but adds noise and pager fatigue.
- Window coupling — how tightly the ratio is read against the recombination clock; the tighter the coupling, the more the dashboard pushes decisions to beat the window rather than admire the number.
When it helps, and when it misleads¶
Its strength is that it makes optimism falsifiable. "We're all over this" becomes a number that is either above the bar or not, and pairing it with the window kills the subtler error of winning a segment a day after it stopped being isolable. It is the honest counterweight to a team's natural belief that attention equals superiority.
Its failure mode is that the ratio is only as good as its denominator, and the denominator is a guess about how hard "resolved" really is — a guess that is systematically too low for exactly the messy, tacit work that dominates real resolution. A dashboard reading a comfortable 1.4 against a threshold that was set 40% too soft is worse than no dashboard, because it launders false confidence into a green light. The classic misuse is tuning the denominator down until the gauge looks good — managing the metric instead of the segment. The guarding discipline is to source the threshold independently of whoever owns the outcome, and to widen it whenever a resolution runs long.
How it implements the components¶
local_superiority_threshold— the dashboard is the running threshold check: capacity numerator over resolution-demand denominator, the ratio the whole archetype hinges on.recombination_window_model— it carries an estimate of time-until-the-field-can-combine as the axis the ratio is read against, so overmatch is always judged relative to the closing window.
It does not implement decisive_sequence_order — choosing *which segment and in what order is Segment Priority Matrix's job (its nearest twin); the dashboard only measures the segment already chosen. It also does not implement reserve_capacity_buffer: the dashboard reads the ratio, but the held-back reserve and the rule for committing it belong to Reserve Release Trigger.*
Related¶
- Instantiates: Sequential Local Superiority — supplies the live overmatch reading the concentration decision depends on.
- Consumes: Segment Priority Matrix chooses the segment this dashboard then meters.
- Sibling mechanisms: Segment Priority Matrix · Reserve Release Trigger · Recombination Risk Register · Economy of Force Allocation Sheet
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Local Overmatch Ratio Dashboard operates as an ongoing sensing arrangement that repeatedly observes actual state and surfaces changes or alerts because it continuously compares committed capacity against a chosen segment's resolution threshold so focus is never mistaken for genuine local superiority.
Independent corroboration: The frozen evidence defines Local Overmatch Ratio Dashboard as 'Continuously compares committed capacity against a chosen segment's resolution threshold so focus is never mistaken for genuine local superiority', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Military & Strategic Studies
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Local superiority and overmatch are canonical military operational concepts for concentrating force at a chosen point.
Related originating lineages:
- Operations Research — Force-ratio modeling and quantitative allocation materially shape the dashboard's capacity-versus-threshold calculation.
Review resolution: Both independent reviews assign primary provenance to military_strategic_studies. The queued secondary differences (alternate_origin_disagreement, origin_mode_disagreement, encyclopedia_synthesis_disagreement) are reconciled by retaining operations_research only as formative or independently established lineage(s), not merely as application domains. origin_mode=cross_disciplinary_synthesis records the provenance relationship, while domain_reach=specialized separately records applicability breadth. confidence=high preserves the more cautious assessment, and encyclopedia_synthesis=true records whether either reviewer identified a corpus-specific synthesis.
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¶
[n1] The intuition that concentrated local strength can beat a larger distributed force traces to Frederick Lanchester's early-20th-century combat models (Lanchester's laws), which formalized why force ratio at the point of contact — not total force — governs the outcome. The dashboard is the operational descendant: it insists on measuring the local ratio. ↩