In a two-week sprint, I worked in a team of four to integrate a new feature for the existing Lime bike mobile application creating a hi-fi clickable prototype. The new feature is added to help customers creating a multi-point sightseeing tour, browse sight details for major attractions, secure rental bikes nearby and a more personalised app experience as a way to retain current customers and attract potential users.
UX Researcher/UI Designer (Group Project)
User Research | Competitive Analysis | Sketching | Sitemaps | User Flows | User Testing| Wireframing | Prototyping
Sketch | inVision | Photoshop | Pen and Paper
Lime Bikes is an electric bike service that users find and unlock on the mobile app that knows the location of available vehicles via GPS. In November 2018 Lime moved to London and now has a fleet of over 1,000 electric bikes. Lime is founded on a simple idea that all communities deserve access to smart and affordable mobility.
You locate the nearest Lime bike through their smartphone app, scan a QR code on the rear mudguard, and the bike should unlock for you. Test the brakes, and you’re ready to ride. The rental costs an initial £1 to unlock the bike, plus 15p for each minute it’s in your possession. The system allows users to use mobile app to unlock dockless vehicles and park them on the streets when trips are completed – but they must avoid the red zones or they will need to pay a £10 fine.
Our client shared four main points they would like us to take in consideration:
To understand the transport market a bit further, we conducted a competitive analysis of direct and indirect competitors of Lime. We also compared some important features from traveling apps as we would like to optimise the experience of users when it comes to planning holidays and bike tours.
To understand the experience of hiring a Lime bike, we conducted a site visit and made some interviews to localise the pain points for users.
We sent out a short survey online asking people about their travel and commute behaviours in London and if they were used to hiring bikes for themselves. Through this method, we were able to filter and recruit research participants to conduct more in-depth interviews further on.
35 people responded in total but only 9 matched our criteria to move forward with personal user interviews. We tried to recruit two groups of interviewees; we wanted to talk to frequent and non-frequent cyclists to understand why and how they started cycling so that we could address their issues in our product.
During the interviews, we asked individuals about their travel and commute behaviours in more depth. We wanted to understand how they travelled and the reason behind their behaviour. Further to this, they were also specifically asked about their attitude and feelings towards cycling in London or when on holidays.
An Affinity Map was generated with a large amount of data and quotes from the user interviews and online reviews, a few common trends and pain points were identified. After the problem statement was formed, we were able to focus on finding solutions and opportunity areas that guided our project.
From those insights, we realised we would need to focus on some problems we could solve on the app. Many of the user’s feedback were about the quality and physical conditions of the bikes or how they were feeling unsafe knowing they would need to cycle without a helmet – considering it’s something you don’t necessarily have when hiring a bike ocasionally. They were also very vocal about issues they’ve had when it comes to pick-up and drop-off (e.g. mentioning the red zones – places they are not allowed to park and can be charged a fee if they do).
To understand a bit more about our user’s pain points when hiring a bike through a mobile app, we created an Experience Map.
It was clear that stopping to check directions was the main opportunity for us to stand out as a product. When cycling, users need to stop every once in a while to check the suggested route and see if they are following the right path. That’s not only dangerous but it also takes time to juggle between apps. If you look back to check the other competitors, they were not offering any alternatives when it comes to solving this problem either.
The insights synthesised from the user interview data has shaped our persona for Lime bike, Alex.
An integral part of the design thinking process is the definition of a meaningful and actionable problem statement, which the design thinker will focus on solving.
After defining our persona and understanding his problem, we created the happy path: the default user journey that a customer would experience if they proceeded to convert without any deviation during the process.
We also created the app map indicating where they would be placed – according to user’s feedback.
(The area highlighted in black (left) indicates the new feature we designed for the app – and where it would sit according to the current app map.)
With the problem statement and our persona in mind, our team brainstormed for various potential solutions. Due to the balance of time and resources, create route, reserve bikes and add multiple stops were the priorities of the new feature integration. We started sketching and creating wireframes for our low-fi prototype.
Key point: We knew how important it was to test the low-fi prototype straight away as we wanted to collect some feedback from users and see if we were moving on the right direction.
With the problem statement and our persona in mind, our team brainstormed for various potential solutions. Due to the balance of time and resources, we decided to do a feature prioritisation matrix, that has an impact axis and an effort axis. We plotted all of the ideas that were produce from the second design studio.
As a group, we placed the features on this matrix, and decided to use the features that were high impact for the MVP. These are shown in the top two quadrants (in green). These included:
How-Might-We questions are a way to frame your ideation, and often used for launching brainstorms. This worksheet gives some strategies to use your current perspective on the challenge to create different How-Might-We questions that may prompt an array of fruitful ideas. The goal is to create questions that provoke meaningful and relevant ideas; do so by keeping the questions insightful and nuanced.
Suggests that a solution is possible and because they offer you the chance to answer them in a variety of ways. A properly framed How Might We doesn't suggest a particular solution, but gives you the perfect frame for innovative thinking.
… help people navigate a new city in an efficient way?
… help people create a bike group activity whilst travelling?
Lo-fi clickable prototype was tested. The scenario given to users was the following:
They had to complete 3 main tasks:
With all the instructions given to users, a few common problems were pointed out and addressed in the second iteration – and refined further on the final iteration. The main problems were:
To better understand all feedback we received from V1, we’ve done an Affinity Map with the main issues and used post-its to find patterns on the possible changes we would need to do. That was very helpful when you have a lot of feedback and you want to put them together to have a visual and better understanding of your next steps.
In order to apply the new features following the current branding of our client, we created a design guide with the visual elements of Lime. The look and feel of the app follows the original designs and we added some illustrations and a few other additional icons to help users navigate in the app.
To continue to grow Lime, a few new features are considered to be added. They focus on improving customer service and giving users a more personal experience.
I truly enjoyed the project and appreciate my supportive teammates who were very committed to the excellence we wanted to achieve. We were able to brainstorm and express our creative ideas and I felt we were all deeply involved in the project. In the end, we combined all of our great ideas to the final solutions based only in the research we’ve intensively done. Timeline and file-management were also very important to the project due to the short project time frame. The cross-functional team helped each of the members strictly follow the deadline and deliver what we had on the original brief – with clear steps of what to do in the next phase of the project.