Skip to main content

Priorities

Priorities aren't about what you do. They're about what you stop doing.

Play with Purpose — Protocols and Platform feeding Agency through Patterns, Potential, Priorities

The Scoring Arc

Five inputs, one score. Each P asks a question, scores a dimension, and builds a C:

#tight FiveQuestionScoresDrives
1ProblemsWhat's broken?PainCommitment — knowing what matters enables sacrifice
2PurposeWhat is needed?DemandCertainty — clear focus reduces decision fatigue
3PerspectiveWhat is everyone missing?EdgeCuriousity — resources concentrate where focus is clear
4PredictionsWhere is this heading?TrendConviction — seeing the trajectory enables bold bets
5PersuasionWho needs convincing?ConversionCredibility — consistent focus signals reliability
PRIORITY = Pain × Demand × Edge × Trend × Conversion

The higher the composite score, the more it deserves your finite attention. Prompts are the output — right action, right time, based on the scores.

Problems and purpose are mirrors. A problem without purpose is suffering. A purpose without problems is fantasy.

Perspective enables predictions. You can't see where things are heading from inside your own bubble.

Predictions enable persuasion. Conviction with evidence moves people. Conviction without evidence is delusion.


The Priority Algorithm

This scoring arc is how you decide what to build, what to invest in, what to stop doing. The same pattern at every scale:

ScalePainDemandEdgeTrendConversion
PersonalWhat frustrates you daily?What do you need to progress?What can you see that others can't?Which skills are appreciating?Can you sell this to yourself?
ProductWhat's broken for users?What JTBD scores highest?What's our unfair advantage?What does the work chart show?Will someone pay for this?
PlatformWhat's the commissioning gap?What do the JTBD supersets say?What's built but dormant?Where is AI % rising fastest?What's closest to revenue?

The pit of success design: score everything, sort by priority, and the next move becomes obvious. You fall into doing the right thing instead of climbing toward it.


Prompts Are the Output

Prompts close the loop. They're the action layer — what you do once priorities are clear. Three forms:

FormMechanismFor Whom
MantrasInternal trigger phrases — the human hookYou under pressure
MemesSchelling points — concentrate imagination for coordinationTeams and communities
AI PromptsStructured instructions for agents to execute work chartsThe machines

The cascade: Mantra → Rule → Hook → System. The goal isn't to remember more. It's to engineer systems that eliminate the need to remember.

How long before the prompters become the prompted?


Context