# Test prioritisation scoring

> Use when you have a backlog of test ideas and need a defensible running order.

## Fill in before running

- `{{BACKLOG}}`
- `{{TRAFFIC_BY_PAGE}}`
- `{{CAPACITY}}`
- `{{BUSINESS_PRIORITY}}`

## Prompt

```
You are prioritising a backlog of conversion test ideas. Score consistently and show your reasoning.

BACKLOG (one idea per line, with any supporting evidence): {{BACKLOG}}
PAGE TRAFFIC FOR EACH LOCATION: {{TRAFFIC_BY_PAGE}}
TEAM CAPACITY: {{CAPACITY}}
CURRENT PRIORITY OF THE BUSINESS: {{BUSINESS_PRIORITY}}

Score each idea 1 to 5 on:
- Evidence: how strong is the reason to believe there is a problem here
- Reach: how many users hit this page or step
- Expected effect: how much of the conversion decision this element plausibly influences
- Effort: 5 means very low effort
- Learning value: what we find out even if the result is null

Output a table with those five columns, a total, and a one line justification for the lowest scoring dimension of each idea. Sort by total, highest first.

Then:
- Name the top three and the order to run them, accounting for the fact that tests on the same page cannot run simultaneously without interaction effects. Flag any collisions.
- Name any idea that should not be tested at all because the traffic cannot support it, and say what to do instead.
- Name any idea that should just be shipped without a test because it is an obvious fix.

Constraints: do not score Evidence above 2 for anything supported only by opinion or a competitor doing it. Do not invent traffic figures. No em dashes.
```

## Getting a better result

- Feed in the raw backlog including the bad ideas - the scoring is what filters them.
- The "just ship it" list is often a quarter of the backlog and needs no test time.
- Re-score quarterly; evidence scores change as research lands.

---

From the QuQi prompt library - https://www.quqi.io/prompts/test-prioritisation-scoring