Priority Formula
What wins the pump?
Use this formula when competing plans ask for attention:
priority = (demand value x capability to deliver x plan quality) / (time x cost x resources)
Score with HIGH, MEDIUM, LOW, and conviction. Do not invent decimal precision.
Terms
Demand value: how much real pain, delay, trust loss, or upside exists.
Capability to deliver: whether we can actually do it with current or quickly reachable assets.
Plan quality: whether the bridge from Reality to Dream is believable.
Time, cost, resources: the scarce capacity the pump must spend.
Standard
- Run the self-audit: would you spend your own scarce hours on this bet?
- Score every term.
- Reject wishes before ranking.
- Pick one winner.
- State the review trigger that can reopen the decision.
Action
Use a small table when plans compete:
| Plan | Demand value | Capability | Plan quality | Time/cost/resources | Verdict |
|---|---|---|---|---|---|
| A | HIGH | MEDIUM | HIGH | LOW | Candidate |
| B | MEDIUM | HIGH | LOW | HIGH | Wait |
The winner should move to Attention. The losers need an explicit fate: wait, shrink, delegate, or delete.
Checks
- Capability is discounted, not assumed.
- Plan quality breaks ties.
- One winner reaches Attention.
- The losing plans wait, shrink, or die.
Failure Modes
- Demand theatre: urgency is mistaken for value.
- Capability fantasy: the plan assumes assets that are still DREAM.
- Precision cosplay: decimal scores hide weak judgment.
- No loser fate: every option stays alive and drains attention.
Context
- Purpose — priority starts with what the loop serves.
- Performance — measurement keeps ranking honest.
- Triad System — priority chooses the Bridge worth trusting.
- Demand Handover — Engineering demand must pass capability and value checks.
Questions
Which assumption would make the winning plan a wish instead of a bridge?
- Is demand real enough to buy scarce attention?
- Is capability REALITY, DREAM, or CONSUMED?
- What review trigger can reopen the decision?