Navigation Menu
Project screen 1 Project screen 2

Sugar

Product Designer

Duration: 8 weeks
Sugar is giving consumers the option of anything-sharing. Like ride-sharing, but for anything.
Prototype
Prototype

My Role

Discovery
Information Architecture
Brand Development
Visual Design
Prototyping
Testing

Deliverables

Logo Design
Style Guide
High Fidelity Mockups
Prototype

Tools

Figma
Usability Hub
InVision
Google Forms

Problem

Most of our homes are full of things we rarely use. We spend money on these things, then have to store them, and eventually they all end up in landfill. Why would you spend hundreds of dollars on a camera that you will use once a year when your nextdoor neighbor has one sitting in their desk drawer? Or a ladder? A suitcase? A projector?...

Solution

The solution is a platform where you can borrow what you need from people in your area. 93% of people said they would be open to lending their things and 83% said they would be open to borrowing. So I designed a website to facilitate that interaction.

Sketched Wireframe Digital Wireframe
High Fidelity Mockup Final Mockup

Research & Discovery

Competitive Analysis

This isn’t a new concept. Many sites have come and gone trying to address this very problem. Everyone loves the idea, but no one has been particularly successful. Three major players in the market today are Fat Llama, PeerRenters, and ZiLok.

Fat Llama Logo

Fat Llama

Fat Llama has strong visual design, insurance for renters, and an intuitive site. However, the platform is expensive, taking a 15% cut from both parties on every transaction.

PeerRenters Logo

PeerRenters

PeerRenters is only available as an iOS app, so they are missing out on a huge portion of potential users.

ZiLok Logo

ZiLok

ZiLok has been around a while, which is obvious from their website, which has a dated, cluttered, and unresponsive interface.

Competitive Analysis

Survey

There is definitely room in the market for a product that can really solve user needs. In order to understand what those user needs are, I conducted a survey.

93%

open to lending

83%

open to borrowing

100%

concerned about damaged items

71%

more comfortable dealing with acquaintances

66%

expect to pay or be paid less when dealing with acquaintances

45%

don't know if lenders should be paid

Survey Results

User Needs

Peace of mind
Control over who they interact with
Guildance for pricing
Control over pricing

User Personas

From the survey results, I learned that there are three types of user. I created a persona for each type.

Jessica Hart portrait

Jessica Hart

Lender & Borrower

Wants to recoup investment costs
Wants to pack less when travelling with kids
Worried about interacting with strangers

Samantha Elliott portrait

Samantha Elliott

Borrower

Wants to keep apartment free from clutter
Wants access to items at low cost
Worried about sanitation issues

Britt portrait

Britt Perkins

Reluctant

Wants to help her community
Wants access to infrequently used items
Worried about her things being damaged

User Personas

Information Architecture

User Stories

From the survey and personas, I wrote the user stories and prioritized them.
The stories include basic app functions like create account, add listing, etc. But the stories that directly address the main user needs are:

High Priority:

Peace of mind - As a user, I want a signed contract so I know what to do if something goes wrong.
Control over who they interact with - As a lender, I want to accept or decline a request to borrow an item.

Medium Priority:

Guidance for how much to charge - As a lender, I want to know how much to charge for an item.

Low Priority:

Control over how much to charge - As a lender, I want to set the price for my item.

Although the survey suggested that users might be interested in having social features in the site so they can share with people they know, I chose not to include that in the initial MVP. I wanted to create the leanest site that would get the job done well, but not perfectly. The leanest way to solve this was to give the control to the user, so lenders can choose to accept or deny any request for any reason.

User Stories

User Flows

From the user stories, I built out the user flows for my solution. This created a framework for the screen that I would need to design.

User Flow
User Flows

Wireframes

I chose to brainstorm with physical sketches to make sure I was considering lots of different ideas and none of them were too sticky. I sketched at least 4 options for each screen and then selected the best, which was sometimes a combination of multiple ideas.

Once I had decided on the general layouts for my screens, I created digital wireframes in Figma. I wanted to keep these wireframes very stripped down and gray-scale with only the basic layout and functionality so that I could test the basic functionality of my solution.

Digital wireframe home screen Digital wireframe create account
Wireframe Sketches
Wireframe Prototype

Usability Testing - Round 1

With my wireframes, I created an InVision prototype for my first round of usability testing.

I had my users guess the purpose of my site based only on the home screen and then I asked them to complete 4 tasks:

Create an account
Add a listing
Request to borrow an item
Delete a listing

Key Takeaways

The purpose of the site was very unclear. I was missing a hero image in my wireframes, so I thought creating an illustration for the home page would help.

Digital wireframe home screen High fidelity mockup home screen

I had two separate menus in my initial design and found that it was very confusing for some users. I decided to just combine everything into one menu.

Digital wireframe navigation menu Digital wireframe account menu
High fidelity mockup home menu

The “Create Listing” button was too difficult for users to find. I thought I would add a direct link into the navigation menu to make it more accessible.

Digital wireframe My listings screen High fidelity mockup enu

Users were confused about which page they were on. My initial thought was that adding color and style to the screens would help visually differentiate the screens.

