If employees have to leave a request to find a customer identifier and then search for the request again, you can investigate that detour. You do not need to redesign the entire application at the same time. The work can begin with opening the request and end with returning to the previous list position.
Choose a small but complete piece of work
“Modernise the detail page” says little about what should become easier. “Resume a case after asking a follow-up question” describes a useful unit. It includes the entry point, required information and a recognisable finish.
The GOV.UK live-phase guide covers continuing to improve an existing service. That does not mean constantly rebuilding everything. Define a bounded task and check which neighbouring functions depend on it.
In the assumed customer-identifier case, first establish whether people need to read, copy or edit it. Only then can you choose between displaying information within the case, providing a preview or linking elsewhere.
Separate preserved rules from new decisions
To keep a small change from disrupting the rest of the workflow, you also need the rules that must remain. These include identifiers, business states, permissions, saved filters and links from other views. Focusing only on the new screen can easily leave those dependencies out of the design.
A short change matrix helps the discussion:
| Preserved | Changed | Still unresolved |
|---|---|---|
| Existing case identifier | Customer information is reachable in context | Which details may this role see? |
| Saved filter | Returning restores the previous position | What happens to the list after an edit? |
Resolve the two open rules with domain specialists and developers before detailing the views.
Do not confuse familiarity with usability
Experienced users often develop ways around obstacles. Their workaround is valuable research material. It does not establish that the interface works well, nor that every habit should be removed.
Trying the revised task with suitable people lets you check both the new route and the transition from the old one. If a familiar entry point disappears, existing users need a clear replacement or a hint where they can continue. A long set of release notes at login rarely helps with that specific transition.
Check the change in operation
Describing how you observed the current flow and what should improve gives you the same task to check after release. Any processing-time measurement is comparable only when the start, finish and interruptions are defined consistently. The new layout alone does not demonstrate time saved.
The current workflow beside the intended change shows which information and actions will disappear, be added or need preserving. That gives UX decision support a concrete basis for the unresolved choice. If the question is how your team prepares and decides on changes together, that belongs in a UX working-practices review.
