<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 FigJam boards 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 FigJam board in full.
It can be found at the end of this page, or on this master page.
</aside>
Having completed version 1 of my wireframes, I wanted to test it with users to get some feedback to build into version 2. I first needed to plan what journeys to test.
When creating a prototype for user testing, I find it’s best to test individual flows, as it’s more focussed and easier to set up. After looking through my wireframes, I identified 5 flows to test.
<aside>
Testing account creation and setup, habits, and ordering of questions.
</aside>
<aside>
Testing where this should come in the flow, whether in onboarding or later.
</aside>
<aside>
Testing flow for in the moment travel.
</aside>
<aside>
Testing flow for planning a journey.
</aside>
<aside>
Testing ticket management flow.
</aside>
Next, I developed these into tasks that were phrased as to not overly direct users.
<aside>
Testing account creation and setup, habits, and ordering of questions.
“You’ve recently learnt about a new public transport app called “Metronet”. Now that you’ve downloaded it, you want to create an account to use the app.”
</aside>
<aside>
Testing where this should come in the flow, whether in onboarding or later.
“Now that you’ve created an account, you want to add a payment method to your account.”
</aside>
<aside>
Testing flow for in the moment travel.
“You want to go and meet a friend for coffee and want to use public transport to get there.”
</aside>
<aside>
Testing flow for planning a journey.
“You have an upcoming trip to Dublin and want to plan and book train tickets for the journey.”
</aside>
<aside>
Testing ticket management flow.
“You want to go back and check the details of your ticket.”
</aside>