Legacy-to-modern transition direction
Legacy-to-modern transition direction is the plan for moving users from an old interface to a new one while the business keeps running.
Long-term users work fast in the legacy system, and they judge the new interface against that speed.
Key facts
- Experienced users judge a new interface by how fast their frequent tasks are.
- Frequent tasks in the new interface should be at least as fast from the keyboard.
- Domain terms users already know should stay.
- Records migrated from the old system should show their origin.
- If experienced users remain slower after the agreed observation period, Redbrix investigates task steps, shortcuts, training, performance and changes in work complexity.
What it covers
- Keyboard paths for experienced users
- Coexistence of old and new screens during a staged rollout
- Terminology carried over from the legacy product
- How migrated records look in the new product
- Measures of how users adapt after the switch
Who uses it
Two groups judge the transition differently. Long-term users compare it with the speed they had. New customers and prospects compare it with competitors. The product owner has to keep the first group productive while winning the second.
What makes it hard to design
Keyboard paths. Experienced users often work from the keyboard.
Staged rollout. During a module-by-module rollout, users move between old and new screens.
Terminology. Domain terms users already know should stay, even if the new team prefers others.
Migrated records. Records carried over from the old system often look incomplete. Marking their origin stops users from treating gaps as errors.
Keeping the familiar scenario and the structure of the data lets users recognise it in the new interface. A staged rollout can reduce disruption, but dependencies and the cost of supporting two versions may favour a coordinated switch.
Trade-offs
- Keeping legacy patterns reduces resistance, and old structural problems move into the new product with them. A clean break fixes the structure, with a temporary drop in productivity while users adjust.
Common mistakes
- New names for terms users already know
- Navigation between old and new screens left undesigned
- Frequent tasks that need more steps than before
- Migrated records shown as if they were complete
Redbrix agrees an observation period based on task frequency, compares equivalent tasks before and after rollout, then investigates navigation, shortcuts, training and system performance before attributing the cause.
Where Redbrix has worked on this