Use Case Priority Matrix

Priority → Dependencies → Focus

all commercialall marketing

likelihood discounts shared demand eco risk compounds

Use cases

Ranked by priority. P = (L/10) × (w·m + (1−w)·c) × 100 · C is re-centred on 5, so a loss leader subtracts.
Tick Committed to treat one as decided — everything else is then re-costed against what it already pays for.

#	Committed	Use case	L	C	M	Needs	Avail	P	Sprints	P/sprint

ID Name L C M Notes

Building

Engineering work we do. Sprints are work remaining — 0 means it exists already, blank means not yet estimated.
Only leaves carry a number; a parent shows the sum of its leaves.

Deliverable	Sprints	Demand	Depends on

ID Label Under Sprints

Eco-System

Third parties and partnerships. Sprints are elapsed time to have it in place, not engineering effort.
If an integration is really about exposure rather than capability, give it a use case — that is what scores the marketing value.

Deliverable	Sprints	Likely	Demand	Depends on

ID Label Under Sprints Likely

Matrix

■ needed □ implied by a parent or a dependency · click a cell to toggle

Focus

A use case delivers nothing until everything it needs exists, so the question is not what is most wanted but what is cheapest to finish

Use case	P	Marginal	P/sprint	Still missing

Deliverables by ROI — demand per sprint. Things that already exist carry no ROI: they are not work.

Deliverable	Demand	Sprints	ROI	Blocked by

Sensitivity

Priority as the marketing weight moves 0 → 1. Crossovers are the arguments actually worth having.