# How to Redesign a Legacy System Without Disruption

Source: https://www.jvds.cn/en/share/ui-design/legacy-system-ui-redesign
Language: en
Published: 2026-09-26
Author: JVDS Design Studio

When designing a newly approved product from 0 to 1, designers can explore cutting-edge layouts freely. But redesigning the UI of a legacy system that has been running inside a company for eight years and is used intensively every day by more than a thousand business staff and warehouse administrators is a different matter. If a designer starts with “shock therapy”—replacing all the top menus with a collapsible sidebar, moving every table button, and turning all the dense information into spacious, oversized cards—the internal complaints line will absolutely be overwhelmed on the first day the new version goes live.

Why? Because although the old system looks ugly, has dated colors, and is a maze to navigate, **experienced employees have already developed “muscle memory” for it**. A warehouse clerk can issue a document with their eyes closed by pressing `Tab` three times and then Enter; a finance specialist can spot an unusual number at a glance in a dense table with 40 rows on one screen. If you double the row spacing for a “modern visual feel” and the screen can now show only 10 rows, that is a serious loss of working efficiency for them, rather than an upgrade.

![Artwork](https://www.jvds.cn/upload/2026/0824/1787562629460-834574.webp)

When [JVDS](https://www.jvds.cn/en/service/uiux) takes on complex legacy system redesign projects, we consistently follow a strategy of “respecting existing business workflows and evolving smoothly in three phases”:

## Phase One: Keep the interaction paths and start with “visual decluttering and component reskinning (UI Reskin)”

If the underlying backend architecture will not be rebuilt in the short term, the safest first step is to **keep the existing menu hierarchy, form field order, and keyboard shortcut conventions unchanged**, and first address the most visually exhausting issues:

![Artwork](https://www.jvds.cn/upload/2026/0824/1787562629460-642046.webp)

- **Remove the jumble of highly saturated colors and thick double borders**: Older systems often draw table borders as harsh, thick black lines or use bright red and green backgrounds everywhere. Introduce modern neutral grays, clear font-weight contrasts, and a consistent component stylesheet first, and the interface immediately becomes clean and fresh.
- **Offer a “Compact / Default” density toggle**: Retain a compact table view with high information density for roles involving intensive data entry and checking. Never sacrifice the amount of information per screen for appearance.

## Phase Two: Consolidate steps in the most painful 20% of high-frequency core workflows

Sit beside frontline staff and watch them work for half a day. Identify the “back-and-forth trips between pages” that truly drive them crazy, and make targeted changes:

![Artwork](https://www.jvds.cn/upload/2026/0824/1787562629460-325968.webp)

- For example, staff may previously have had to remember the document number after completing a goods receipt, then go to another menu to search for that number and upload a quality inspection attachment. In the redesign, combine these two steps in the same drawer workspace. Experienced employees will immediately notice that they need five fewer mouse clicks and will naturally embrace the redesign.
- For “zombie features” accumulated over ten years in the old system—obsolete buttons or reports that usage data shows nobody has clicked even once in six months—first move them into a secondary “More” menu and observe for a month. Remove them entirely only after confirming that nobody needs them.

## Phase Three: Run both versions in parallel and provide “lightweight transition guidance”

Avoid suddenly shutting down the old system altogether in the middle of a Sunday night. Early in the rollout, keep a prominent “Return to the old view (30-day transition period)” toggle in the top bar, and add a lightweight, one-page tooltip guide beside the 3 core features that have moved, telling experienced staff: “The previous \[Batch Export\] option has moved to the upper right of the table, and now supports exporting by custom fields.” Only when more than 95% of users stop switching back to the old version can a disruption-free system upgrade truly be considered complete.