<aside> 👋
This, and all of the blogs, give an overview of the process and steps taken for each part. I’ve included images taken from the Figma File where the majority of the work lives to illustrate the process.
If you would still like to see further details on each part, please view the Figma File in full.
It can be found at the end of this page, or on this master page.
</aside>
While continuing to develop my wireframes, I wanted to implement the feedback I had received from my first round of user testings. At this point, I had archived the wireframes I tested with as “V1”, and this set of changes would now become “V2”.
A fairly minor change that was found through my testing was to make the habits sections in the onboarding optional. There were a few reasons for this:
This was an easy fix, just requiring a content tweak and extra button to skip that part of the onboarding.
There was a feeling that the way I had intended users to add a payment method was too hidden, and that having the “wallet” section on the home screen would be confused as related to payments rather than passes and tickets. Equally, users may not trust adding a payment method in onboarding as they don’t fully trust the product yet.
To fix this, I added a modal that appears when the user first reaches the home screen to prompt them to add a payment method. This made it feel more optional, while still being clear and direct.
A slighting more nuanced problem was when users were buying tickets for others. As the questions in the flow used personal pronouns, it became unclear who the pronouns were addressing. To fix this, I used a technique I had used on placement of adding an initial screen to ask the use who they were buying tickets for with each possible combination of options.
Although this added an extra step, triaging users in this way helps provide clarity over who the system is talking about.
