Our initial approach, we tried to understand the scope of our design space - meetings in modern companies. We explored this problem space through a variety of research methods– competitive assessments, surveys, secondary research, semi-structured expert and user interviews.
Research and Insights
Given the timeline of the challenge, research needed to be conducted in a quick, efficient way. We employed primary and secondary research methods to understand what e-ink is, and the feasibility, viability and desirability associated with it. Beyond an understanding of e-ink, we also looked to understand the role of dockless bike share systems in large cities and any problems that people may encounter.
News Research Reference
Riders regularly and willingly engage in unsafe navigation practices.
Unfamiliarity with bicycle-friendly roads leads people to choose alternative methods of transportation
With the insights in mind, we generated a total of over 15 design concepts. The 15+ concepts were then narrowed down to four loosely related concepts- an on board navigation system with GPS map display, a built in universal phone mount for the bike, and two versions of an on board navigation system with visual and auditory navigation cues.
Down Selection Criteria and Rationale
Through interviews and evaluation of our four concepts, we reached three insights to drive our final design direction.
GPS map is too distracting and compromises safety.
Phone case is inconvenient for the riders.
Headphones are unsafe and unsanitary
We decided to move forward with the on board navigation system that uses an e-ink display for visual navigation cues and auditory navigation cues in the form of a built-in speaker.
What we wanted to understand
To test the concept, we developed digital and paper prototypes using Adobe Illustrator, InVision, cardboard, tape, and glue.
- How might people interact with screens while riding?
- How might people perceive and respond to visual navigational cues?
- How might people react to a new sharing bike with a navigation system built into the app?
After testing our initial paper prototype, we learned a few key findings that influenced our final design.
People found progress bar misleading: is it displaying progress to the next turn/move or overall progress to the destination?
Initial ETA metrics (distance to destination, time to destination, and time of arrival) were overwhelming and unclear.
It is too loud to hear auditory navigational cues in a city environment.
Final User Interface