capstone
Case Study
MODE: Rideshare
PROTOTYPING
Prototyping, Usability, Testing and Iterations
Initial Prototypes
While I used Invision and Sketch here and there, Figma anchored my workflow (I can’t say enough about the ease and functionality Figma provides for situations where I run into obstacles with other platforms). For a few reasons I stayed with two key scenarios: onboarding and creating a ride experience. Lower level tasks like “update registration information,” “add a profile picture” etc. are well-modeled throughout the UX world, and would waste valuable time with users during testing. In the extremely lean circumstances of a study like this one, I had few incentives to keep their attention: I needed to maximize the ratio of actionable insights to time.
Also, I wanted to see how tasks integrated at a systems level: implementing end-to-end testing paid off well. If I had simply tested for one scenario—“navigate to your library”—in the onboarding sequence, and then tested for another scenario—“select your mode”—in the experience creation sequence, I would have missed crucial insights about the wholistic user experience. Key points of confusion only came up in when users were able to ask me things like “Wait, when I was on the learning screen 10 minutes ago in the onboarding part, does that affect the ‘create my experience’ task now?”
Local issues are much easier to sort out when iterating on your own design, but systemic issues are often blind spots because you think you already know how it all fits together.
And
Outcomes & futures