# Scarcity and demand storyboard

Previous setup: Establish the allocation problem and define what counts as demand and availability.

| Unit | Audience arrives with | Headline / point | Substance + status | Closing beat | Audience leaves with | Connection to next | Layout/use and alternatives | Missing input / format limit |
|---|---|---|---|---|---|---|---|---|
| 1 | The reader assumes the easiest contribution to produce is the one most worth producing. | Look for the useful gap. | The four examples occupy distinct combinations, so scarcity alone cannot masquerade as demand. The proposed next step is investigation rather than an unsupported commitment. Fictional, not proof. | Investigate the gap before committing resources. | The reader can identify a possible demand/supply mismatch and request evidence before prioritising it. | Test demand, investigate scarcity and assess feasibility. | S79 / scarcity-and-demand; alternative S57 | HTML only; real evidence required. |

Suggested next headline: Test demand, investigate scarcity and assess feasibility.

Copy says: Demand and availability must be considered separately before selecting an opportunity.

Image adds: Four labelled qualitative regions separate demand from availability; multiple items may share a region without implying measured distances.

Together: The reader can identify a possible demand/supply mismatch and request evidence before prioritising it.

Medium: editable HTML diagram and typography; no generated artwork needed. Canvas: 16:9 desktop; free-height responsive document on phone. Reading order follows the relationship and ends with the implication. Qualifications stay visible; no client assets.

Selected treatment: S79 two-axis arrangement, using qualitative quadrant regions rather than precise unmeasured coordinates; no invented numerical scale.

Alternative: S57 Comparison columns. Can show evidence and constraints for each offering, but is slower to scan for the two-dimensional gap. Useful when evidence detail matters more than spatial overview.

Count: Repeatable offerings, not one compulsory item per quadrant. Both dimension definitions survive count changes. See reuse.json for actually checked instances.