Published on | Prototyping: From UX to Front End — Medium Max Cameron-Taylor

UX Design Case Study

Overview

This project was a quick, 4 day sprint with the aim of discovering a specific problem in the daily life of a single user, and then designing a conceptual digital product to solve that problem, for that user.

My user was Karolina: a young graphic designer who had just moved to London from Warsaw.

User Research

The first stage of the process was to conduct a series of increasingly focused interviews in order to first understand our user and common problems that they experience in their life, and then gain actionable insight on a specific topic.

This required asking broad questions to ‘cast the net wide’ and encourage our user to open up about frustrations they experience in their daily routine.

From this process I was able to learn that Karolina enjoys keeping plants but has some difficulty looking after them properly.

I used specific questions to then lead a discussion with the aim to fully understand my user’s approach to this topic and to extract actionable information to assist me in designing the most appropriate solution in order to address their needs.
The WWWWWH (Where, Why, When, What, Who, How) framework assisted me in constructing questions that would gain the most valuable insight from my user.

In order to have a visual overview of my user research I charted my findings on a concept map documenting the key themes from our discussion of why she keeps plants, how she goes about it and what frustrates her about it.

Concept map

This process helped me to clarify exactly what the problem I was designing for was, as well as what I hoped to achieve:

Initial Designs

My first sketches explored the ideas I had about how to gather the required information about my user’s plant collection and then display each individual plant’s current status.

The first iteration was based around an overview page of photographic icons depicting each plant, with the time until the next required watering overlaid on top.
From here users would be able to tap on an individual plant to see detailed information on watering schedule, nutrient or fertiliser requirements, sunlight requirements, re-potting preferences and other information specific to that plant type.

This quickly became, cumbersome, confusing, and complicated.

It included the information that the user wanted to know — but was it really achieving the user’s goal?

Focusing on the essentials

By taking a step back to revisit my user research and synthesise the data I was able to focus on the user’s core need of being able to simply track when she needs to water her plants.

I went through a process of drawing out several iterations of user flows in order to analyse how the user would move through the app, and stripped the process down to a simple, happy path to improve usability and achieve the user’s goal.

Stripping the user flow back to a simple, happy path

From this I settled on two main requirements for a minimum viable project:

1. Allow the user to add plants to the app

2. Notify the user when they need watering.

The user flows gave me a structure from which to construct the necessary individual screens for the app and ensure that the process had a clear continuity. I took these wireframe sketches and turned them into paper prototypes to gather some initial feedback from the user on the usability of the app.

Sketch wireflows

I adapted my sketches to provide a more visual experience within the app, with the aim of making the information more immediately accessible to the user and the product more enjoyable to use.

I experimented with the use of colour to communicate at a glance how long until a plant needs watering, and if a plant is overdue a drink.

Adding visual interest to the sketches

Testing & Iterating

Creating paper prototypes

Through the testing process I learned three main points:

1. the user became confused about what the app wanted from them

2. the user wondered why they were needing to enter certain information

3. the user didn’t fully understand how to progress through the app.

The current design was causing them to have make several assumptions about what they should be doing and as a result the user experience was negatively impacted.

Clickable prototype testing with Karolina

In response to this feedback I introduced an instructional interface that would enhance clarity and keep the user on track to their goal, while ensuring that they know what to do at each screen.

Further user testing with a clickable prototype positively reinforced my assumptions, with the user responding immediately to the on-screen prompts and being able to interact with the product without reaching any pain points or resorting to trial and error.

Final Prototype

The screen flow below shows the final prototype design for this sprint:

Next Steps

Given more time on this project, I would like to reintroduce some of the more advanced features showing information that the user suggested they would find useful:

Drainage/ watering technique requirements
-Repotting schedule
-Ideal sunlight exposure

Other features I would like to include are:

Help the user become more aware of the calendar feature through prompting.
Allow for more than one plant to be added at once.
Make the process of watering the plant and resetting the timer more clear.

Visual Design

Click here or on the image below to also read about how I approached the visual design of the app interface!

Thanks for reading!

If you’d like to get in touch or find out more about me, please use one of the links below:

Email // LinkedIn // Portfolio

<a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a>

pluvia: Making plant care easier was originally published in Prototypr on Medium, where people are continuing the conversation by highlighting and responding to this story.

pluvia: Making plant care easier

Cool stuff, every week

More Articles