Giving Statements
Pushpay’s Giving Statements tool originally only allowed church admins to generate tax statements once a year. My design work for this feature focused on allowing church admins to generate statements for yearly, quarterly or custom timeframes.
While our UX research team handled user testing activities, I led the design work on our interaction model, prototyping and final UI designs.
Users problem
Pushpay's tax statement feature only allowed users to generate tax statements once a year, forcing users to maintain separate tools for quarterly or custom-date tax statements. This created duplicate work and data inconsistencies throughout the year when sending them to their church givers.
Design solution
To reduce the maintenance of multiple products and improve communication with more accurate financial data for church givers, we updated the existing feature to support quarterly and custom tax statement generation for churches to send out more frequently and accurately.
Userflow for Giving Statements
I led the direction for an improved userflow for Pushpay users. Originally the experience was 5 steps which I reduced down to cut down setup time to generate tax statements. Other significant changes to the new user-flow design I applied included:
Removed unneeded links that were pulling users out of the flow mid-task
Added a statement history view so admins could avoid re-generating statements they'd already sent
Introduced a new configuration page for admins to set their preferred send method — email, SMS or physical mail
Ideation and Prototyping
I facilitated a co-design session with my team to complete low fidelity sketches to increase the range of ideas to help design the prototype for testing. From here I took the strongest ideas and formed a new prototype in UX Pin for testing
From 5 rounds of testing, key trends we found included:
The majority of users wanted to preview and download statements before sending out to their givers so they could be assured of what is being sent out
Users wanted to be able to customize content for their emails so they could be more personable with their messaging
Loading spinners in the prototype gave no indication how long users have to wait until all statements are generated
"It’s definitely improved… Hands down this was much better, much easier to manage and think through. I remember hesitating quite a bit with the other” - Customer quote from user-testing
UX Pin prototype
Co-design sketches
Final UI Design
I utilised our design system to create a consistent visual experience across desktop and mobile. I also helped our development team coding the HTML and CSS/SVG tick animation to appear when statements have been sent successfully.
Mobile UI designs
Pushpay design system:
Compromises we made for our timeline
The biggest challenge I faced was working with a fixed deadline. As we had told our customers in advance that we would have this feature in the market by the beginning of quarter 3, we had to cut back on certain requirements to ensure we met our deadline.
I collaborated with key stakeholders to make sure we were aligned on what we needed to cut back on to reduce scope. Compromises we made included:
Pausing on adding other communication methods for church givers to know they’ve received their tax statement - We decided to launch first with our most common method of emailing
Cutting out timeline and auto fill improvements for the launch and adding these in as fast follows after the launch
Delivering mobile UI layout updates gradually as most of our users would do this task on desktop according to internal analytics
Outcome
The feature was successfully launched live and on time to Pushpay’s customers.
Over 150,000 tax statements have been successfully generated with multiple Pushpay users providing positive feedback how the re-design helped save time using multiple tools and improved their outreach to church givers.