Learn from repeated actions Anticipation
Finding
When deleting something, we often get a confirmation:
Are you sure you want to delete this?
That's useful for preventing mistakes, but when a user is deleting many items, asking the same thing again and again becomes annoying.
Idea
If the user repeatedly deletes items, the system can understand that they are intentionally cleaning up.
After a few repeated deletions, we can remove the confirmation and give them an Undo option instead.
Delete → Delete → Delete → Delete
instead of:
Delete → Confirm → Delete → Confirm → Delete → Confirm
- Untitled project Delete Delete this? Cancel Delete
- Old screenshots Delete Delete this? Cancel Delete
- Draft: pricing page Delete Delete this? Cancel Delete
- Scratch notes Delete Delete this? Cancel Delete
- Test project Delete Delete this? Cancel Delete
- Archive 2025 Delete Delete this? Cancel Delete
Why I like it
It handles both situations:
If it was a mistake, the user can Undo it.
If they are intentionally deleting many items, they can do it much faster.
The system is not just following a fixed rule. It is responding to what the user is doing.
One thing to consider
I would keep this behavior limited to the current session or task, especially for destructive actions.
The interface should adapt to the user's behavior, but still keep them safe.