≈ volna.computerSince February 2026
← My notes

Undo after another edit

An undo button becomes harder to design when several people or agents can change the same thing. Restoring an old value may erase work that happened after the action being undone.

Consider a shared task list. An assistant moves a deadline from Tuesday to Friday. Later, a colleague moves it from Friday to Monday after speaking with the customer. The user returns, sees the assistant's change in an activity log, and clicks Undo. Setting the deadline back to Tuesday would also discard the colleague's decision.

For this interface, I would make undo conditional. The change record would contain the previous value, the value written, and the revision produced by the write. Before restoring Tuesday, the service would check that the task still has that revision. The check and the restoration must happen together, so another edit cannot slip between them.

When the revision has changed, the interface should show the conflict. It can say that the assistant set Friday, a colleague later set Monday, and restoring Tuesday would replace Monday. The user can then choose with the current state in view. A revision check may catch unrelated edits too. Tracking revisions per field can reduce those interruptions, at the cost of more complicated bookkeeping.

Some actions need a different recovery operation. For a hypothetical invitation system, revoking an invitation can prevent its future use. The recipient may already have read the invitation email. The button should say Revoke invitation, and the confirmation should explain that the email remains in the recipient's inbox.

I would test these cases with two actors before putting undo in an activity log. One test would change the same field between the original action and its reversal. Another would perform an action with an external effect. Both force the interface to explain what the button will do when the history is no longer simple.