Ironhack’s Pre-work: Design Thinking Challenge 1

Brief Introduction

Hello! I’m Jorge Antonio Ramírez Padilla. I am an Artificial Intelligence Engineer (a fancy way my university calls Computer Science) working as a Front-End developer in Aguascalientes, Mexico. I have enrolled into Iron Hack’s Full Time UI/UX bootcamp taking place in Berlin, Germany from October to December. However, I need to complete a pre-work to get me ready to begin my formal classes. This is my first assignment. My first challenge.

Challenge 1: Design Thinking

For this first challenge, I need to create a solution for my client. This client is Citymapper. I need to empathize, define a problem statement, ideate a solution and build a prototype.

The problem

Although the current product of Citymapper already solves some of the main problems of the urban mobility, there is one pain point for many users: the different amount of public transport tickets the users have to purchase.

Step 1: Empathize

First, I need to understand my user. I will interview 5 people who have used public transport to get to know their main issues when purchasing a ticket to get to where they need to be.

Step 2: Define

So, now after I’ve done some research, I need to define a problem statement. I came to the conclusion that the main pain point for the customer is having to know a lot of information scattered through multiple places and not having it all in one place.

Step 3: Ideate

This is where the fun begins. Having done my research and now ready to begin ideating some solutions, it’s clear that having a universal solution is a great challenge, so I’ll try to come up with a solution that better suits all or most of cities necessities.

Step 4: Prototype

I decided to go with the approach of letting the user purchase tickets while setting up the app for the first time, or in the future while they use the app. We will have a Ticket Wallet, which will have the list of cities where they have tickets, the tickets for each city. They can see the ticket status, either if it’s currently valid, expired ones, access to the code to get physical tickets, etc. In the prototype sketches, the yellow highlights are the buttons clicked to continue to the next screen. The green highlights are important information for the user and the blue highlights are important information which leads to other pages not drawn in the prototype because they are not relevant to the current design.

  • A QR code that can be scanned by guards or at any ticket booth that can read the code.
  • Below the QR code, there is a alphanumerical code which can be introduced in a ticket booth so the user may get a physical ticket.
  • The expiration date of the ticket, as well as a countdown to remind the user how many days are left until the ticket expires. This will work also as a notification system to alert the user when the ticket is about to expire.
  • A ‘More info’ button which will show the same information as shown on screen 5).

Conclusion

This was a very interesting challenge. Knowing how public transport in general works so differently from city to city demands finding common ground to help anyone, local or tourist, to move through a city in a familiar way with not so very complicated steps.