The decision role — Examples

Example 1 — Ordering a wish list against a stated goal

The backlog below has been collected over three months in arrival order, so the team is picking by loudness. The decision role chooses what the team works on next and says why, against a goal the business agreed. Write the goal first, then order the list, giving the top three a reason that names it.

Backlog, in arrival order
  saved payment methods          dark mode for the app
  refunds before shipping        better search on the help site
  export to CSV                  single sign-on for business buyers
  a second status dashboard      bulk edit for the admin screen

Solution

Goal: cut repeat-purchase abandonment at the payment step from 42%
      to 30%, measured monthly, by the end of Q3.

1 refunds before shipping   refund disputes top the support contacts
                            that block the Q3 goal
2 saved payment methods     directly targets the abandonment number
3 bulk edit                 removes a manual step for the team
                            handling the refunds
4 single sign-on            serves business buyers, not the goal
5 export to CSV             requested, no line to the goal

Deliberately not doing: dark mode, the second dashboard, help search.

The goal is a change with a measure and a date, so every reason can be checked against it and the order is judgement rather than arrival time. The mistake is a reason that restates the item (“refunds matter”) instead of naming the goal it serves; without the goal, any ordering is defensible.

Example 2 — Writing down what the yes cost

You agreed to build refunds before saved payment methods, and the decision has been repeated in three meetings without anyone recording what it gave up. Every yes is a no to something else, so the trade should be visible at review. Turn the note below into a decision entry with the goal, the alternative it beat, and a review date.

Meeting notes: refunds first this quarter. Support keeps asking
about saved payment methods; we said not yet. Someone asked why,
and we explained it again.

Solution

Decision    Ship refunds before saved payment methods.
Goal        Cut repeat-purchase abandonment at the payment step.
Foregone    Saved payment methods, which support expects to remove
            around 30 calls a week.
Reason      Refunds block the Q3 goal; payment methods do not.
Review      6 June, or sooner if the abandonment number moves.

The entry names the next-best alternative and the goal it lost to, so a later challenge is answered from the record instead of re-argued. The common failure is recording a conclusion with no alternative attached, which makes any reordering look like a change of mind, not a response to evidence.