5

5

Rapid Prototype

Project Overview

Remedy

Tailored for Juan - An App for one

Brief: Discover a problem in your neighbours' life that could be efficiently resolved with a mobile app.

Timeline: Three days

Process: Interview, Journey Mapping, Sketching, User Flows, Prototyping & User Testing.

App map / user flows


Close

The Root of the Problem - Interview

An interview was conducted to discover more about Juan's user problem. The interview identified why the problem occurred and where the opportunities for a solution existed within his routine.

Juan is very punctual and is used to a common routine. However he lives a busy life and frequently finds himself in a rush to get ready in the morning. At times he forgets to take his medications and vitamins.

Key Insights

Juan leaves home at the same time every morning but he forgets to take pills two to three times per week. He wakes and leaves the house when alerted by the alarm clock, finding an alarm a good way to ensure he always arrives on time. In the rush he often forgets to take his pills. Once he has forgotten to take his medicine it is extremely unlikely for him to remember to do so later on.

Analysis

User flows

User flows were constructed over two versions.

Version 1: The initial stage mind mapped the key features discovered during the user interview and plotting them into a diagram to visualise the relationship and task flow.

Version 2: Mind mapping was done first, followed by plotting an initial user flow and annotating the thumbnails, before sketching the required components. These annotated thumbnails were qualified with the user to ensure his needs were being met within the apps’ functionality and that the experience aligned closely with his needs.

Solving the problem: This helped identify the four stages within the apps flow.

  1. Setup
  2. Storing Details
  3. Manage Reminders
  4. Notification

Once finalised these were then detailed through the initial sketching stage and assembled into a first run prototype for user testing and feedback.

App map / user flows


Close

Concepting

Usability Testing

Prototyping

The initial prototype was constructed rapidly in POP an app prototyping tool. Upon completion, feedback was sought in a focused user testing session. This helped to highlight and identify any issues in usage and make specific needs-based improvements.

Testing Round 1 - User Feedback

“This is nice but it is too complicated for me. It needs to be simple and fast.”

- Juan Cordoba, Day 2, 4pm

Experience Preferences

Juan prefers simple, easy experiences with his mobile. He requires a solution that is easy to setup and manage.

If things are too complicated he won’t use them.

Usability Refinement

Testing Round 2 - Improving Experience

User testing stripped the stages back to three stages as one stage had a negative impact on Juan’s user experience.

  1. Storing Details
  2. Manage Reminders
  3. Notification

By minimising the screens in the app, simplifying and consolidating steps, Juan felt his needs had been accommodated. Juan hopes his app will go into production and be refined so that he may never forget to take his medication again. This will also assist him in taking his vitamins over the course of the day instead of all at once.

“This is much better, I would use this.” - Juan Cordoba, Day 3, 9am