Introducing the faster, smarter and more environmentally friendly way to get around town.
In just two taps, you can conveniently locate a Gobee.bike near you and ride to a destination of your choosing – completely unshackled.
The aim was to design an easy to use mobile app to rent shared bikes for urban cities. Locals and tourists can pick-up and drop their rented bicycles all around the city (except for some no-go zones). Their usage will be counted in minutes.
When I first joined GobeeBike, the company wasn't Agile. They were facing many problems at the time, and they had no framework or a process to come-up with solutions in a fast and efficient way.
The main constraint for me was how to put together a way of working that is flexible enough to solve GobeeBike's most urgent problem. That's when I started learning about Lean UX and Design Sprints.
It was very obvious to me that we can't use massive swaths of time to do massive research studies before work begins or design a pixel-perfect interactive prototype before developers start coding. Instead, we will focus on:
• Cross-functional teams
• Removing waste
• Continuous discovery
• Shared understanding
• Permission to fail
• Fewer deliverables
.png)
.png)
We started by a one day workshop with different stakeholders where we debated features and functionality, at the end of the day we came up with some solutions to our questions: Should the the No Parking Zone & City Limit be like a restricted area on the map? How interactive should the map be? Should we use the geo-localisation feature?
After testing few prototypes we went with a simple visualisation of two solutions. No-Go zones are represented with a dashed border on the map and the user still receives a text telling him that is not allowed to park or to ride the bike in this area.
Maintenance fees are one of the highest cost for the company. Our users are very involved in this process by reporting damaged parts or bikes. We had to make the process easier and more accurate for higher efficiency and cost saving.
After testing few solutions, the grid with an illustration of each part of the bike was the winner. Users found it easier to quickly see the part's icon and select it instead of going through a whole list of part's name that wasn't really known by most of the users.
If you want to learn more, see more screens or even experience a prototype for this project, please get in touch!
Get in touch
