Previous
¶ Legacy Solution Evaluation
¶ What it is
Legacy solution evaluation is an optional process when a project starts, which is only necessary when a legacy solution exists for the system to be built.
Depending on the size of the project and the legacy solution, formal user research or simple system analysis could be selected to evaluate the solution. Project managers and the design and development team should be all involved.
The details of the existing approach should be understood as much as possible, and the advantages and the pain points need to be recorded accordingly. A report would be produced as the deliverable of the evaluation.
¶ Why it is useful
When a legacy solution exists, it is natural for the users to compare the newly built system with it and have expectations. The current user behaviours are essential and cannot be ignored. Such facts make understanding the legacy solution mandatory before designing the new system.
In addition, when the legacy solution contains a digital system, the technical specs, like the environment setup and the data migration, should be considered when building the new system.
¶ When to use it
It is preferred to perform the legacy solution evaluation at the beginning of the project. The evaluation deliverable should be used to scope and design the new system.
¶ How is it done
- The stakeholders should provide the description and the instructions for the legacy solution. Demo account credentials are needed if digital systems exist.
- The production team needs to understand the basic of the legacy solution and try the significant use cases as much as possible.
- If the system is too complicated for external parties, user interviews should be conducted with key users.
- Information like user behaviours, pain points, and existing tech stack should be recorded for further analysis.
¶ Do's & Don't
Do's
- Before performing the user interviews, try to locate the right persons in different positions to cover the critical use cases as much as possible.
Don't
- Do not ignore the non-digital part of the legacy solution.
- Refrain from underrating the existing processes being used by the users. They may not be that fancy or modern, but the wisdom lies within may benefit our system design.
¶ Tools needed
¶ Example
