Advertising Partner

We developed an MVP monetisation

feature

that

advertises

partner

venues

and

events

as

suggested

templates,

enabling

users

to

create

Clyx

events

effortlessly

View Clyx Website

Role:

UX Lead

Duration:

4 weeks

Tools:

Figma, Figjam, Mixpanel, Zoom, Typeform, OneSignal

My Role

As UX Lead, I used a combination of qualitative and quantitative research methods to develop actionable insights into user goals, pain points, and expectations. Based on these insights, I designed potential solutions for review with Clyx’s Founder and Head of Growth. After reaching a consensus, I communicated the solution via user flows and wireframes to the dev teams before completing the handover by providing the finalised designs.

Context

Clyx’s core monetisation strategy revolves around advertising partner content for users to join and go to in-person. Currently, this is achieved by business accounts posting their own events.

Problem

While events hosted by our partners fit easily in to the existing event discovery flows, many partners want to advertise their venues irrespective of a hosted event.

So, how do we advertise un-hosted content?

Work flow
Defining Success
01

Conversion

% of users who engage in partner content in their first 30 days

02

Recurrence

% of converted users who who engage in partner content for a second time

03

Retentiveness

% difference in D7, & D30 on or after retention for relevant cohorts

Research

Through data analysis, we developed an initial understanding of users' content creation behaviour, focusing the types of events and details

Based on specific cohorts, we conducted stratified sampling

Through interviews and surveys, we developed insights into users’ off-Clyx behaviour when finding venues, especially what information they prioritise, how they make decisions, and how they invite others. By analysing user data and navigation patterns, we then researched how this new feature could fit into our current ecosystem.

Process
Insights
01

Images, proximity, & reviews are key factors

When looking for venues, users tend to look for this information to narrow their search.

02

Users need flexibility on what they decide first

The first decision in the organisational process fluctuates based on a variety of factors.

03

User-events outperform business-hosted events

Clyx's key value prop is to meet new people IRL. The more people-focused an event is, the better.

04

Only creators open the create flow regularly

We want to target all users, not just creators. For this feature to have high top-of-funnel, it needs its own space.

Ideation & synthesis
01

Insight-driven brainstorming

After researching, we developed a pool of possible solutions backed by our insights.

02

Affinity
Mapping

To synthesise our potential solutions, we thematically grouped them to combine overlapping options.

03

Development cost analysis

Finally, we compared expected dev costs to find the right balance of cost and potential benefit.

User flow & wireframing

Next, we began the design process by creating wireframes - focusing on information architecture while minimising development cost.

Once we came to our chosen solution, we mapped it out in a user flow to ensure clarity and alignment with our insights.

Finally, we began the handover process by communicating the user flow and wireframes to the FE & BE teams for a technical review.

Solution
01

Step-by-step flow changed to a central hub with sub pages

To reduce the number of potential drop off points

02

All detail fields except the title are given defaults with optional editing

To reduce the number of barriers to posting

Wireframes
01

Detail options are grouped by importance

To incrementally encourage users to add detail optional without overwhelming them

02

A bottom sheet is used instead of a full page

To clarify the connection between the creation process and the home feed.

03

Most assets from the previous iteration are reused

To reduce development
cost and maintain our release cycle.

Solution
01

Step-by-step flow changed to a central hub with sub pages

To reduce the number of potential drop off points

02

All detail fields except the title are given defaults with optional editing

To reduce the number of barriers to posting

03

Detail options are grouped by importance

To incrementally encourage users to add detail optional without overwhelming them

04

Most assets from the previous iteration are reused

To reduce development
cost and maintain our release cycle.

04

Ideas use an alternate content format to the feed

To differentiate events from idea suggestions.

05

User-specific and activity-type categorisation are separated

To allow us to easily tailor the promotion of partner content to each user while still providing flow flexibility

01

User can view through user-specific or venue-type categories

To provide flexibility on decision ordering.

02

User-specific categorising is variable

To provide opportunities for testing.

03

Steps to post are minimised

To reduce drop off and simplify the process.

Designs

The key element of our chosen solution is it's flexibility for testing. With its own page, we're able to adjust the context and ordering in which we present the content without interfering with other features. Outside of testing, the feature provides suggestions in a clear and easily navigable way, allowing users to explore and find something they love quickly.

Key info is highlighted early

Based on our research, images, proximity, and reviews are the three strongest factors when deciding between venues. To help users make decisions faster, this info is clearly displayed on the outside of all suggestions.

Testing user-centric categorisation

The discover page utilises user-specific categorisation to offer personalised suggestions. Each section can easily be swapped out to create new combinations for multivariate testing.

Testing activity-type categorisation

In the case where users are looking for an idea that is specific to a type of activity, category filters are available at the top of the page. The ordering of these categories is flexible based on the types of activities we see the most demand for.

Impact

66%

Conversion to joining

% of active users who have joined a suggestion-created-event

30%

Conversion to posting

% of active users who have created a suggestion-event

65%

Repeat conversion to posting

% of converted users who use a suggested event twice in 30 days

+12 pp

Higher D30 posting cohort retention

D30 retention for posting cohort against the non-converted cohort.

Iterations
01

Merger with feed

Most users don't open the discover page frequently enough.

So, to further increase top of funnel and reduce the number of features the user needs to learn, we merged the discover page with the home feed.

02

Retaining idea originator

The cohort of users who have joined events created from suggestions, don't convert to creating from a suggestion any more frequently.

When a user creates an event from an idea, the source of the idea is shown alongside the user who turned it in to an event.