Select Page

Vigor CRM

Problem

This was an internal tool redesign of a customer relationship management from Dynamics to IFS. 

Reading time: 7 minutes

Vigor is an industrial business with seven locations in Oregon, Washington, and Alaska with over 2,300 employees. The customer relationship management (CRM) system with projected sales growth and customer retention opportunities was outdated. This aging data was missing important information the sales team needed in order to make business decisions about where to put their time and effort for the company strategy and approach. The sales team needed a tool to document their touch points with customers and house accurate data to support those efforts. Due to the nature of the project involving proprietary financial information dealing with government entities this case study is limited to comply with NDA.

Timeline

10 Months

Role

My role was UX Designer; conducted research, data analysis, prototyping, design, usability testing. The team also included the UX Researcher and Developers. 

By the end of the 10-month project, our team designed an internal CRM tool that provides an easy system for documenting customer opportunities and contacts. The CRM also included a way for the entire sales team to interact as a community and keep track of sales touch points. 

Approach

We began with a discovery stage that included internal stakeholders and IT consultants. This project is unique over other projects because of the nature of the data and timing during an in progress acquisition. An in-depth discovery stage was the right approach for this project to identify the many locations the data was housed over 10+ years.

Old Interface – The Endless Scroll

The old interface was very overwhelming at first glance from a UX perspective with many unnecessary fields that would never be filled. Reporting was cumbersome and difficult in the old interface. All salespeople relied on one person to run the report which took time to generate and customize. The time between edits made and reporting out made it difficult to keep up with pipeline updates in the market. 

Assumptions

I made assumptions about how easy it would be to map the old CRM Dynamics data to an already in-use internal tool. Since part of the company was already using the IFS software, we needed to close the gap between our data to the data already in our tool before migration. When you move houses you have different rooms in the new house than you did in the old house. We had to take into account those space and shape of those new rooms before we moved in our data from the old house.

New Interface – Live Edits

Reporting is seamless in the new interface, IFS,  so that all salespeople could export reports instead of relying on one person to run the report. This closed the loop on reporting and made live edits during meetings possible.

Challenges

The most challenging parts of this project were getting team agreement on data points that were necessary to track projects. When it came to areas of ambiguity it was necessary for the team to meet and discuss what each field meant to members of the sales team who represented different sectors of the industry and come to agreement about the best unified path forward.

Conclusion

The project concluded with a live product for the sales team to input data, groom their opportunity pipeline and contacts, and export to excel to utilize for metrics. The new CRM is live in IFS with the sales team using this as their main point of data entry for customer tracking. During usability testing we were able to troubleshoot live with the sales team and Developer to customize screens to further streamline their input process. Weekly reporting is now updated live with the sales team viewing entry of information.

Future ERP Ecosystem

The IFS CRM project is part of a much larger ecosystem redesign for enterprise resource planning. I’m happy to talk more about the project scope and my role in an interview.

Pin It on Pinterest