Decisions · Layer 1
Should you manage loyalty liability as a growth constraint
Manage points liability as a live constraint on earn, expiry, transfer, and redemption design. Protect the member promise first, then change funding mechanics with evidence.
Manage points liability as a live constraint on earn, expiry, transfer, and redemption design. Protect the member promise first, then change funding mechanics with evidence.
## The decision boundary Liability grows when issuance outpaces redemption, point value rises, or a new promise expands access. Track the balance ledger, expected redemption cost, and breakage evidence separately.
## The options
### Rate discipline Choose this when issuance creates more exposure than behaviour. The cost is additional operating complexity.
### Redemption expansion Choose this when useful catalogue access can convert balances. The cost is more measurement and exception handling.
### Liability reset Choose this when old rules no longer match the promise. The cost is a stronger funding and review obligation.
## What it costs you The currency is liability, margin, engineering time, operating capacity, or member trust. In a hypothetical illustration, 2 points per dollar on 400 dollars of spend creates 800 points. At a hypothetical 1 cent value, that is 8 dollars of liability. Ten comparable cases therefore represent 80 dollars of stated value.
## How to decide 1. Name the behaviour or obligation the rule must control. 2. Identify the independent evidence that proves the event. 3. Price the member, operating, and liability cost of each option. 4. Choose the least complex control that protects the least reversible outcome. 5. Set the evidence that would cause a later review.
## What breaks The failure mode is a rule that measures its own success. Keep source evidence, eligibility, issuance, adjustment, and fulfilment separately observable. Revisit the recommendation when the balance has no meaningful value or the event cannot be independently verified.