Digital wireframe listings screen High fidelity mockup listings screen

Users didn’t understand some of the terms I was using, specifically around pricing. I thought adding some definitions and tips would help clarify the process.

Digital wireframe pricing screen High fidelity mockup pricing screen

Branding & Visual Design

Brand Characteristics

The id “Sugar” comes from the concept of borrowing a cup of sugar from a neighbor, so I wanted to embody that neighborly vibe in the branding. However, because I knew that users were concerned about damage and theft, I needed to make sure the site came across as professional and trustworthy. The brand characteristics I wanted to embody are:

Professional
Fun
Friendly
Gender-neutral
Minimal

Color Palette

Color Palette

For the color palette, my initial thought was to use greens because the environment was such a large motivator for users. However, I ultimately felt that didn’t jive well with the id “Sugar”, and decided I could do better. Pinks and purples are an obvious choice because they are bubbly and sweet, but I wanted to keep it gender neutral and that could easily turn feminine. I decided on a terracotta orange and periwinkle blue. They are gender neutral, friendly, professional, earthy, and align well with the id “Sugar”.

Moodboard image 1 Moodboard image 2 Moodboard image 3 Moodboard image 4 Moodboard image 5 Moodboard image 6 Moodboard image 7 Moodboard image 8 Moodboard image 9 Moodboard image 10 Moodboard image 11 Moodboard image 12

Typography

H1 RALEWAY BOLD 21px

H2 RALEWAY REGULAR 21px

H3 RALEWAY EXTRABOLD 14px

H4 RALEWAY REGULAR 14px

H5 Zilla Slab Light 17px

H6 Zilla Slab Light 14px

I struggled with the typography because I found it difficult to balance the fun/friendly side with the professional/trustworthy side. I knew I wanted to use two typefaces, one for the headers and one for body text.

For the headers, I liked the personality of some of the more organic typefaces, but ultimately decided they felt unprofessional. As for body text, I knew I wanted something with a serif and a fairly uniform stroke so that it would be easy to read. I decided to use Raleway for the headers and Zilla Slab for the body.

The logo text is actually a modification of Raleway Dots, but rather than dots, I used small squares, reminiscent of sugar cubes.

Sugar logo text

High Fidelity Mockups - v1

Once I had determined the direction I wanted to take the brand, I was able to create some high fidelity mockups, incorporating my learnings from the first round of usability testing. Some of the major edits I made were:

Adding an illustration to help users understand the purpose of the site.

Combining menus to help with navigation.

Linking to the “Create Listing” screens directly from the navigation menu.

Adding color and style to help with page differentiation.

Adding definitions and tips to help users through the process.

Sugar home screen version 1 Sugar menu screen version 1
Hi-Fi Mockups v1

Preference Testing

69% of participants preferred the gradient background (left).

Preference Test 1, version 1 Preference Test 1, version 2

88% of participants preferred the solid white background (right).

Preference Test 2, version 1 Preference Test 2, version 2

56% of participants preferred the pink message background (left). However, I did learn that the purpose of highlighting the message was unclear, so I knew I needed to adjust my design.

Preference Test 3, version 1 Preference Test 3, version 2

High Fidelity Mockups - v2

Taking all of that feedback into account, I made another round of iterations to my designs. The changes in this round were:

Scaling back the background colors.

Reducing the amount of dialog boxes.

Changing the “new message” highlight to a different type of marker.

Sugar create account screen version 2 Sugar requests screen version 2
Hi-Fi Mockups v2

Usability Testing - Round 2

At this point, I had added quite a bit to my designs and I needed to validate my decisions. I did a second round of usability tests and this time built my prototype in Figma so that I could take advantage of the horizontal scrolling feature. For this test, I again asked the users to guess the purpose of the website and then to complete six tasks:

Create an account
Add a listing
Request to borrow an item
Accept a borrow request
Delete a listing
Respond to a new message

Key Takeaways

The purpose of the site was much more clear with the addition of the illustration.

Navigation within the site needed to be quicker. Users were getting frustrated that they had to go into the menu to get anywhere, so I thought adding a bottom navigation bar would make the site more accessible.

Mockup menu screen Final mockup menu screen

Users were still having a difficult time with page differentiation, even after adding color and style. I decided to do three things:

Add page titles.
Change the layout of the listing cards.

Mockup listings screen Final mockup listings screen

Change the color of the search bar on some pages and add prompting text.

Mockup requests screen Final mockup requests screen

Final Design & Conclusion

Final Design

In my final design, I made the following changes:

Added bottom navigation with a “Create Listing” button.

Added page titles.

Changed search bar color and added prompting text.

Changed the layout of the listing cards within browse so they no longer resemble the listings on the “My Listings” page.

Prototype

Conclusion

The problems I set out to solve were wasted money, storage, and landfill. There is ample opportunity in the marketplace for a product that solves users’ needs, which are:

Peace of mind
Control over who they interact with
Guidance for pricing
Control over pricing

Sugar delivers on all of these user needs with a platform that is friendly, trustworthy, and intuitive and gives consumers the option to share things within their neighborhood.