Summary
iOS app + Web tool
Jyve is a mobile platform for users to find, reserve, and execute jobs at nearby CPG retailers. As the startup's first designer, I worked closely with the founders to translate their initial concept into a fully functioning pilot iOS app and WEB admin portal in 12 weeks. The product is currently live and is used daily to perform thousands of jobs per week.
Process
Problem
Identify and prioritize all necessary features for product v1.0.
Solution
I led the Jyve team through a brainstorming exercise to identify all the possible features and actions a user needs to find, reserve, and execute a job. I then built a collaborative GoogleSheet for our team to identify and rank the product's required and optional features. Team members were able to:
Problem
Translate our list of features into a network of logical, dead-end free, user-flows.
Solution
I used LucidChart, a collaborative visual task-flow diagramming software, to map and sequence each feature in relation to one another. Translating each feature into a visual object that comes before, after, or simultaneously relative to another enabled our team to understand a hypothetical user's flow of possible actions. We worked through multiple iterations on these diagrams with the goal of reducing the overall number of choices and clicks, trimming away redundant connections, and locating dead-ends.
Problem
Design a visual interface that enables a user to access and perform the product's features.
Solution
Working from the LucidChart diagram, I marked each point in the flow that required a unique screen. I began with a rapid round of low-fidelity wireframes to define basic layout, interface, and information architecture concepts. These wireframes are crude, but aim to successfully communicate the product's big ideas to our team and investors.
Problem
Solution
I worked with my client to identify areas for improvement. While I can admit that I am an OCD aesthetic detailer, I recognize that my priority when working as a product designer is to make sure the product actually does everything it needs to do. I value elegant user experience over elegant style - always. So we took a few steps back to analyze whether or not the designs truly convey all the necessary information for a Jyver to easily find a job, reserve it, and execute it. Here are some of the big issues that needed to be addressed:
I went back to the drawing board after processing this feedback and took another stab at the design. We agreed to strip away unnecessary styling and push that off to a later release, focus on the fundamentals, and get a design that optimizes the Jyver's ability to do their job with minimal obstacles.
We launched this version of the app ahead of schedule and conducted a week of 'in the wild' user-testing with users who have never engaged with the product before. Our team expected these first-gen users to encounter pain-points such as encountering dead-ends, getting lost in the app, or being unable to complete an action, but we were pleasantly surprised to hear that users were able to find, reserve, and execute jobs as the prototype intended.
The design foundations of the v1.0 pilot largely proved to be successful - my next steps were to work with engineering to trouble-shoot bugs, further optimize flow by reducing # of actions, and now spend some time to develop a consistent, template-driven aesthetic look and feel. Here are some of the key issues we encountered and needed to address:
OK! And finally here's the v2.0 design of the Jyve iOS application.
This is a clickable InVision prototype. Click around to explore the app. It's a demo with limited functionality - but you can Find, Reserve, and Execute mock jobs. Cheers.