Increasing the sponsor retention rate through missed donations.

By Aqil Azrif
Timeline
1 Month (2024)
Tools Used
Figma, Notion, Askable, Optimal Workshop,

Project Summary

I designed and optimised the missed donations flow within The Smiths Family sponsor portal through harnessing qualitative interviews and quantitative testing methods.

Background Details

  • The Smith Family is a non-profit organisation that focuses on providing aid to underprivileged Australian students with their education. Over 100,000 Australian students are supported through donations and sponsorship.

I began with interviews and ticket analysis alongside the customer experience team to gain a broad understanding of the current problems and requirements facing missed payments. We identified that the main user pain point was frustration with needing to call customer support and as a result led to significant drop-offs in regular donations.

Conducting initial interviews & ticket analysis with the supporter experience team to gain a better insight into the needs and requirements for missed donations.

Project Goals

From the interview with the supporter experience team, we created a few key metrics to track as a measure of success for the project.

  • - Decrease in calls (and reduced cost-to-serve) for supporter experience team
  • - Decrease rejection rate as sponsors are able to update their bank details and prevent rejections occurring in the first place.

User Stories

To address these painpoints, I extrapolated the customer support tickets and interviews into user stories to reframe these insights into actionable items for the userflow and wireframe.

A snapshot of the user stories extrapolated from the previous interview with the supporter experience team.

Userflow & Wireframes

I then created a userflow outlining the key screens and actions required for the missed donations flow while connecting the actions to the user stories to ensure all pain points are met through the flow. I then proceeded to create quick wireframes to act as a reference point for the prototype.

The Missed donations userflow. User stories are numbered and connected to the respective action as seen by the yellow boxes
Quick mobile driven wireframes of the missed donations flow to be used as a reference point for high-fidelity screens.

High Fidelity Prototype

Drawing from our new Smith Family Design System, I proceeded to design and prototype the missed donations screen. With the intention of creating an unmoderated test with this prototype, I formatted the prototype into 3 set tasks. This allowed the test to be completed without requiring assistance through optimal workshop.

the prototype in figma before we mapped it to optimal workshop

Heatmap Testing

After double checking with the rest of the team that all the user needs were met, we then proceeded to test our designs using the optimal workshop heatmap feature to gain unbiased insights into how users interact with the prototype.

An example of one of our insights from our heatmap test. We noticed from a couple of our tests, users wanted to know in more detail which date their missed donations would be fully processed.
Operating off of the heatmap test, we added more context to how missed donations would be processed through using a table section.

Conclusion

The missed donation feature has recently gone live and early signs of sponsor retention are encouraging. We have seen a 76% reduction in the percentage of calls to customer experience surrounding the topic of missed donations.

(Full data insights will be updated here once the timeframe has allowed for more reliable sets of data)