Analysis and Prioritization

<aside> 💡 Affinity Map Link: Figma file

</aside>

Screen Shot 2023-04-25 at 1.40.46 PM.png

<aside> 💡

Definitions of success (i.e., your metrics)

</aside>

https://app.maze.co/report/Refunds-Feature/ac9ilgud1odk/intro/embed

Task 1: Track a refund from a previous transaction, Zara from April 17th & return to ‘Home’

6/9 users can accomplish tasks within 90 seconds	100%
6/9 users can complete the tasks without giving up	**80%
20% gave up when asked to “Return back to Home”**
6/9 users can accomplish the flows without error (i.e. clicking/tapping on anything outside of the prototyped flow)	85% misclick rate when asked to “Return back to Home”

Task 2: Check the status of the registered Zara refund

6/9 users can accomplish tasks within 90 seconds	90%
6/9 users can complete the tasks without giving up	90%
6/9 users can accomplish the flows without error (i.e. clicking/tapping on anything outside of the prototyped flow)	66.7%

<aside> 💡 • Recommendations for the next steps for expected results. Explain what worked well and should be moved into development, and why further testing on those specific aspects of the design is not needed for now.

</aside>

Task 1: Track a refund from a previous transaction, Zara from April 17th, then return back to Home

Rework the prototype to allow multiple entry and exit points. Many users wanted to exit via the icon on the top right or return home via the navigation bar
Perhaps delete the screen and have it smart animate back to Home?

Task 2: Check the status of the registered Zara refund

Show a preview of the Upcoming Refunds card on the Home page

What Worked Well?

Process of how to track an expected refund for the respective transaction
How to view the tracked refunds, although could be improved with a preview on Home