Wework

Increasing the conversion rates for Wework India On-Demand

Increasing the conversion rates for Wework India On-Demand

Wework

Increasing the conversion rates for Wework India On-Demand

Logo

Role

UX Intern @ Design Brewery

Year

2023

Timeline

Timeline

May - June (4 weeks)

Team Size

Team Size

5 Designers + Researchers

Keywords

Keywords

UX Audit, Funnel Analysis, Heuristic Analysis, User Flow, UI Redesign

TL;DR

What is wework, theirofferings, the problem and what was fixed

Objectives

The project kicked off with a crucial two-stage approach. In the first stage, I was entrusted with another UX designer to quickly assess the existing design. Our goal was to identify immediate pain points and develop a concept sample design that we could present to the WeWork team. The second phase involved improving the booking flow, and finally creating device agnostic design for the product.

Phase 1: Initial Audit & Research

A Puzzling Drop-off

92% of the traffic came from mobile, yet the conversion rate was 0.7%

Our deep dive into the analytics for this initial audit quickly revealed a stark reality. While an overwhelming 92% of WeWork India's user traffic flowed from mobile devices, the conversion rate on these very devices lingered at a dismal 0.7%.


We began by analyzing the existing booking funnel, which consisted of eight steps across both mobile and desktop platforms. The funnel tracked users from session start through to final purchase, including viewing workspace lists, selecting items, adding to cart, and completing checkout.

The current paradigm led me to believe that there is a "crisis of imagination," a stagnation in design where we've accepted a passive, fragmented user experience. The process of performing a simple task like checking flight times or creating a calendar event requires multiple manual steps and navigation across different apps, creating unnecessary cognitive load.

The mobile experience was failing at the very first step. While desktop performed at industry standards, it represented only 8% of total traffic. We were essentially optimizing for the wrong platform.


Our research revealed how far behind WeWork's mobile experience was lagging. The industry standard Next Step Rate for mobile e-commerce sits at 61.69%, while WeWork achieved only 14.81% - a gap of 46.88%. The bounce rate told an even more concerning story with the mobile bounce rate being 85%, far higher than the industry standard of 41%

The current paradigm led me to believe that there is a "crisis of imagination," a stagnation in design where we've accepted a passive, fragmented user experience. The process of performing a simple task like checking flight times or creating a calendar event requires multiple manual steps and navigation across different apps, creating unnecessary cognitive load.

Heuristic Evaluation Findings

We conducted a systematic heuristic evaluation of the existing interface, focusing on the first two steps where most users dropped off.

The mobile homepage violated multiple usability principles.

  • The banner area consumed excessive screen space, pushing actionable elements below the fold.

  • The copy on the search button on the mobile website says "Book Workspace" which is too early for the user to commit before finding the right workspace.

  • On the View Item List page on mobile, the entire first fold contained no actionable items to progress the journey.

  • Users encountered blocks of text and unnecessary iconography before seeing actual workspace options.

and many more…

Acknowledging this crisis of imagination led me to ask a broader question:


How do we go beyond incremental improvements and rethink the way we interact with our devices?


To tackle that, I needed a methodology that wasn’t just about fixing what’s broken, but one that could help me imagine what should be and what could be. employed a dual methodological approach, using Design Futures and Design Fiction.


Design Futures merges Design Thinking's problem-solving with Futures Thinking's foresight. The (modified) diagram above by Elliot P. Montgomery shows where these methods lie in this spectrum between the Unconstrained & Imaginary and Constrained & Applied design practices.


In this approach, I looked at what’s currently trending today—AI, LLMs, agentic frameworks and tools and designed for probable futures i.e. scenarios that are likely enabled by near-term technological advancements in other words, what could we realistically build now?

Creating the Sample Solution

Rather than just presenting problems, we developed a prototype demonstrating potential improvements.

We reduced the banner size to maximize actionable screen space. Using geolocation, we pre-selected the user's city and showed all locations by default. The three service types became sticky tabs that remained accessible while scrolling. We redesigned the workspace cards with image sliders, allowing users to explore spaces without leaving the list view.


This initial presentation, combining our audit findings with the sample solution, convinced WeWork to proceed with a full redesign project. They approved a one-month sprint to address critical issues, with potential for extended engagement based on results.

Acknowledging this crisis of imagination led me to ask a broader question:


How do we go beyond incremental improvements and rethink the way we interact with our devices?


To tackle that, I needed a methodology that wasn’t just about fixing what’s broken, but one that could help me imagine what should be and what could be. employed a dual methodological approach, using Design Futures and Design Fiction.


Design Futures merges Design Thinking's problem-solving with Futures Thinking's foresight. The (modified) diagram above by Elliot P. Montgomery shows where these methods lie in this spectrum between the Unconstrained & Imaginary and Constrained & Applied design practices.


In this approach, I looked at what’s currently trending today—AI, LLMs, agentic frameworks and tools and designed for probable futures i.e. scenarios that are likely enabled by near-term technological advancements in other words, what could we realistically build now?

Phase 2: Deep Research

Detailed Funnel Analysis by Service Type

With WeWork's approval, we dove deeper into understanding user behavior across their three main offerings. The data revealed distinct patterns.


We started by segmenting the funnel data by service type.

  • Day Pass showed 699,000 sessions converting to just 6,100 purchases.

  • Conference Rooms performed better proportionally, with 56,000 sessions leading to 2,000 bookings.

  • But the real surprise was Day Pass Bundles—despite being the most profitable offering for WeWork, it attracted only 3,700 sessions with 1,400 conversions. The bundles had a better conversion rate but suffered from low awareness.


