Skip to content
Interface language: English
Design / Signal

Delete, undo, recover: three different moments in an interface

Undo and the recycle bin need different rules. Establish which item returns, where it goes, and what happens to its associations and access.

Article language: English

A person lifts a sheet from an open sample case on a wooden table beside a simple meal.
In this article

An "Undo" button can carry a surprisingly large promise. Will it restore the same file, its former folder, its project links and colleagues' access? Or will it merely put a row back on the screen? Before designing that small button, decide on the answer. The label must not promise more reversibility than the application can deliver.

In a fictional materials library, we delete a draft instruction. Moments later, we discover that it was still needed. That is a simple starting point, but the next step might be undoing the last action, finding the item in the recycle bin or recovering it with help from the right person. Each route has its own limits and its own way of making the outcome recognisable.

We are not deciding here how long a company should retain data or when the law requires it to delete it. The interaction must match the system behaviour that has been agreed. Its job is to show the next available step and the identity of the recovered item clearly. A brief "Done" should not obscure that distinction.

Undo must reverse a specific action

Start with the word "Delete". In one place it means deleting a file, in another removing it from a collection, and in a third hiding a column. If the application uses the same label for each, people may expect the wrong result. Putting an item back on a list is not the same as recovering its content.

For a saved products list, "Remove from list" may be enough. The guide to saved product lists (in Polish) discusses designing such a list. It does not delete the product from the catalogue. With saved table views, the thing being removed is a display configuration, not the records. The guide to saved table views (in Polish) discusses their design. Naming the object alongside the verb saves people from guessing which layer of the application they are changing.

In the library, a deleted draft might go to the recycle bin while a temporary button undoes that particular operation. One possible message is: "Draft 'Shelf assembly' moved to the recycle bin." An "Undo" button appears beside it. The user can recognise both the item and the effect without opening a separate change log.

GNOME identifies an undo button after a destructive action as one use of a toast, a short message in an application window. It also distinguishes information about a single event from an ongoing state. This is a useful pattern, not a definition of the recovery mechanism.

Undo needs to be tied to the right operation. If someone deletes two drafts in succession, a lone "Undo" should not require them to remember which one it concerns. The interface could show two recognisable messages or a combined scope, if the application can actually reverse that scope. A new action should not silently change the target of a button that was already visible.

Also distinguish undoing an action that has happened from cancelling an intention. If deletion is still waiting to be saved, "Cancel" can withdraw the pending change. If the server has already carried it out, a restoring operation is needed. The two may look similar on screen, but the message must reflect the actual state. In the specification, show what happens when the connection is lost so that a disappearing row is not automatically treated as confirmed deletion.

Undo is not the same as creating a similar new file, either. If the application restores a different record under the same name, earlier links or associations may not return. Decide what must retain its identity. For the user, a simple test is whether a previously saved link leads to the recovered draft according to the agreed rule.

A shared library also contains other people's work. After the draft was deleted, someone may have added new material to the same project. Undoing the deletion should not accidentally return the entire library to an older state and erase that later work. The expectation concerns the chosen action and its effects. A broader restoration needs a separate decision and a clearly described scope. In the test, keep the new material as a checkpoint that must remain untouched.

When someone presses "Undo", show that the operation is in progress if the result is not immediate. A success message is justified only once recovery is confirmed. Without confirmation, the user needs a way to check the state. Pressing again should not accidentally create another item or change a different operation.

Do not assume that every brief opportunity to respond is enough for everyone. Someone may use a keyboard, need longer to read a name or be looking elsewhere on the screen. If the button disappears, explain what route remains afterwards. How long a message is visible and how long recovery remains available are separate decisions.

Fluent 2 advises against using toasts for necessary actions and points to a more persistent surface, such as a message bar or dialog. It does not follow that there is a universal number of seconds for undo. The component should suit the importance of the information and the way people reach the next action.

In the library design, the recycle bin can provide that later route. The disappearance of the temporary message then does not end the possibility of recovery. If the system has no bin and truly closes that possibility after a set time, do not describe it as a complete restore model. When the limit affects the decision, make it known before the action.

In the recycle bin, find the right object, not just a familiar title

After a break, someone returns to the library. Three files in the recycle bin are called "Shelf assembly". Depending on the actual work, they need to recognise the project, deletion date, author or version. A name alone is not enough for a responsible choice, even if all the titles in the demonstration data happened to be beautifully unique.

