Case Study

Post Up

Helping remote workers locate public spaces to set up and work.
Role
Strategy, UX, UI Design, Usability Testing
Focus
Consolidate everything a remote worker needs to evaluate a space into a single, scannable interface
Tools
Adobe CS, Figma

Too long; didn't read

SUS Score
95.625
CSAT
100%
WTP (unprompted)
3 of 6 test participants
An iPhone sitting on the corner of a wooden table showing a map with search results for a cafe with ratings and other information.

The Problem

Remote workers are a permanent fixture of the modern economy — and they're working from everywhere except their own offices. Coffee shops, libraries, hotel lobbies, coworking day passes, parks with decent WiFi. The problem isn't finding a space. It's finding the right space.

The current workflow for finding a remote-friendly location is fragmented and time-consuming: Google Maps for location, Yelp for reviews, the venue's website for hours, a separate search for WiFi quality, noise level, and outlet availability.

A worker can spend twenty minutes researching a location
only to arrive and discover the WiFi requires a purchase or the space is full by 9am.

The Goal

Build a mobile app that consolidates everything a remote worker needs to evaluate a space into a single, scannable interface, so the decision from "I need somewhere to work" to "I'm walking in the door" takes 2 minutes, not 20.

The secondary goal: make it valuable enough that users would pay a monthly subscription. That bar shaped every feature decision.

Understanding the users

I was provided with pre-existing user research: research highlights, a user interview, and a persona. Rather than treating these as a brief to execute against, I used them as a starting point for my own synthesis — identifying the underlying behaviors and mental models that the surface-level pain points pointed toward.

Three patterns emerged as the foundation for every design decision:

Specificity
Remote workers aren't looking for "a coffee shop." They're looking for a coffee shop with reliable WiFi, at least four outlets near seating, moderate noise level, no two-drink minimum, and open until 8pm on Tuesdays. General-purpose apps can't surface that specificity. Post Up needed to.
Fragmentation
The existing workflow requires bouncing between Google Maps, Yelp, the venue's website, and often Reddit threads where someone asked the same question six months ago. Post Up needed to consolidate, not add to the stack.
Unfamiliar territory
Remote workers frequently work from cities they don't know — conference trips, client visits, workations. In unfamiliar territory, the stakes of a bad location choice are higher because there's no fallback. The app needed to perform for someone with no local knowledge.
A user journey flow showing the steps a user might take when using an app.

Competitive analysis

I used a lightning demo to study three apps that solve adjacent discovery problems: AllTrails (finding hiking trails), Upside (finding gas deals), and Yelp (finding restaurants). The goal wasn't visual inspiration, it was understanding what each app's design decisions teach about discovery UX, and what gap they collectively leave.

What All Trails gets right

Highly specific, filterable search built around the attributes that actually matter to the user; trail length, elevation gain, difficulty, surface type. The filter system is the product. Users come for the specificity that Google Maps can't provide. Post Up needed the same filter-first logic applied to workspace attributes.

A set of 3 screenshots of the All Trails app

What Upside gets right

Extremely low-friction entry. The default state is a map with immediate, scannable results. No search required to start seeing value. The passive discovery model is something Post Up could borrow for users who don't have a specific destination in mind.

A set of 3 screenshots of the Upside app

What Yelp gets right

Social proof at scale. Review volume, photo quality, and recency signals do the work of building trust before a user commits to visiting.

A set of 3 screenshots of the Yelp app

Exploration

Crazy 8s

I focused the Crazy 8s exploration on highest-stakes screen in the experience, the results screen. The search itself is straightforward; the pain is in evaluating results. Eight rough directions in eight minutes, then a structured vote.

Direction 4 won: a card-based results list that prioritizes scannability over exhaustive information. Each card shows the venue name, a crowd meter, distance from the user, an amenity icon strip, and an overall rating. The decision to use icons rather than text for amenities was deliberate. A row of icons can be read in under a second, a list of words takes three times as long.

A set of 3 screenshots of the Yelp app

Sketching and storyboarding

With the results card direction chosen, I sketched the full primary flow: app launch to arrival at a chosen location. Three screens anchored the experience.

