Bottleneck Valuation Map¶

Artifact — instantiates Bottleneck Capacity Shadowing

A visual that lays out each constrained point, the concrete relaxation options available there, and their ranked relief priority — with migration risk flagged.

Version: v2 · 2026-08-28 · History
Mechanism #: 887
Type: Artifact
Form family: Representation, Specification & Plan
Solution family: Tradeoffs & Decision Support
Problem family: Decision, Search & Optimization Failure
Problem subfamily: Leverage Position & Target Selection
Origin domain: Operations Research
Also from: Economics & Finance, Organizational & Management Science
Instantiates: Bottleneck Capacity Shadowing

Bottleneck Valuation Map is the communication artifact of the archetype: a single picture that arranges the system's constrained points, hangs the concrete relaxation options on each, and encodes their ranked relief priority so a mixed room can see the whole decision at once. Its defining trait is that it displays and orders value rather than computing it — it takes shadow values and costs produced upstream and turns them into a legible, shared object, flagging where relief would likely just move the bottleneck rather than remove it. It is deliberately not an analysis: a map alone is not the archetype, and treating the drawing as if it were the reasoning is the failure it invites. What it adds over a plain process diagram is exactly the relief layer — the options and their ranked priority.

Example¶

A private foundation maps its grant-disbursement pipeline to decide where to unclog it: intake → eligibility review → legal contracting → matching-funds verification → budget-cap check → applicant support. On the map, each stage carries the concrete relaxation options available there — add a second reviewer, templatize the contracts, waive matching for small grants, raise the annual budget cap, staff an applicant coaching desk. The stages are ranked and colored by relief priority: legal contracting sits at the top because the value it would unlock (drawn from the shadow-price work) is high and templating it is cheap, so it is the first action. The budget cap shows high value too but is flagged red for migration risk — relieve it and eligibility review immediately becomes the new bottleneck. Program officers and the CFO read the one page and agree on the sequence without re-litigating the underlying numbers.

How it works¶

Lay out the constrained points. Arrange the system's stages in flow order (or ranked by value), so the geography of the bottlenecks is visible.
Attach relaxation options. At each constrained point, list the concrete ways it could be loosened — the map's core content, not an abstraction of it.
Encode relief priority visually. Use rank, color, or size to show the action order, consuming the shadow values and costs computed upstream.
Flag migration risk. Annotate where relieving a stage is likely to shift the bind elsewhere, so priority is read with its consequence.

Tuning parameters¶

Layout logic — flow-ordered (shows where in the process the pain sits) versus value-ranked (shows priority directly); each foregrounds a different question.
Visual encoding — what maps to color and size: relief value, cost, feasibility, or a blend; the choice steers what the eye treats as important.
Option density — how many relaxation options to show per stage; completeness versus a clean, decision-ready page.
Risk annotation — whether and how prominently migration risk is drawn; louder flags prevent naïve relief but can clutter.
Audience framing — an analyst-grade version with the full detail versus an executive one-pager that hides the derivation.

When it helps, and when it misleads¶

Its strength is alignment: it collapses a pile of estimates into one legible object that analysts and decision-makers can argue over together, making both the priority order and the migration risk visible at a glance. It is the archetype's best tool for turning a valuation into a shared decision.

Its failure mode is that a clean map looks authoritative while only re-presenting whatever went into it — garbage in, handsomely rendered garbage out. It inherits every weakness of its upstream inputs and adds the seduction of a confident picture, which is why treating the visual as the analysis is the classic misuse. Its lineage is value-stream mapping, but a value-stream map shows flow^[1] and waste, not the relief value and migration risk this artifact overlays on top. The discipline that keeps it honest is to treat it strictly as a downstream display of vetted values, date it and cite its sources, and carry the inputs' uncertainty onto the page rather than letting the rendering imply a precision the numbers don't have.

How it implements the components¶

relaxation_option — enumerates and places the concrete relief options available at each constrained point, turning "this stage is tight" into "here is what could loosen it."
relief_priority — encodes the ranked action order visually, so the sequence in which constraints should be relieved is immediately legible.

It displays but does not compute the marginal values it shows: it produces no shadow_value and certifies no binding_constraint — that's Shadow Price Analysis; it does not sweep response ranges or model relief cost (marginal_response_range, relief_cost_model, baseline_solution) — that's Constraint Sensitivity Report; and it flags migration risk but does not monitor migration after the fact (constraint_migration_monitor, downstream_effect_audit) — that's Before/After Constraint Monitoring, the sibling it is most easily confused with on the migration point, since the map shows the risk beforehand while the monitor measures the movement afterward.

Instantiates: Bottleneck Capacity Shadowing — the map is where the archetype's valuation becomes a shared, actionable picture.
Consumes: Shadow Price Analysis and Constraint Sensitivity Report supply the relief values and costs the map renders.
Sibling mechanisms: Shadow Price Analysis · Constraint Sensitivity Report · Before/After Constraint Monitoring · Capacity Investment Analysis · Marginal Capacity Value Review

Editorial Notes¶

Form Classification¶

Form family: Representation, Specification & Plan

Rationale: A visual that lays out each constrained point, the concrete relaxation options available there, and their ranked relief priority — with migration risk flagged, making its operative form a non-executable information artifact that externalizes static or prospective structure.

Independent corroboration: The frozen evidence defines Bottleneck Valuation Map as 'A visual that lays out each constrained point, the concrete relaxation options available there, and their ranked relief priority — with migration risk flagged', so its operative form is Representation, Specification & Plan.

Review outcome: Independent reviewer agreement; high confidence.

Origin Attribution¶

Primary origin: Operations Research

Origin pattern: Cross-disciplinary synthesis

Present-day reach: Multi-domain

Rationale: Shadow-price and constraint analysis rank the value of relaxing bottlenecks; the map turns those valuations and migration risks into an action sequence.

Related originating lineages:

Economics & Finance — Economics and finance contribute the valuation, allocation, incentive, market, or portfolio logic used here.
Organizational & Management Science — Management science contributes coordination, learning, workflow, governance, or change-management practice used here.

Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.