Ironhack’s Prework: Sonia Leon_Challenge1
Citymapper is a technology company founded in London focused on improving urban mobility through a digital transit and mapping application. The platform helps users navigate cities by offering optimized routes that combine different transportation options, such as metro, bus, train, bike, and shared mobility services, within a single app. By integrating public transport data and real-time navigation, Citymapper aims to make moving through complex urban environments easier, faster, and more efficient for both residents and visitors.
Main Problems Identified in User Interviews (Empathize).
Confusion about which tickets to buy:
- When are zones or municipalities instead of stops.
- They travel outside their usual route or city.
- They transfer between lines or operators.
Complex ticketing systems
- Too much information
- The logic zones, fares, or operators are not always intuitive.
Need for multiple tickets for one journey
- They cannot purchase the entire machine or on a single website.
- They are confused about where to buy what.
Difficulty understanding systems in new cities.
- Language barriers
- Unfamiliar systems
- Complex fare structures
Emotions:
- Frustration
- Insecure
- Anxious
Users don’t want to choose tickets; they want to enter origin and destination and automatically receive the correct ticket for the whole journey.
Get Leon Isern Sonia’s stories in your inbox
Join Medium for free to get updates from this writer.
2. Problem (Define)
Users need a simple and centralized way to buy the tickets required for their journey, because there are currently barriers (different operators, systems, or languages) that make the process confusing, slow, and prone to errors.
3. How to solve (Ideate)
Creating a feature for UrbanGo app to solve the pain of having to purchase different public transport tickets by different channels.
4. Prototype
Key Things that I learned in the process
1. The formulation of questions is an aspect that can influence the overall outcome of the research.
2. During the empathy phase, I discovered user needs that were different from those I was aware of.
3. Prototyping requires not only defining what you want to do on each screen, but also how to express it through visual elements, how to archetype the information, and what flows to follow.