The bin view should show the information needed for identification while respecting permissions. That does not mean exposing every document's full content. A preview or a recognisable description of the context can help. Decide what to show in conjunction with the application's behaviour, rather than adding arbitrary data simply to make recognition easier.

Once the item is selected, establish where it will be restored. That might be its previous folder or a chosen destination, if the solution offers one. But what happens if the previous folder no longer exists? That is a question about the item's relationship to its surroundings, not a cosmetic detail of the confirmation.

Aeneia conceptual photography

SharePoint documentation describes restoring a deleted folder when an item inside it is restored. The recreated folder contains the restored item. Restoring the folder itself, by contrast, can include its former contents. The scope therefore depends on the action selected.

We do not automatically transfer that behaviour to our own library. The source shows why dependencies need an explicit decision. Recovering one instruction should not silently restore a whole set of materials if that is not what the user requested. If the system requires a wider effect, the interface should explain it.

With Aeneia Design, this route can be designed from selecting the item to confirming where it returned. The work needs the application's actual rules, examples of similar names and its dependencies. Screens and messages must reflect the recovery mechanism agreed with the implementation team.

Moving files between folders (in Polish) also requires naming the destination and the effect on sharing. Recovery may involve a similar decision, but it need not be an ordinary move. Do not assume that a file's presence in its former location by itself confirms that every previous collaborator has the right access again.

A name conflict also needs a rule. A new file with the same title may already exist at the destination. The user needs to recognise both items and the effect of the choice: keep both, use a different name or refuse the operation according to the application's rule. Automatically overwriting current work would be a serious expansion of what "Restore" means.

Check what happens if permissions change between deletion and recovery. Someone may have lost write access to the former folder. The interface should not promise successful restoration to a location the system will not let them change. It needs an accessible route to an explanation or a choice of destination, if that choice has actually been provided.

If recovery is refused, show the appropriate route for further help. If another role is needed, the user should be able to provide a recognisable item identifier and describe the obstacle. They should not have to send anyone their account password or search again using only the title. The design can help prepare such a request, provided that it matches the application's real support process.

Restoring several items can also produce a partial result. If two of three drafts returned, the summary should say two and identify the remaining item. A later retry should concern the missing scope. If the solution instead rolls back the whole operation, show that outcome. People should not have to count files themselves to guess whether the button kept its promise.

An active filter may be why a recovered draft still does not appear in the normal list. Instead of another "Restored" message, offer a way to reach the right item or location. The recipient should be able to see the result without manually reconstructing every setting. Recovery then has an outcome that can be checked, not merely a green colour.

Aeneia Design

Let us map undo, the recycle bin and the return to the right location for one kind of material. We will design action names, ways to recognise the version being recovered and conflict messages that match your application's behaviour.

Discuss the design of undo and item recovery

The final confirmation should say what will become irreversible

When a task permanently ends the possibility of recovery, do not automatically copy a quick-undo model. Before the action, show the item and the consequence. If the action ends the possibility of restoring a particular item from the bin, say precisely that for the item concerned. The person needs to understand that, after confirmation, they cannot return by the same route they used earlier to find the draft.

For a bulk selection (in Polish), confirmation must cover the same items the user actually selected. "Delete selected" does not explain whether that means the visible page or the whole set. If some items cannot be changed, show the actual scope of the action rather than confirming an imagined whole.

Do not require a long phrase to be typed merely to make a dialog look more serious. Extra effort needs a reason tied to a specific risk of error. First make the object's name, item count and consequence clear. "Delete permanently" and "Keep" say more than "Yes" and "No" beneath an unclear question.

As the principles of brand voice in interface messages (in Polish) suggest, a joke should not conceal the consequence of deletion. The person needs to decide on the action, not work out what the writer meant by "Say goodbye forever". Concrete language does not deprive a brand of character. At this moment, it shows respect for the user's work.

Test recovery using controlled materials. First, undo deletion of one draft. Second, return after the message disappears and find it in the bin. Third, arrange for the old folder to be missing or for a name conflict. The result should identify the item, its location and the dependencies that actually returned.

Also check the keyboard route and how the message is read with appropriate assistive technology. A button that briefly appears on screen does not prove that a user noticed it and can operate it. On error, retain the selected item's information so that a retry does not require guessing which of several similar titles the previous attempt concerned.

For our library, the correct result is specific: that draft returned with the right identity, to the agreed location and with the confirmed scope of its associations. If only the row title came back, the task remains open. The small button should lead to exactly the recovery the application can perform.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear