To incentivise meaningful human relationships online and offline by becoming the primary touchpoint for hospitality, providing groundbreaking interactive tools to consumers, professionals, and businesses, which are built on top of the largest and first fully mathematised datasets that layer industry entities and turn them into matrices, making hospitality analysable and generative.

<aside> <img src="/icons/view_gray.svg" alt="/icons/view_gray.svg" width="40px" />

General Information

Domen:

Date:

Role:

Market:

Event Management and HoReCa (Hotels, Restaurants, Cafés).

June 2024 - September 2024

Product Designer, UX/UI Designer

United Kingdom (UK)

</aside>

<aside> <img src="/icons/book_lightgray.svg" alt="/icons/book_lightgray.svg" width="40px" />

About the Functionality

Purpose: This is a new tool for organizing events in bars and restaurants. It allows users to invite friends, discover new places, and expand their social circles. The system motivates users and helps promote venues through organized parties.

Hangout is a feature that encourages users to participate in offline meetups and events at bars. It allows for easy organization of gatherings, inviting friends, and discovering new venues. The motivational point system incentivizes users to actively participate and provides opportunities to receive discounts at establishments.

</aside>

<aside> <img src="/icons/book_lightgray.svg" alt="/icons/book_lightgray.svg" width="40px" />

Tests:

Types of Tests: Quantitative and qualitative.

UX Tools: • Prototype testing, closed (Quantitative). • Qualitative interviews. • AI testing.

Methodology: Double Diamond.

Segmentation: Yes

Iterative Process: Yes

Scenarios:

Two

• Creating a hangout.

• Joining an existing hangout.

</aside>

<aside> <img src="/icons/book_lightgray.svg" alt="/icons/book_lightgray.svg" width="40px" />

Other work:

Design-system: Refactoring and improving component base and approach.

Documentation: Writing documentation and describing components.

Communication with development: Collaborative work and planning improvements for components together with the team, creating processes for implementing components from the UI kit into the dev kit.

</aside>

Introduction

💡 Goal

Encourage users to engage in offline interactions by creating an environment where they can easily organize meetups and events at bars. Promote venues through the platform and motivate users to organize events through a point system that can be exchanged for discounts.

🎯 Objectives

• Create an intuitive and user-friendly interface for organizing meetings and events.
• Help people expand their social circles through the DrankStar platform.
• Provide users with the opportunity to quickly share their parties and attract new people.
• Provide a convenient mechanism for promoting bars and establishments through communities on the platform.

🧐 Issue

Many users remain in the online space and lack sufficient motivation to move communication offline. Bars are also not always recognized or visited by new customers due to limited visibility. We need to find a way to engage users in attending events and support venues in their promotion efforts.

Usage Scenarios

1. Joining an Event:

Key-auditory

The user searches for events in their city and joins those that align with their interests

2. Event Organization

Second-auditory

The user creates an event, selects a bar, invites friends, and opens it up for others to join.

3. View recommendations:

Second-auditory

The user browses a list of bars based on recommendations from other users, ratings, and event locations.

Script Writing for Respondents

Our research focused on understanding what users truly want and the challenges they face. We began by creating a list of interview questions to gather in-depth feedback. All the questions were open-ended to allow participants to express their thoughts freely. Since it was crucial for us to understand how they organize events, interact with bars, and perceive new connections, we divided our script into several topics: event organization, bar selection, social interactions, and motivation.

Interview

We used Google Meet for the interviews—it was convenient and quick for everyone. Each conversation lasted about 30-40 minutes.

To streamline the process, we used tools like a 'note-taker' to capture key points.

• Introduction: Explaining what will happen.
• Working through the script and probing deeper if we found it valuable.
• Allowing the respondent to add anything they considered important at the end.”

Transcription

After the meetings, we used automated transcription tools (such as Otter.ai and the notes recorded by our note-taker) and then manually reviewed the transcripts to ensure nothing was missed. We gathered all pieces of information, grouped them by topic, and highlighted the key points.

Persona Creation

Based on the collected data, we began creating personas—fictional characters representing different types of users. We divided respondents into several groups, including those who frequently organize events and those who only join gatherings. After that, we created a user journey for each persona, allowing us to prioritize their issues and identify the areas that needed attention first.

| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |

Once we created these personas, we were able to move on to developing the first interface prototypes. This provided a foundation for designing solutions tailored to the real needs of our users.