E-scooter parking solution,
built for a startup incubated in Demium Startups, Spain
Ignacio Herraiz
Physical and digital product design.
From scratch product.
60 Hours of work.
Process
Research
Define
Ideate
Prototype
Test
Research
Quantitative research
I conducted a survey to validate our problem statement. I focused on general constrains and pain point while using e-scooters. (63 Participants)
Qualitative research
I ran 5 user interviews with scooters users, my main purpose was to identify closely the type of usage e-scooters are having and which problems come along with it.
Discoveries
1. Riders feel unsafe doing long trips with their scooters because of the danger of riding alongside cars
2. Riders feel their scooters could easily be stolen
3. Riders don't usually use their scooters on social occasions because of the lack of spaces to leave the scooters
4. Riders usually have to carry safety items such as helmet or reflective waistcoat
5. Riders would love to use their scooters on every occasion if they could
Contextual research
I asked the users to perform some actions in order to study the manoeuvrability of the scooters. To find limits and comfortable solutions for users I needed to see how they might act in manoeuvrability situations, I also needed to understand the timing of each action.
Discoveries
Users demonstrated that average scooters had a high-level of manoeuvrability
Users had no problems at the time of the manoeuvring with scooters, but it is true that extreme users with low strength might have them.
Affinity Mapping
I clustered all the ideas and user quotes into groups to get an insight on the data
I extracted all the ideas and codes from the interview transcription, to understand the data and discover patterns and the importance of the ideas.
User POV
I put myself into the users' shoes to understand their POVs. This exercise was useful to explore perspectives and think out of the "designer's box".
Redefinition of the Problem
After delving deep into the problem, I had a pretty good idea of the needs and user requirements. Most of my assumptions were wrong, which was a good indicator.
HMWs
How might we create safe places to charge and park e-scooters? A useful method to start the ideation journey, I especially enjoyed using it. It helped me ideate and order new features for the website that I had in mind.
User MAP
From the discovery of the service to the goal action, each step was crucial for my understanding. I also mixed the HMW questions with the user map, and applied this rule: Where more questions are in place more focus is needed.
User flow
I created the app and parking user flow
Once this was clear, it was easier to imagine how the user might interact with the app and how to approach the rest of the process.
Storyboarding
After having ideated the software part it was time to think how the user might interact with the locker.
I created a storyboard to imagine the physical flow of users when using a garage.
MVP Prioritization
I used the MVP method and classified the ideas, taking as reference the impact and effort they would have by a diagram. This process made me discard some ideas and highlight others.
App Sketching
I sketched the whole flow to test the design as soon as was possible in the process.
Garage Sketches
I sketched the E-garage itself with the features I had designed.
App Lo-fi
Based on the sketches, I created some wireframes and added some details to the locker sketches.
Garage Lo-fi
Testing technique
Introduction, Chitchatting
User usage of the prototype,
I asked them to "think aloud"
User Feedback
Discoveries
Discoveries:
The hierarchy wasn't clear. The texts contained in the UI didn't clarify where exactly the user was in the app
The colour hierarchy didn't focus user attention where it needed to be, causing confusion.
The scanner and location button had an icon that confused users.
The onboarding wasn't clear enough.
The chosen outlay didn't fit user needs.
The confirmation steps of the process confused users.
Any question?
Let's discuss the case study!