OnlyFans Promotion Backlog Prioritizer: Rank the Next Test

Direct answer: gate first, then rank one channel’s ready ideas

Put only ready ideas for one selected channel into the worksheet. Gate each row for a clear test question, executable asset, appropriate placement, measurable intermediate action and known effort estimate. Hold any row that fails. Score eligible rows from zero to two on evidence need, decision value, effort fit and test distinctness. Add the four scores, rank highest first, and break ties by lower effort, older unresolved question, then backlog age.

This OnlyFans Promotion Backlog Prioritizer does not choose channels, build a content calendar, track live results or replace broader promotion strategy. If the channel has not been chosen, use the channel selection worksheet. The prioritizer owns only the order in which comparable, executable test ideas enter a selected channel.

Define a backlog item as a question, not a slogan

Write each item in the form: “Test whether changing this one controllable element affects this observable intermediate action for this audience context.” Attach the asset or brief, intended placement, fixed elements, effort estimate and owner. “Post more clips” is not ready because it changes volume without naming the decision the result should inform.

Keep the unit consistent. One row should represent one test that can be started, observed and closed. Do not mix a single-caption comparison with a month-long account redesign. If an idea contains several dependent changes, split it into ordered rows or return it to planning until the first question is clear.

Add the reason the question exists. Link a prior observation, a recurring audience confusion, a distribution constraint or a missing comparison. An idea with no evidence trail may still be worth exploring, but the sheet should distinguish curiosity from a known operational gap.

Apply the readiness gate before scoring

The gate prevents a vague, exciting idea from outranking work that can actually start. Require five yes answers: the test question is specific; the selected channel and exact placement are named; the required asset or approved source material exists; one observable intermediate action is defined; and a task-level effort estimate is available.

Add a current-suitability check. The proposed use must be reviewed against the channel’s current rules and the team’s approved public-content boundaries. Mark the source and date. A row that needs a workaround or unresolved approval is held, not assigned a low score. Eligibility and priority are different decisions.

Use three statuses: eligible, held with reason, or retired. “Held” requires an owner and the missing input. “Retired” requires a short explanation, such as duplicate question, changed channel condition or no longer relevant. Do not leave rejected ideas in the scored list, where their old number may still influence planning.

Re-run the gate when a held item changes. Never copy its former score forward automatically. A new asset, measurement definition or placement may alter feasibility and distinctness.

Score evidence need and decision value

Evidence need asks how important the unresolved gap is. Score zero when recent comparable evidence already answers the question, one when evidence exists but is stale or incomplete, and two when a current operating choice depends on a genuinely missing comparison. Link the evidence record so reviewers can challenge the score.

Decision value asks whether the result changes a concrete next action. Score zero when no decision is named, one when the result may refine a secondary choice, and two when either result will choose between clear alternatives. A test should not receive two points merely because its topic sounds commercially important.

Write the decision in both directions: “If the intended action becomes more frequent under comparable conditions, repeat this version; if it does not, retain the current version or test the next diagnosed breakpoint.” A one-sided rule that describes only a favourable result is not a complete decision.

Score effort fit and test distinctness

Effort fit compares the task-level estimate with the capacity already allocated to this channel. Score zero when the test cannot fit without displacing protected work, one when it fits but consumes most of the available test capacity, and two when it fits comfortably with its complete preparation, execution, response and evidence steps.

Test distinctness asks whether the result will add new information. Score zero when the row repeats a recent comparable test with no meaningful condition change, one when it extends an earlier test to a justified new context, and two when it isolates a clearly unresolved variable while keeping the important surrounding conditions stable.

Do not award distinctness for cosmetic novelty. A different audio track, crop or caption tone may still ask the same question. Conversely, a visually similar asset can support a distinct test if it changes one diagnosed message element and preserves the comparison conditions.

Build the Backlog Prioritizer worksheet

The method is an original SirenCY prioritisation worksheet. Its weights are deliberately equal and visible. Change them only through a documented team decision, not to move a preferred idea upward.

Total score equals the four criterion scores. Preserve the component scores; a total of six built from high evidence need and low feasibility is not operationally identical to six built from moderate scores across every criterion.

Apply tie-breakers without editorial bargaining

When totals tie, choose the lower complete effort estimate first. This increases the amount of evidence the fixed capacity can produce without assigning extra hidden points. If effort also ties, choose the question whose relevant evidence is older. If that still ties, choose the item that entered the eligible backlog first.

Record which tie-breaker resolved the order. Do not add decimal scores for urgency, enthusiasm or senior preference after seeing the result. If a true operational deadline exists, document it as an external constraint and make the override visible with an approver and reason.

Limit work in progress. Moving the top row into execution should not pull the next five rows with it. Keep one next-ready item if capacity allows, but preserve the ranked queue until a slot opens or new evidence requires rescoring.

Rescore only when evidence or constraints change

Set a regular review point and event-based triggers. Rescore when a relevant test closes, a channel placement changes, capacity materially changes, an asset becomes ready or a decision is no longer needed. Do not rescore every time someone adds a comment. Constant movement makes the queue impossible to trust.

Version each scored snapshot with date and reviewer. Keep the previous component scores and note what changed. This creates an audit trail showing whether an item rose because its evidence gap grew, its effort fell or another test answered part of the question.

Once a test enters execution, remove it from the ranked backlog and link its run record. This page does not define performance tracking. After completion, compatible cost and outcome data can be reviewed with the promotion ROI scorecard, while the learned decision returns to the backlog as evidence.

Work through a disclosed ranking example

Imagine three eligible ideas for the same selected short-form placement. Item A has a strong evidence need, clear decision, comfortable effort and a new isolated question: two, two, two and two, total eight. Item B repeats a recent comparison but fits easily: zero, one, two and zero, total three. Item C addresses an incomplete question with a meaningful decision but consumes most test capacity: one, two, one and two, total six.

The queue becomes A, C, B. The rank does not predict that A will attract the most attention. It says A currently provides the strongest combination of needed evidence, usable decision, capacity fit and distinct test design. When A closes, its evidence may lower or retire another item.

The example and scores are invented to demonstrate the worksheet. They are not a SirenCY campaign record, recommended backlog size or universal weighting. Teams should keep the disclosed rubric but populate it with their own ready ideas and evidence.