Pentaria
Sign in Book a demo
Pentaria
Book a demo Sign in
Workflow

Backlog Prioritization

Ordering the backlog so the order survives challenge

About this workflow

Ordering the backlog so the most valuable work comes first — every item scored with the agreed model and read through a second lens, then ordered and cut against capacity. The work runs from merging the export and scoring each item from its own description, through a draft order taken straight from the scores in which every move a person makes is recorded with its reason, until the final order is written up with a file the tracker can import.

Its purpose is to keep judgment in the order while making it visible. A backlog ordered by feel cannot be defended when someone asks why their item sits below the line; one ordered purely by score hides the calls that were actually made.

The recognizable task

Typical trigger
  • More validated items than capacity, so an order is needed
  • Priorities are contested and the current order cannot be defended
  • A periodic re-prioritization comes due
What good looks like
  • Every item carries a score per dimension, a second-lens score and a confidence mark, with blanks left blank
  • Every departure from the score order is recorded with its reason
  • The capacity line is drawn from a stated number, and the cost of waiting is shown below it