Chase Merchant Services - Enterprise Pricing Model (2018-19)

Problem space

“Create a solution for RM or BDR who want to efficiently work with their client not only during the pricing model process but also before and after the deal”

Pain Points: Before creating a pricing model

• Manually migration data between EPM and Salesforce increase errors and reduce efficiencies

Pain Points: During the pricing model creation

• Different pricing models are generated and managed by a different platform

• Difficult to collaborating with additional tools

• Long and complex pricing deal approval process

Pain Points: After creating a pricing model

• Won't be able to propose a new pricing model for the merchant based on an existing deal (Current/Current)

• There is no way for managers to track their sales team performance

PRODUCT GOAL

Business goal: Manage pricing model by automating manual processes, which will reduce errors and increase efficiencies.

User goal: set clear expectations, get more merchant deal opportunities and easy approved process.

Design goal: Create a "One-stop Shopping" experience for generating and managing all pricing methods. Simplify team collaboration process and manager approval procedure. Fix current usability problems.

DESIGN SOLUTION

• The new design provides a dashboard view for Business Development Representative and Relationship Manager to analyze their sales data. There is another Dashboard view gives our Sales Manager a clear vision to track their sales team performance.

• Sales Manager also be able to track/manage their team members status in detail on My Team and My Team Model page.

• Model and Scenario management were available on the new design for both sales and sales manager.

• Redesigned Pricing Scenario page provides a wizard view by category for scenario details, as well as real-time collaboration and simplified finalize/approval function embed.

• The competitive view has been integrated into the pricing scenario page, it helps the user to easily compare "current/current" and proposed scenario.

• During the pricing process, additional calculation tools floating on the bottom of the page that ready to be used as a multi-task window that provides side by side experience for the user.

DESIGN PROCESS

User Research (Contextual Interview and Analysis)

To better understand the user, I conducted user insights research to understand and inform Stakeholders and the project team on pricing tool processes and opportunities to improve.

The research focused on US Retail and Canada, Relationship Managers (RM) and Business Development Representatives (BDR), for North America platforms (NAP) and Global Platforms (GP). Pricing tools studied included the Enterprise Pricing Module (EPM), Global Pricing Calculator (GPC) and the Competitive Analysis Tool.

Research Population:

Managers, individual contributors, and the EPM Retail/Canada trainer. Most users were strictly NAP or Global, and so employed only one—EPM or Global Pricing Calculator—but a few currently used both, or had used the alternate on in the past. Relationship Managers managed from one or two clients (Premier/Omni) to forty or more (Government Healthcare/Higher Education). There is a large range in the number of models having been created, from just a few to over 1,100. Total 44 BDRs and RMs participated in this one-hour long interview.

Key Findings:

• “Almost everything has to be approved at the highest levels because we will be priced out of the market if we don’t have thin margins.” While everyone understands the need for the approval process, several felt the process could be improved to reduce timeframes and eliminate approvals for deal margins that were always approved.

• Users really liked the Errors message area that tells you when something is not complete or the contribution margin is not met.

• Note: There is no equivalent Errors area in GPC and this was noted as a significant usability difference between GPC and EPM.

• Observers noted that there was always something displayed in the Errors area, which caused experienced users to ignore the area and confused novice users. This feature is very helpful but needs some adjustments.

• Cannot Finalize the scenario if it has an error. “Would be nice to be able to get an error alert but still be able to finalize the scenario.”

• Login through Citrix is cumbersome and it times out. If Citrix times out the EPM work is lost, so an auto-save function would be helpful.

• RMs need to create “Current/Current” scenarios (current volume, current pricing) to provide a baseline for comparing proposed pricing scenarios and to justify any decrease in pricing. RM may reach out to the merchant to determine if they anticipate significant growth.

• Salesforce opportunities are not transferred from Sales to RM once the merchant is boarded, but the Salesforce opportunity is not transferred. The RM creates a new Salesforce Model and re-enters all relevant data.

• Canada Retail BDRs use the Competitive Analysis tool to compare the current payment plan (competitor) vs the proposed chase payment plan, then use the Merchant Service Proposal to explain to the merchant.

• A model typically includes more than one scenario. User cannot copy an entire model to a new model. When creating a new version of the model, the user can only copy one scenario to a new model, but then has to manually recreate all the other scenarios in the new model. This is very time-consuming.

• If the user transfers a model to their manager for assistance, they don’t have a version to keep, so are unable to tell what changes their manager made when the model is returned to their ownership.

FLOW MODEL

After I had enough data, I drew flow models to understand the current user experience and to identify the merging and breaking points. This helped me to gain a better understanding of the entire process for a different user profile.

Personas and user journey mapping

Ideation

I presented the research findings and analysis with the stakeholders, while we leveraged our collective wisdom by the cross-functional team and bringing many ideas to the table. By sharing interview insights with the product team and co-created the solution together.

information architecture

Define Style Guide

Based on regions, segments, and bank channel alignment, JP Morgan Chase has different guidelines that cover brand architecture, logo reproduction, approved typography, official color values and more.

The EPM is the project that crosses regions and banking channels. So a specific style guide was required for this project. I've analyzed different style guide and made a purpose to stakeholders and product team. Then worked with the style guide team to customized some design elements that required for the EPM project.

Wireframes

Final Design 

Back to My Work