When points liability belongs to product analytics

Documents and charts being reviewed at a table

Finance already knows the outstanding points balance. They have to. What they rarely get is a sentence about which product choice moved it. A double-earn weekend, a quieter expiry copy, a wallet pass that suddenly shows a larger number in bigger type — these are UX decisions with balance-sheet consequences. Leaving them entirely in the close pack is how product teams stay innocent and then surprised.

Module five of Loyalty Signal Architecture is the driest week on the calendar. Students still tell us it is the one they reopen. We take a liability movement, strip out accounting adjustments, and ask which in-app surface changed. If nobody can name a surface, the movement is not a product story yet, and we do not invent one.

Expiry copy is a product surface

A grocery banner once softened expiry warnings because the tone felt “unfriendly.” Burns accelerated in the following fortnight, then earn slowed as guests decided the programme felt extractive. Liability looked “healthier” in the close. Attachment did not. The interesting chart was not the balance; it was silent earners after a harsh burn.

This is why we refuse to treat liability as a single KPI tile. It is a downstream reading of several upstream choices: earn rules, expiry UX, redemption merchandising, and whether staff can still explain the mechanic at till.

What to bring to the close

One paragraph naming the UX change, one chart of intended versus clearance burn, and the liability delta with adjustments removed. If that packet feels too small for your board, add an appendix. Do not add a second story.

Observatory Circle reviews always include this packet. Signal Desk students practise it on their own programme without our written brief. Either way, stop letting finance be the only team allowed to look at the number everyone is already arguing about.