The abandonment patterns were consistent across all three offerings. Between 45% and 85% of users dropped off at four critical points: landing on the page, viewing the list of buildings, selecting a specific space, and adding billing details. Mobile showed 70% to 85% abandonment rates compared to desktop across all these steps

Competitor Analysis

Our competitor analysis revealed fascinating contrasts in approach.

  • MyHQ had implemented quick filtering directly within listing pages, reducing time to purchase.

  • Workafella used clean, minimal designs optimized for mobile loading speeds.

  • Regus' checkout flow wasn't particularly innovative but their listing page wasefficient. Filters and sorting options were prominently displayed, and the information hierarchy perfectly matched user priorities.

Social Media

  • Unclear Product Offerings: WeWork's On-Demand ads didn't specify the different types of flexible workspaces available, such as day passes, bundles, or conference rooms, which confused new users.

  • Vague Social Media Messaging: WeWork India's social media used too many aspirational adjectives like "inspiring" and "collaborative" without providing concrete details or benefits, unlike their competitors.

  • Mixed Messaging in Video Ads: Their YouTube video ads tried to appeal to both individual freelancers and large enterprise teams simultaneously, which diluted their message and confused their target audience.

  • Word Cloud Analysis: A word cloud analysis showed WeWork's social media content lacked keywords related to amenities, while competitors like Workafella had a better balance of descriptive adjectives and service-oriented words.

User Research and Personas

Using the data we were provided we identified the top three client industries: Technology (obviously), Consulting and Creative Services. Individual Contributors and management-level roles were equal in distribution.234w1

Most surprisingly, the majority of On-Demand clients either owned or worked for incorporated businesses. These weren't just freelancers looking for WiFi and coffee. They were serious professionals who needed flexible but professional workspaces.

We developed four personas based on this data:

  • The freelancer booking spaces while commuting.

  • The startup founder needing impressive meeting rooms.

  • The team lead coordinating group bookings.

  • The digital nomad prioritizing location and amenities.

System Usability Scale Testing

We conducted SUS testing with representative users to quantify the usability issues

To quantify the website's usability issues, we conducted a System Usability Scale (SUS) test with 10 representative users at a nearby WeWork workspace.


The website achieved a final SUS score of

55.25, which is rated as "Below Average". This score is well below the industry average of 68 and falls into the "Marginal" acceptability range, suggesting that users are likely to have a negative experience with the site.


This quantitative data supported our qualitative findings. During the test, users consistently rated the system as unnecessarily complex and noted that there was too much inconsistency throughout the booking process. This test helped us set the focus on areas of improvement in the booking flow.

Booking Flow Analysis Deep Dive

The existing booking flow required users to make too many decisions too early.

Our detailed booking flow analysis revealed structural problems beyond the interface issues. The "How it works" link on the homepage took users to a completely different website section, breaking their mental model of the booking flow. The "Call us" CTA, meant to be helpful, took the user out of the booking flow with no way to return.


The existing workflow required users to make too many decisions too early. Before seeing any actual workspaces, users had to choose between Day Pass, Bundles, or Conference Rooms—distinctions that weren't always clear. Then they selected a city, then a specific location, all before seeing if spaces were even available.


We mapped out the current user journey and identified multiple points where unnecessary complexity created friction. The system asked for team member details individually rather than just the number of seats needed. The date selection came after space selection, meaning users might fall in love with a space only to find it unavailable on their desired date.

Phase 3: The Redesign

New booking workflow

With research complete and insights synthesized, we began the actual redesign.


The new workflow compressed eight steps into four intuitive stages. First, the system auto-detected user location and immediately showed available workspaces nearby. Users could adjust the location if needed, but smart defaults eliminated friction for the majority. Second, users browsed and selected spaces with rich visual previews and key information visible at a glance. Third, they specified their needs, dates, number of seats, and duration with intelligent suggestions based on availability. Finally, a streamlined payment process with saved preferences and one-click options for returning users.

Mobile-First Design Approach

Frontend Architecture

More decisions explained

Frontend Architecture

More decisions explained

Frontend Architecture

More decisions explained

Frontend Architecture

More decisions explained

Frontend Architecture

More decisions explained

Results

The interface is rendered in React, using GridStack.js to manage layout, resizing, and drag-and-drop interactions. The renderer interprets the JSON specification coming from the orchestration layer and maps each component definition to a corresponding widget. GridStack’s persistence features, paired with a Supabase backend, allow widget positions and configurations to be stored between sessions. This means that even though Genie dynamically generates new widgets on demand, users retain control over how those widgets live on their screen.

Takeaway

The interface is rendered in React, using GridStack.js to manage layout, resizing, and drag-and-drop interactions. The renderer interprets the JSON specification coming from the orchestration layer and maps each component definition to a corresponding widget. GridStack’s persistence features, paired with a Supabase backend, allow widget positions and configurations to be stored between sessions. This means that even though Genie dynamically generates new widgets on demand, users retain control over how those widgets live on their screen.

Navin Thomsy is an Indian third-culture kid and a multidisciplinary designer driven by a passion for systematic thinking & experience design.

Contact

Resume

Navin

Thomsy

Navin Thomsy is an Indian third-culture kid and a multidisciplinary designer driven by a passion for systematic thinking & experience design.

Contact

Resume

Navin

Thomsy

Navin Thomsy is an Indian third-culture kid and a multidisciplinary designer driven by a passion for systematic thinking & experience design.

Contact

Resume

Navin

Thomsy