Make the next action clear. Explain what can be recovered.

A focused assessment can identify where the current journey is confusing; a wider engagement can cover research, information architecture, wireframes, interactive prototypes, visual design and reusable patterns. We choose the extent of work with the team rather than assume that every usability issue needs a complete redesign. The brief identifies intended users, representative tasks, devices and the decisions the design should help resolve.

Discovery should establish what the product actually permits. If an item can be archived, the design needs to know who can find it again and what restoration changes. If permanent deletion is available, its meaning and any restrictions come from the responsible product and technical owners. A screen label should communicate an agreed rule rather than create one accidentally.

Design reviews use realistic content and relevant alternative states. We can agree evaluation with appropriate participants, an internal walkthrough or another suitable method, keeping each finding attached to the version and task examined. The handover includes responsive layouts, interaction notes, content and unresolved dependencies. Backend storage, retention and permission enforcement are implementation work to specify and verify in the built product.

Suppose an operator wants to tidy a list by removing an item that is no longer active. An icon labelled Remove could mean hiding it from their current view, archiving it for the team or permanently deleting it. The person cannot make an informed choice if those outcomes share the same unexplained control. This is a hypothetical single-item design example, not a Bristol product result.

Work through the ordinary archive action first. Show what will disappear from the active list, where the archived item can be found and what confirmation the person receives. Then review finding that same item and restoring it. A successful restoration should make its destination understandable, including the case where its former grouping has changed.

Consider permanent deletion as a distinct decision only if the product actually supports it. Review the consequence before commitment and the result afterward. An Undo message should only describe a recovery action that the implementation can provide. Use keyboard operation and a narrow screen during the walkthrough; the meaning should remain clear when a hover tooltip is unavailable.

Share the current screens, a redacted item and the reason it should leave the active list. Explain whether archive and deletion already exist, who can use them and how people recover work today. Include the person who owns retention decisions and the developer who understands implementation constraints. These inputs help distinguish a design ambiguity from a missing product capability.

Bristol collaboration uses agreed remote sessions with Europe/London and Asia/Kolkata named in dated invitations. Consolidated feedback should identify the task and prototype version, so a visual preference does not silently replace an approved behavioural decision.