SAMANTHA LEWIS
About
the
Project
Sunsetting Legacy Systems for a Modernized Product
​Overview
Collaborated on updating a legacy system by integrating its functionality into an existing, modern product already undergoing redesign.
​
Problem Statement
The organization needed to sunset the legacy product while ensuring seamless transformation of data tables and the modernization of outdated screens for integration into the updated platform.
​
Role
UX Designer – conducted research, developed wireframes, and created prototypes to support the transition.
​
Solution
Redesigned complex data tables into streamlined, efficient workflows and processes.
Updated screens with modernized features and new components to align with the updated product's overall design language.
Outcome & Impact
Boosted user interest in the modernized product.
Designed 10+ new features that enhanced usability and productivity.
Achieved a 10% increase in user satisfaction.
Improved information flow efficiency by 16%.
Accomplishments
Streamlined a workflow process to incorporate more collaboration between designers, developers, and business analysts.
Implemented and designed 16% of the product's functionality.
Designed over 10+ new or updated features, including: Adding and Updating Cash Credit Line, Skip Auto Pay, Pricing Strategy, and Method Override
Implemented and presented documentation to update the current design system.
pscu
Introducing PSCU, our recent project that focuses on creating a dashboard concept for credit union agents. By integrating multiple tools into a single platform, PSCU aims to improve workflow efficiency and streamline tasks for credit union agents. The project showcases our commitment to innovation and creating user-friendly solutions for financial institutions.
Project Iterations
*Promotions
*Pricing Strategy
Promotions
Problem/Requirement
Redesign four data heavy promotion screens for a better user experience. These screens are from the back end or admin level of the system.
Design Thinking
Since the way the data is displayed was requested to not be changed, UX will examine the best way to structure and display all screens for the user. Do we want to keep them as seperate entities or combine them?
Solution
The screens are related to promotions so UX has decided to optimize the screen, reduce loading times, and easily access each area by using tabs.
Brainstorming/Wireframes
Single Page
Anchor/Jump Links
Tabs
Original Screens
*Originally four screens but only showing two*
Redesigned Screens
Design Process
1. Top Header Bar - information is prominent in three out of four screens. Highlighting this info in a bar header to emphasis important user info
2. Tabs - design for user to easily access each info and to move quickly while looking and locating information
3. Data space - per requirements format exactly like the original screen; elevated fields is information that can be changed/updated.
4. Cancel - button to cancel changes
5. Update - button to save and update changes
Pricing Strategy
Problem/Requirement
Convert data tables information for Current, Next, Next2 into processes where a user can select the specific override and elect to remove or delete the selected override.
Design Thinking
One of the initial requirements was to give the user the option to delete and remove. From a UX perspective we needed clarification on the remove/delete request as most users use and know the terms interchangeably. Our main focus was to not confuse the user and then focus on designing the data into a design where users can functionally understand and use the process.
Solution
Upon clarification and reassurance that most users who will use this feature will know the difference between remove and delete, UX decided to further prevent error prevention and understanding by providing content in the popup/dialog box that will further let the user know the difference between the two functions. UX designs will show how the user can select the fields related to the override to delete and remove.
Brainstorming/Wireframes
Stepper
Cards
Original Screens
*Replica of the data table*
Redesigned Screens
.png)
Design Process
1. Tabs - easy for user to access informaton from different locations under the same category
2. Dropdown - user can select which method they are updating, conserves screen space, and save users time scrolling the page.
3. Cards - groups the related information so the user can easily understand the action they are updating for each method
4. Delete Options - user will be able to select 'Remove' or 'Delete' (i.e. Remove has a certain date the override can be removed and Delete the override will be deleted the same day).
5. Cancel - button to cancel the changes
6. Confirm - button to save and update changes
* 'Current' card only has one option which is 'Delete' which is represented with a checkbox.
