Troops

An app for students to run errands for other students

My Roles:

User Research & Testing • UX • UI • Branding & Marketing

Type:

Startup with friends

Try the prototype
01

Project Overview

The misson

In Freshman year (2016), two of my best friends and I decided to create a platform to connect students to help other students get tasks done when they were doing them anyway. For instance, if I have a car and am going to pick up late night burgers at In ‘n Out or going to Ikea to pick up an item, why not help another student nearby who needs that task done and make some extra money? We thought that using public and private groups, students could post tasks they are doing to group chats (dorms, frats, classes) and the members of the posted groups can respond if they want the task to be done for them as well.

While apps to help with tasks existed, there was no existing platform to take advantage of the untapped supply of people who are already doing the task for themself. An app would make the process, including necessary details and the money transfer, clear and comfortable between the students.

The outcome

We user tested the basic idea with over 100 Stanford students, asking “What would you pay for to get done in the next 24 hours? What about in general, not necessarily in the next 24 hours?” Once we confirmed there was a need, we set up a google form and Facebook group and we stayed up late delivering late night food orders and running errands for our classmates. I did all of the UI and UX while my partners dealt with pitching, IOS development, and distribution. Though my Figma prototype was a bit rough as I didn’t have much experience, I really learned a lot!

We made over $1000 dollars, created a working website (now defunct), and secured an interview with YCombinator before we decided that we were too busy to be delivering other peoples’ hamburgers.

02

User Research and Testing

We found that...

There was a need a high need for laundry service (Most people could not afford professional laundry service but would love to have it done at a reduced price), cleaning services (Fraternities and Co-Ops really needed help with cleaning after parties and had the funds to pay people to do it), pick ups at stores outside of walking distance (only a few Stanford students have cars and the nearest store is over a mile away), and food delivery (many of Stanford's restaurant options are not available for delivery because they are not accessible by car.)

Many didn't trust a random stranger (who wasn't working for a company) to pick up their food or do their laundry (this is before food delivery apps like Doordash became so popular).
Most people would happily do a load of someone dorm mate's laundry if they are already doing a load of their own or pick up someone's food if they are already picking up food anyway

Students liked the idea of getting a fee on top of the cost of a food order and hated when people forgot to pay them back. At the same time, they felt a bit uncomfortable asking someone to pay them a fee.

We iterated by...

Starting with only a three options for jobs: laundry, store runs, and food pick up. By reducing the scope of the tasks offered to those that are in highest demand, we could design infrastructure to help facilitate each task.

Adding security systems (facebook profiles and student emails) to our app to ensure the users are students at the university and who they say they are.
Allowing users to choose the offers or requests they are interested in receiving notifications for. For example, someone can decide that they want to receive notifications for laundry offers nearby. This would make it easier for students to not miss out on opportunities to get in on an order.

making the payment system entirely automatic and not allowing users to set their own prices. We estimated it would be $5 per food pick up and $10 per laundry. This relieves the carrier of the discomfort of choosing a fee to charge their friends.

We got good feedback so we decided to test out the demand for the product by setting up a Facebook page with a form for people to send requests. We then transitioned to WhatsApp which turned to chaos...



In all, between the 3 of us and some of our friends, we made completed over 200 food orders and 10 laundry orders. Many were group deliveries where we brought food for multiple people. We were testing demand for service, delivery prices, and task execution experience. We found that there was a high demand for cheap deliveries late night and that tasks were relatively easy to complete.

03

Wireframing


I created rough prototypes and began testing it with friends to see what they thought about the user flow. This was my first time using Sketch, so I relied on a lot of youtube tutorials to get a somewhat unattractive first draft out. Users hop on and can swipe through tasks and offers, as well as filter for specific requests.

After a few iterations and insight from my teammates, I developed a much higher quality set of wireframes using Figma. For example, I learned that a navigation bar on top was uncomfortable to use on a phone so I moved it to the bottom. I also learned that the font was difficult to read so I completely changed the styling.

First set of wireframes


Redesign of wireframes

I pivoted away from a map home screen as we were focused on empowering the average student to easily make some money without having to go out of their way or stopping for anyone. This meant the deliveries should be within the community in which they lived (their dorm rooms, fraternities/sororities, and Co-Op houses). The map feature, on the other hand, prompts people to search for tasks to complete outside of their immediate community. The layout is much more conducive to an app for professional carriers who are looking to complete tasks for a living, but that is not what the use case we were interested in.





I came to the conclusion that the home page should be a messaging system as it allows for productive communication between the immediate community. For example, a student can message asking if anyone is planning on picking up food at TAP. Other people in the dorm interested can indicate they would like food there as well. Someone can volunteer to pick up and open up an order for people to add their orders to. It's similar to the way our Freshman dorm Groupme operated but without all the unpaid Venmo requests, confusion with the orders, and lack of incentive to post.



We secured an interview with YCombinator pitching our app and a few other investors. We created pitch decks, wrote out a marketing plan (which largely relied upon subsidizing early adopters on campuses and recruiting ambassadors), and began developing an app. Ultimately, I decided not to pursue it as the idea had a couple serious flaws. For example, we did not have the resources needed to update the constantly changing menus and prices for all the restaurants and stores we offered. While I believe we made some big mistakes, I learned a ton!

04

What did I learn?

1. How to create pitch decks

In preparation for our YCombinator interview, I learned how to properly market and pitch a product. I got much better at designing for Google Slides and learned how to do marketing analysis. Though we didn't get a spot in YCombinator, it was a great learning experience!

2. Sketch and Figma

This was my first project using Figma. I had experience fiddling on Sketch and designing for my High School newspaper using Adobe Illustrator and Photoshop, but I had never designed an app before. I took a course on Sketch and Figma between January and May of 2017 so I made huge improvements on my design throughout the iterative process. Leading the UX and UI for Troops was a huge growth experience for me.

3. How much I love Product Design

This project was the reason I decided to major in Product Design. I began to realize I had a good eye for product sensibility and loved the design process. I particularly loved the collaborative experience of staying up to 1AM every night in our Freshman year dorm basement designing how the app would work and the next steps.