Swipe to delete - advocating for the user

image

The challenge

Convincing stakeholders that enhancing swipe to delete experience was worth adding to scope of project.

💡
Prior to this project there was no indication to users as to whether they were deleting a single transfer or all of the transfers in a series. Yikes!

Another challenge was writing content that could work across any type of transfer/payment so we could have a single unified experience.

The process

We were adding to existing features for moving money in an app, allowing users to have more options for recurring and post-dated transactions.

I noted that there was no indication to users as to whether they were deleting a single transfer or all of the transfers in a series (there were technical limitations that prevented us being able to allow users to delete a single transaction within a series).

I took initiative, reached out to the Product Manager and explained why we should consider adding this enhancement to our project scope. After discussing with the wider team all agreed it was an important enhancement.

The result

I wrote two versions of the alert pop-up content. I kept the content short and informative, as per mobile best practices, and kept the straightforward tone in company design guidelines.

Users can now tell what exactly they are deleting, and are less likely to accidentally delete a series of transactions which could mistakenly end up with them missing payments.

This became a bigger win for the users, as we used the same logic in other delete and edit flows. The pop-up alert has variable and specific content throughout the app now when a user wants to delete or edit an upcoming transaction.

image