Mobile Payment App
A majority of consumers see mobile apps as a convenient and secure way to make purchases, send money and other transactions such as recurring, in-store and person-to-person payments.
A number of apps explore these services in conjunction with perks like rewards programs, fraud protection, boarding passes and NFC (contactless) transactions.
In this tree testing example, discover how to:
The Information Architecture process for this case study started with an inventory of features offered by 3 competitor apps (Mastercard's Cash Passport, Pyypl, and Cards )
We then discussed feature groupings during a card sorting workshop in Miro.
The resulting tree was formatted using a 2-space indentation and uploaded to UXbeam for testing.
The initial rounds of testing revealed an INDIRECT outcome for 4 out of the 6 tasks.
We thus needed to iterate on the tree and instructions -which took 8 rounds to optimize.
Click to view the progress between iterations (rounds of testing) 👇
✅. Discovered unexpected feature groupings ✅ Refined labels ✅ Clarified the task scenario
Once 80% of tasks are Direct, the prototype can be shared with a few participants in a moderated setup, with the same tasks but this time asking for qualitative feedback (what liked/disliked, what is missing, when would you see yourself using this the most, etc.).
In parallel, parsing the tree into meaningful screens and navigation by making sure the labeling conventions are respected and alternative navigations can be concept tested