BUILD+IMAGE1.png

Copy of Enterprise Pricing Model

Chase Merchant Services - Enterprise Pricing Model


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

PROJECT BACKGROUND

The Enterprise Pricing Model (EPM) is the enterprise-level tools for our Sales team daily usage that run into a variety of pricing models for processing credit and debit card transactions of each merchant.

My ROLE

UX lead for the EPM project. Conducted user research and owned end-to-end experience design. Collaborated with multiple cross-functional teams. Worked with style guide team defined design guidelines.

 

BUSINESS GOAL

Reduce errors and increase efficiencies for sales team

 

PEOPLE PROBLEM

“I’m losing deals because of spend long time on generate the pricing model and work with manager on the complex approval process.”

- Sales

 

TOP ISSUES FOR SLOW THINGS DOWN

 

HIGH LEVEL PRODUCT THINKING

Create “one-stop pricing” experience that improve the pricing process

Build in the Manager Approval Process into the EPM

 

pain points

“It’s hard to identify the pricing errors because I don’t know where the errors coming from.”

- Sales

“I need to use calculation tools to complete my pricing deal, but I have to login to different system and jump back and forth to use it every time.”

- Sales

 

Previous Experience

  • Long pricing form with accordion section that hard to navigate

  • No error notice, users have no idea where the error come from

  • Have to scroll to the bottom to see the pricing summary results

  • External tools usage

 

design solution

  • Redesigned Pricing page provides a wizard view that break each section down into categories, as well as different error message notice user.

  • 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 fixed 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.

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

 

new experience

New Pricing page layout with Vertical Wizard on left side, and three different ways to show error message notice

Integrated Tool bar fixed on the bottom, simple click to bring up multi-task window that provides side by side experience for the user to calculating during pricing process

 

Sales Pricing Model Management

Sales Pricing Scenario Management

 

pain points

“We always spend so long to work together on a pricing deal approval, we usually loose the deal during this time period.”

- Sales Manager

Sales Pricing Model Management

Pricing Scenario Page before

Sales Pricing Scenario Management

 

Additional Calculation Tool for Pricing Scenario

Competitive Analysis function for Pricing Scenario

 

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