▸ Overview

Context

Key Insights

Localization

Solution

Principles

Constraints

Tracking Potable Water Collection Rates

Tracking

Potable Water Collection Rates

Client

The WASH Foundation

Timeline

4 months

Skills

Content Design

Interaction Design

User Research

Localization

Product Thinking

Prototyping

Content Design, Interaction Design, User Research, Prototyping, Localization

Role

Content Designer

Product Designer

Content Designer, Product Designer

Tools

Figma

Team

1 Designer

5 Developers

1 Product Manager

1 Tech Lead

1 Designer, 5 Developers, 1 Product Manager,

1 Tech Lead

Brief

Design a mobile app for users to record data on water collection rates.

English Prototype

English Prototype

Spanish Prototype

Spanish Prototype

Context

Outside the metropolis of Lima, Peru, ~700,000 households are off the primary water grid, without consistent access to clean water.

A new technology allows fog nets to collect fog water and convert it to potable water.

In order to garner more funding for these fog nets, the WASH Foundation needs more data on their conversion rates. 

I created a 0-1 mobile solution for locals on the ground to record and verify data from these fog nets daily.

Key Insights

Research through 5+ expert interviews taught us:

1

The data collection sites are physically out of the users' way.

2

Data accuracy is self-managed.

3

There are clusters of different fog nets which collect water at varying rates.

4

Users like to see their contributions make an impact.

Constraints

Users need to be motivated to walk a distance to the fog nets.

Users need to be motivated to walk a distance to the fog nets.

Data needs to ensure accuracy.

Data needs to ensure accuracy.

Data needs to be specific per fog net.

Data needs to be specific per fog net.

Data needs to be recorded daily.

Data needs to be recorded daily.

Solution

We initially thought users wanted to know more about how effective the fog nets were at scale so we designed data visualizations of water collection across fog net clusters.

Research, however, showed users were most interested in ease of use. These designs are as straightforward as possible to reduce time for use.

Feature #1

Welcome page

Welcome page

Submission page

Submission page

Focus on the primary task.

Focus on the primary task.

Simplify to solely the CTA.

Simplify to solely the CTA.

Use "today" and "yet" to encourage daily submission.

Use "today" and "yet" to encourage daily submission.

Invite user with "Hi, [user's name]" in a friendly tone.

Invite user with "Hi, [user's name]" in a friendly tone.

Feature #2

Confirmation page

Confirmation page

Double-check the work before submitting.

Double-check the work before submitting.

Require users to double-check their inputted data with an additional confirmation page for accuracy.

Require users to double-check their inputted data with an additional confirmation page for accuracy.

Maintain a clear UI distinction between confirming "yes" or "no."

Maintain a clear UI distinction between confirming "yes" or "no."

Feature #3

Submission feedback

Submission feedback

Celebrate their contributions.

Celebrate their contributions.

Offer feedback that leaves an impression.

Offer feedback that leaves an impression.

Give a user-specific lifetime metric for a clear sense of individual impact and reward.

Give a user-specific lifetime metric for a clear sense of individual impact and reward.

Localization

While I designed an English prototype for our clients in the WASH Foundation, I also designed a Spanish prototype for the Peruvian user base.

Adaptation #1

Language Toggle

Language Toggle

Users can choose a Spanish or English setting on the login and homepages.

Users can choose a Spanish or English setting on the login and homepages.

Small flag icons serve as visual indicators next to the standard abbreviations.

Small flag icons serve as visual indicators next to the standard abbreviations.

Adaptation #2

Title Case

Title Case

In Spanish, only the first word in titles are capitalized. The following words in titles, subtitles, and buttons are all lower case.

In Spanish, only the first word in titles are capitalized. The following words in titles, subtitles, and buttons are all lower case.

User profile details in English

User profile details in English

User profile details in English

User profile details in Spanish

User profile details in Spanish

User profile details in Spanish

Adaptation #3

Date Information Fields

Date Information Fields

Date
Information Fields

The order of the information fields changes based on different date notations.

The order of the information fields changes based on different date notations.

English Date Notation is mm/dd/yyyy

English Date Notation is mm/dd/yyyy

English Date Notation is mm/dd/yyyy

Spanish Date Notation is dd/mm/yyyy

Spanish Date Notation:

dd/mm/yyyy

Spanish Date Notation is dd/mm/yyyy

Adaptation #4

"Number" denoted by "#"

"Number" denoted by "#"

"Number" denoted by "#"

"Number" denoted by "nº"

"Number" denoted by "nº"

"Number" denoted by "nº"

"Number" Notation

Principles

Less is more. Simple and straightforward makes it easy to create a daily habit.

Less is more. Simple and straightforward makes it easy to create a daily habit.

Keep feedback loops positive.

Keep feedback loops positive.

Adaptability for localization is key.

Adaptability for localization is key.

Previous Project

Next Project

If you'd like to chat about my work, please email or message me. I'm always happy to connect!

Thank you for reading.

I'm always happy to chat about design,

short stories, or translation theory.

Let's get coffee!

I'm always happy to chat about design, short stories, or translation theory.

Let's get coffee!