EventMeet

Increasing event attendance through social community engagement

Role:

Solo product designer in charge of research - ideation - design - testing

Project Overview

Problem Statement

The business team has found that the number of people who say they are going to an event is significantly higher than the actual number of people who attend. Their data shows that, on average only 20% of people who RSVP actually show up at the event.

Scope and Constraints

Although I was familiar with most of the techniques required for this project, the time constraint forced me to carefully select the most effective techniques in order to complete the work within one month.

Goal

Increase the conversion of accepted invites to event attendees and help people to meet new friends.

The Solution

EventMeet is an app that increases event attendance through several key features, including:

  • A pre-event group chat feature, which helps connect attendees who are attending alone.
  • Notifications for users before an event they have RSVP'd for.
  • A customizable filter button for event criteria such as ticket price, distance, and subject.

Impact of Solution

Participants found the user flow to be smooth and straight forward

Participants liked the UI design of the app

Participants said an app like this could help them attend more events

1

Empathize

2

Define

3

Ideate

4

Prototype

5

Test

Process

I followed the Design Thinking process as a roadmap to make sure that my design decisions were supported by user research and feedback.

Empathize

Competitive analysis

I began this project by conducting competitive analysis of apps with similar goals, focusing on their user flows for RSVPing to events.

Key Insights

Add a filter button for date, category, type of event, and distance.

Include a section for users to see their previous and upcoming events.

Allow users to see the list of participants for each event.

Use live and exciting colors for CTA buttons.

Ensure a clear search box for users to search for specific events by keyword.

Display a "free" label for events that do not require payment.

Interview

I created a screener survey to identify five individuals who have previously RSVP'd for an event but did not attend.

Conducting interview with a person

Define

Affinity Maps

After conducting user interviews, I used affinity mapping to group and categorize the information collected into general themes. This process provided me with more in-depth insights into the factors that prevent my target users from attending events, which in turn helped me create detailed personas.

Affinity maps (see photo)

Findings:

  • 100% reported that they sometimes become too busy to attend events they have previously RSVP'd for.
  • 80% reported that they would not attend an event if they did not have any friends there.
  • 40% reported that they sometimes forget about events they have RSVP'd for.
  • Event distance and traffic, subject, and ticket price were identified as other important factors for users attending an event.
Factors that prevent people from attending an event

Persona

I used the results from the affinity maps to create two personas that represent different types of users:

  1. The first persona is someone who values the social aspect of events and would not attend if they did not have friends to go with, and sometimes forgets about events.
  2. The second persona is someone who is motivated by professional growth and is comfortable attending events alone.

Based on the insights gained from the personas, it became clear that the first group, who values attending events with friends, should be my primary focus when developing solutions.

Primary persona (see photo)
Secondary persona (see photo)

How Might We Statement

Using affinity maps and persona, I created “how might we” questions to reframe my insights to provide an accurate description of the challenges I had. It also led me Ideate on the right problems during the next phases of the project.

1

How might we minimize factors that prevent people from attending an event?

3

How might we find ways so people won’t forget about the events?

2

How might we create a community so people can make friends to go with to an event?

Ideate

User Flows

Creating user flows was a critical step in understanding the series of actions required to guide my users from the homepage of the app to RSVPing for an event.

To help my main persona attend events with friends and remember scheduled events, a significant challenge was creating a feature to enable her to connect with other attendees and start conversations.

User Flow: RSVP an event

User flow: RSVP an event (see photo)

Sketching

After mapping out the user flows, I began sketching screens that addressed my users' pain points.

Sketches (see photo)

Wireframing

After sketching, I created high-fidelity wireframes in Figma to add more detail and visualize the final screens.
This also helped me test the user flow for RSVP, see how users would interact with the group chat and notification screens.

A couple of wireframes are shown below:

Some high fidelity wireframes

Creating a Brand and Style Guide

Before creating high-fidelity screens, I developed a style guide to define the look and feel of the app's UI elements.

The business team provided the brand platform, which included the brand attributes and personality. Using this information, I created:

  • App name and Logo
  • Color Palette
  • Fonts
  • UI Elements
  • Iconography

to ensure consistency with the brand platform.

To make the app as accessible and inclusive as possible, I ensured that all colors passed AAA-rated contrast requirements and all fonts and UI elements followed both Apple and Google's design principles for sizing.

Brand and style guide

Usability Testing 1

I created an interactive prototype using Figma and conducted a moderated usability testing on 5 participants.

Although 4 out of 5 users told me that the user flow was smooth, there were some pain points.

Prototype & Redesign

High Fidelity Interactive Prototyping

With the users' pain points in mind, I created high fidelity screens by revising my design solutions based on the feedback gathered during user testing:

Pain Point 1:

Expected to see more icons on the filter screen.

Design Solution:

  • Added some chips with icons instead of checkboxes.

Pain Point 2:

Group chat was hard to be found.

Design Solution:

  • Allotted a separated screen for group chat after the RSVP process to make it more visible.
  • Changed the name of the group chat to make it more tempting to join.

Pain Point 3:

Pop up notification was hard to be read.

Design Solution:

  • Changed the style and made the clickable part bigger.

Creating high fidelity screens helped me conduct the next round of user tests, as participants could better interact with the app in this stage, and they could give me more reliable feedback. It also helped me to see what the final app would look like.

Usability Testing 2 & Redesign

Usability Testing 2

I conducted a second moderated usability testing on 5 new participants.
While all 5 users told me the flow was smooth, there were some parts that needed to be revised.

Here includes the most important results of the user testing before and after revising my design solutions:

Pain Point:

Expected a confirmation note after activating notification for upcoming events.

Design Solution:

  • Added a pop-up message that confirms the user's selection.
  • Added a note to the event cart that informs users that they will receive notifications for upcoming events.

Below includes the summary of the users’ pain points in usability test 1 and their success in usability test 2 after revising those pain points:

Users’ pain points in usability test 1 and their success in usability test 2
A couple of final screens
RSVP an event flow
Join event chat flow
Activate notification for events flow
View Prototype

Challenges & Lessons Learned

  • Pre-event group chat feature: One of the biggest challenges in this project was creating a feature that would encourage users to engage with each other and start conversations before events.
  • Project constraints: I learned to select and prioritize design methods and techniques for maximum impact when faced with time and resource constraints in the project.
  • The importance of usability testing: Although icons and labels may be familiar to me, it does not guarantee that users will understand their meaning. Usability testing helps to validate design decisions and ensure that users can understand the app as intended.

Edge Cases I thought about

  • Specific events: Users can use the search box to find specific events or subjects if they cannot locate them through the "Filter" button.
  • Event location: Users can change the event location to their desired address by accessing the search box and typing in the event name.

Next Steps

  • Develop a web version: Given more time, I would have considered developing a web version of the app and incorporating additional features such as hover states.
  • Group messaging feature: Given more time, I would have focused on enhancing the group messaging feature by adding more options, such as auto commands and auto replies, to make messaging more efficient and user-friendly.
  • Follow other event attendees: If given more time, I would enhance the app by adding the capability for users to follow other event attendees to see which events they are attending. Additionally, I would incorporate video and voice chat features into the messaging functionality.
Back to Top