The idea
A timing comparison should specify when each benefit is received and when it can be used. The illustration contrasts a smaller reward today with a larger reward received later, giving both the same validity from receipt and making clear that the later option provides nothing today; otherwise validity or eligibility could explain the preference. Use the framework to test early value and visible progress while explaining the actual schedule rather than making a delayed reward sound instantly available.
Use it thoughtfully
- State receipt timing and validity clearly.
- Keep eligibility comparable when testing rewards.
- Offer useful early value and visible progress.
An example
In an illustrative loyalty choice, customers compare a small data reward received now with a larger one received later. Both last the same period after receipt, and the team checks whether customers understand the delay before interpreting their preferences.
A question to try
Is the customer choosing reward timing, or reacting to different conditions that accompany each option?
A useful framework is a starting point, not a guarantee. Effects vary with the audience, product and situation. Use truthful evidence, respect customer choice, and test the result.