Create Invoice

Overhaul of PayPal Invoicing on iOS App

Overview

Invoicing is an integral part of all SMB life cycles. Key aspects for ideal invoicing workflow include time efficiency, standardization, automated invoicing software, online payment integration as well as invoice tracking and management. 

The PayPal Invoicing team was tasked at overhauling the product end-to-end in order to stand out in the competitive landscape and increase monetization.

Strategy

Make use of progressive disclosure within the experience. An interaction design technique often used in human computer interaction to help maintain the focus of a user's attention by reducing clutter, confusion, and cognitive workload. This improves usability by presenting only the minimum data required for the task at hand.

Role

Strategy, Cross-team Collaboration, User Research, iXD, Prototyping

Team

Director of Invoicing PM, Merchant App PM, Analytics (2), FE dev (3) and BE dev (1)

Tools

Sketch, InVision, Miro, Confluence


Business App drop-off metrics

Business App drop-off metrics

Top inputs entered

Metrics from Analytics team showing top fields populated.

Variants tested in UER - 🔎


Team developed and deployed 2 variants to test against control.

Team developed and deployed 2 variants to test against control.


Final Designs delivered

Post A/B testing results which show that the Inline variant converted better than Step-by-Step variant. Good to note that both variants performed higher than the Control.


Team Unity

  • The entire team including product managers, developers, analytics, and design were active involved throughout the multitude of sprint work. 

  • PM and designer facilitated in lab user testings.
    FE & BE developers were invited to the sessions and were eager to join sessions.

  • Our squad (3iaB) met afterwards for collective findings and readout.

  • Once A/B testing plans were in place everyone were on board with the direction with what being built and deployed.

Outcomes

  1. New users mostly filled in the basics and sent invoices out.
    For those who used the ‘More details’ regularly, consider to set threshold (5+ clicks) to open by default to reduce need to expand.

  2. The challenge to test will still be legacy users who want everything the way it is.

  3. For desktop users, consider to have Progressive Invoicing as default. For legacy users ease in the changes by opt-in users to choose ‘Simplified Invoicing’ vs. ‘Classic Invoicing’

Omni Channel improvements

  • Native Mobile Merchant App success brought appetite and wins for desktop create invoice simplifications.

  • The deployment and minor tweaks of A/B test results ramped to 100%.

  • Responsive designs were prioritized and leaned more towards mobile UI design than desktop version.