Overview

PostUp is a mobile app that utilizes places already available to the public, filters reviews for work-specific needs, and determines how to efficiently get there. For this project, I utilized a Design Sprint to guide the app in the right direction, and is still in the design stages as more edits can be made.

Design challenge:

Problem

From user interviews, workers had issues finding places that had amenities they wanted (free wifi, quiet places for calls, avoiding crowds, sufficient outlets, etc). It can sometimes take a lot of time to read through reviews and finding sufficient information and it isn’t the best if one has a limited amount of time to work. 

Persona

Nina is a freelance copywriter and works at least 3 days traveling for client meetings and remote work. Between meetings, she’ll want to work somewhere, but sometimes she spends more time looking for a place than actually working. She wants to be able to spend less time finding places so she can get more work done.

Day 1: Map

Day 2: Sketch (and competitor research)

Yelp

Pros

  • portable app
  • lists amenities
  • picture of dishes and interior with the ability to filter which

Cons

  • not all work related amenities available
  • most photos are of food
  • reviews are food based ​​​​​​​

Workfrom

Pros

  • work-related amenities
  • View by location

Cons

  • community-based forum on slack, but paid ($100 for life, they say they have 3.5k members)
  • website only unless you pay for the Slack

Sketches

Crazy 8's

Maps are simple, so I focused on different ways to display the icons vs what they meant and how many different ones should there be. I chose the map as the most important screen to focus on for this activity because that is the visual that will present the options to the user to choose the place they decide to work at.​​​​​​​

Solution Sketch

I wanted to make it as efficient as possible, so having people select things that they need and filtering the surrounding cafes was the best option.

  • The only question now is how many different variations would remote workers want?’

From interviews I conducted, people worked remotely, but that wasn’t their main way of working. This would be something to consider because some may want a space for working with a client vs working alone vs in a group.

Day 3: Decide

Day 4: Prototype

Features:

Day 5: Test

I conducted a usability test with

Everyone I tested was able to navigate the app relatively easily with some confusion here and there.

The main challenge was to make it simple and there should be something “more” in order for one to want to pay for it. After having conversations with all the potential users, I decided that adding a feature to efficiently go to the destination to work would be ideal. Distance doesn’t always matter because it may not be fast to get there by the user’s preferred mode of transportation.

Learnings

This was an interesting experience as this was a fast-paced process, but it helped me learn to prioritize and finished it earlier than I need to.  Scheduling and coordinating to get testing all done in one day was overwhelming at the time, but I felt accomplished being able to do so when I was done.

For future iterations of the project:

Their priorities for efficiently getting around would potentially be higher when having multiple meetings and needing to get work done in between. Having a good understanding of what people would pay for is important when wanting to do a subscription service for an app.

NEXT PROJECT: ETAL