<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>
As I come to the end of this sprint, I thought it would be nice to revisit my user journey maps and see how what I design would solve the issues I found during the mapping.
To start, I went through each opportunity I had identified in my journey maps, and found how I had design for each through Metronet.
I was pleased to see that I had managed to design solutions for almost all problems I had identified, despite the solutions not be the same as the opportunities I had considered. For example I had originally considered allowing the app to auto-buy tickets for users, but this wasn’t legally feasible, however the quick buy techniques I found covered the issue anyway.
As I worked through all the user journeys, I was really pleased to see how my work related back. I find I can often get to stage in the design part of a project where I don’t really touch base with my research again. Doing this at the end of the project let me find any final issues, and brought the project full circle. I’m really pleased I’ve done this as it’s helped me realised what I’ve accomplished in the last year.
The full design system for this project can be found in this Figma file.
https://www.figma.com/design/y0PROqO78LpF5wLlkzWBL7/Metronet-–-Design-Library?node-id=435-27574&t=QlO2XyHUYTSYMDiU-1
With this sprint pretty much wrapped up, I now wanted to think about the back end platform in sprint 2.