Home screen
A map view with three quick-access location type buttons — the fastest path from open to results for users who know roughly what they want. A custom search link handles the specificity case for users with detailed requirements.
Results screen
The card system from the Crazy 8s decision, implemented with consistent information hierarchy across every card. Scannable, sortable, immediately actionable.
Location detail screen
A hero image, the full amenity set, hours and real-time busy times, and user reviews filtered for remote-work relevance. This is where the decision gets made so the information architecture prioritized the attributes that actually move that decision.

The storyboard extended the design beyond the app screens to validate the full use case: user realizes they need a workspace → searches Post Up → evaluates two or three options → reads reviews → gets directions → arrives. Each step mapped to a screen or interaction. The storyboard made one thing immediately clear: the review and photo content would determine whether users trusted the app enough to act on it. The UI could be perfect and the app could still fail if the content wasn't credible.One of the core challenges in SMS-based interfaces is that conversation can break in ways a graphical UI never encounters. A user can type anything. They can ignore a prompt. They can respond hours later. The system has to be resilient to all of it.

Prototyping

I built the prototype with realistic content throughout — real venue names, real photos, real amenity combinations — rather than placeholder text and generic images. The rationale: usability testing with placeholder content would measure how users navigate a prototype. Testing with real content would measure whether users trusted the product enough to use it.

Visual direction stayed close to the existing Post Up brand: clean, modern, high contrast, minimal decorative elements. The information was designed to do the work, not the aesthetic.

Usability testing

Five participants. Moderated sessions. Each participant was given two tasks: find a workspace within a specific distance that meets a defined set of amenity requirements, then find a workspace in an unfamiliar neighborhood with no prior criteria.

Four issues emerged clearly enough to be considered critical.

Icon legibility
Of the amenity icons used in the results cards, the volume and the cost/no-cost icons were misinterpreted or questioned in three of five sessions. Users correctly identified the remaining four icon types without hesitation. The volume icon failed because it was difficult to tell the difference between low- and high-volume spaces at a glance. The cost/no-cost icons failed for the same reason.
UI limitations
The users felt limited by the UI; the map needed to be interactive and the search feature and filtering options needed to be more robust. The users wanted more freedom in how they could navigate and discover new workspaces.
Content credibility
Across all five sessions, participants raised unprompted questions about how photos and reviews would be sourced and maintained. This wasn't a UI problem, it was a trust architecture problem that the design couldn't solve without a clear content strategy.
Subscription value gap
When asked directly whether they'd pay a monthly fee for Post Up, three of five participants hesitated. The features shown weren't sufficient justification for recurring cost.

What testing revealed

The usability issues were solvable. The content credibility problem and the value gap were the more important findings — and they pointed toward the same root cause.

Post Up, as designed, helps users find information that exists elsewhere. It aggregates and consolidates. That's genuinely useful, but it's not yet a product users will pay for, because the value proposition — "we found this so you don't have to" — doesn't hold if users can find it themselves with two extra taps.

The version of Post Up that closes the value gap is one that generates insights users can't get anywhere else. Real-time occupancy data integrated directly from venue systems. Crowdsourced, remote-worker-specific reviews. Predictive busy-time modeling by day of week and time of day.

That's not a design failure. It's a product scope question that the UX work surfaced. The prototype did its job: it revealed the most important question the MVP hadn't yet answered.

What I'd build next

Worker-verified reviews
A review format built specifically for the remote-work use case; structured fields for WiFi speed, outlet availability, noise level, staff friendliness to long-stayers, and purchase requirements.
Curated collections
Editor- or community-curated lists for specific use cases: "Best spots for video calls in Austin," "Quiet spaces with all-day seating in NYC," "No-purchase-required spots near downtown." Reduces the cognitive load for users who want a recommendation, not a search.

Lessons learned

The MVP bar is higher than "functional"
A product that works is not automatically a product worth paying for. The right question to ask at the start of every project with a monetization goal is: what does this need to uniquely provide that users cannot get elsewhere? That question would have redirected the feature prioritization earlier.
Content strategy is not a handoff problem
The moment usability testing revealed that the credibility of photos and reviews was a primary concern, the right response was to design the content sourcing model alongside the UI. For products where the content is the product, the design of how that content is generated and maintained is as important as the design of how it's displayed.

Other work

Case Study

NAF

National recruitment campaign with 677% increase in candidate acquisition over 4 months.
View Case Study
View Case Study
Case Study

NAF Pride

Helping make home ownership more accessible, inclusive, and affirming for LGBTQ+ individuals and families.
View Case Study
View Case Study