Plantcare Assistant

Product Marketing

Design Problem

I worked on an interaction design project where I researched a domain of interest and designed a novel solution to address a problem. From my research, I decided to design a mobile application and soil moisture sensor that helps people take care of their plants.

Project Overview

Plantcare Assistant Hero Image

High-Fidelity Screens

Approach

For this project, I followed the double-diamond design framework by beginning with research and deciding upon an area of interest for my design problem.

Double Diamond Diagram

Double Diamond Framework

First, I conducted a cultural probe and sent out a survey in order to gain information on the plantcare domain and the people who participate in it. From there, I created personas, an empathy map, and a journey map. To explore possible solutions, I then conducted user enactments. From there, I was able to narrow in on a core set of features which I documented via storyboards and userflows. Finally, I built wireframes and designed a style guide and ultimately a high fidelity prototype.

Cultural Probe

I conducted a cultural probe in order to learn what motivates people to care for plants and how they feel about plant care. The study was done virtually to ensure safety during the COVID-19 pandemic. In order to mitigate any impact on the data, I created graphical representations of the probe materials to help users get a better feel for what was being asked of them.

The research questions I sought to answer with the cultural probe were:


Plantcare Assistant Cultural Probe Workbook

The Plant Care Workbook helped me gain insights on:


Plantcare Assistant Cultural Probe Feelings Booklets

The Plant Care Feelings Workbook helped me gain insights on:


Plantcare Assistant Cultural Probe Day Log

The Plant Care Day Log served as a mini diary study, and helped me gain insights on:

From the cultural probe, I generated four high-level research findings:

Key Findings:

🔍 ..Plant owners often find it difficult to identify plant health.
🔍 ..Plant owners are often too busy to take care of their plants.
🔍 ..Plant owners have limited access to plant care communities.
🔍 ..People help each other with plant care work outside of core plant care activities (i.e. watering), by motivating, encouraging, reminding, and holding each other accountable to care for their plants.

Survey

I then conducted a survey in order to validate the findings I gathered from the cultural probe, as well as to further dig into plantcare motivations, emotions, and shared responsibilities. I was able to recruit 35 participants and asked them to fill out a 10 question survey on Qualtrics.

Key Findings:

🔍 ..A majority of respondents (76.92%) require support from others with caring for their plants including core plantcare activities and troubleshooting plant issues.
🔍 ..Plant owners find it difficult to identify plant health. (20.45%)
🔍 ..Plant owners would benefit from daily to weekly plant care reminders.

Plantcare Assistant Survey Findings Plantcare Assistant Survey Findings

From the research findings, I generated personas, an empathy map, and a journey map.

Personas

Two personas were created from the research findings; both a primary and secondary persona were built, as this would help me make product decisions and prioritize feature sets down the road.

Personas

Personas

Empathy Map

An empathy map was created for the primary persona, which describes what the user says, does, feels, and thinks in relation to plantcare work.

Empathy Map

Empathy Map

Journey Map

I created a journey map which tracks the users’ mood throughout the plantcare lifecycle. This helped me identify pain points and resulting product opportunities.

Journey Map

Journey Map

User Enactments

I also decided to conduct user enactments in order to test out the different design options I had come up with. The questions I sought to answer with the user enactments were the following:

  1. What is the minimal viable function the product needs to achieve to help users take care of their plants?
  2. How much user control do participants prefer and what level of automation are they comfortable with?
  3. What potential error cases would come up and how should we go about designing for them?

I recruited three participants and created scripts and wireframe props for the user enactments in order to get quick insight on a handful of possible user scenarios.

Plantcare Assistant Wireframes

Wireframes

After conducting the user enactments, I added all of the notes to an affinity wall, clustered them into like-themes, and generated high-level insights that would go on to inform the end product.


Affinity Wall

Affinity Wall


Key Findings:

🔍 ..Users expect the plantcare assistant to give feedback and confirmation immediately after they water their plants.
🔍 ..Users expect to be able to toggle on & off and customize notifications based on needs and preferences.
🔍 ..Users expect the plantcare assistant to provide some practical and actionable recommendations and instructions regarding their specific plant and what moisture levels mean in regards to the plant itself.
🔍 ..Users would like if the plantcare assistant incorporated additional features (i.e. weather, calendars, and GPS) that would provide more detailed information & personalized plant care recommendations (but there are some concerns regarding privacy for GPS monitoring).

Ideation

From the user enactment findings, I did another round of brainstorming and sketched out possible design features and solutions.


Plantcare Assistant Brainstorm

Feature Brainstorm

I then documented core product attributes that address user needs, and evaluated my new ideas based on the following criteria:

Storyboard

Following the evaluation of the newly brainstormed ideas, I crafted a storyboard that helped me start documenting specifications for a minimum viable product.

Plantcare Assistant Storyboard

Storyboard

Userflow

I also created an abbreviated userflow to align on a minimum viable product. By focusing on a happy path for the user, I was able to document the primary flow that would constitute the user experience. Plantcare Assistant Userflow

Happy Path Userflow

Wireframes

After developing a storyboard and userflow, I crafted wireframes that cover the core product experience. The wireframes were made using Google Material Design 3.0 components in Figma. Utilizing Material Design elements allowed me to quickly create wireframes that meet development and accessibility best practices.

Plantcare Assistant Wireframes

Wireframes

Plantcare Assistant Wireframe Annotations Plantcare Assistant Wireframe Annotations Plantcare Assistant Wireframe Annotations Plantcare Assistant Wireframe Annotations Plantcare Assistant Wireframe Annotations Plantcare Assistant Wireframe Annotations Plantcare Assistant Wireframe Annotations

Style Guide

The color pallete was inspired by plant foilage and includes green and tan colors. I decided to utilize a card system with rounded corners to create a playful feeling. It was also important to use ample white space to ensure the app appears clean and organized.

Style Guide

Style Guide

Design Components

Design components were created in Figma using auto-layout and variants; I used them to build high-fidelity screens and a working prototype.

Design Components

Design Components

High-Fidelity Designs

The high level feature points for the final product include:

Plantcare Assistant Product Marketing

The high fidelity screens were designed to include a plantcare dashboard, task assignment modules, and individual plant details, as well as social features and customizable settings.



Product Screens 1 Product Screens 2 Product Screens 3

Plantcare Assistant Prototype



Reflection

During the user enactment sessions, users had expressed that they wanted additional details on plant moisture levels. For future iterations of Greener, I would look into providing more specific plant moisture measurements and instructions for users. Additionally, manual input of plant care details could be added to allow for more personalized plantcare recommendations, however, it would need to be a compelling user experience in order to entice users to do so. I would start by conducting usability tests with an updated high-fidelity prototype and use those insights to iterate and improve the user experience.


rss facebook twitter github gitlab youtube mail spotify lastfm instagram linkedin google google-plus pinterest medium vimeo stackoverflow reddit quora resume quora dribbble