Testing Optimistic UI Rollback by Letting Demo Users See a Failed Change

A public SaaS demo can show whether an interface handles a rejected change by displaying an immediate update, deliberately rejecting the underlying operation, and checking what users understand afterward. The approach separates a pending change from a confirmed one, since a fast animation signals responsiveness but does not prove the change was saved. The exercise uses a fictional task board with a disposable item, a known saved value, and a reversible action so the difference between displayed and stored state is easy to follow. Testers are asked what they believe has happened, what they expect after a refresh, and whether the interface makes the failure clear. The author notes that the example is a proposed review exercise, not a report on any specific product, and that each product needs its own recovery policy.