Athlos

Role / Services

Product Marketing

Role / Services

Product Marketing

Role / Services

Product Marketing

Year

2023

Year

2023

Year

2023

Team

Zasha Coté

Marco M.

Lawrence W.

Team

Zasha Coté

Marco M.

Lawrence W.

Team

Zasha Coté

Marco M.

Lawrence W.

Brief

Athlos Travel (former Egruppa) is a tool that simplifies the booking and management process for groups traveling to sports events. It focuses on federated and not federated clubs' tournaments and competitions, and school’s sports-oriented trips.


Challenge

Until now, Athlos couldn't provide a digital experience for end-to-end bookings that catered to two distinct user groups: sports clubs or federate associations in need to travel for competitions and schools seeking to organize sport-oriented getaways.

The previous flow required the user to switch between multiple channel touchpoints and the booking time could take weeks.

My role as a Product Designer was to give visibility to the different user journeys and to offer a solution that would reduce the booking time and integrate the communications user-business.


Solution

To develop our first version of the product, we started with the hypothesis:

By providing group trip organizers with a booking experience similar to what individual trip organizers are used to, it is more likely that our product will achieve top-of-mind awareness among these users.

This will contribute to Egruppa gaining recognition, attracting new users, and becoming the primary choice for organizing sports trips.

This way we reduced the booking time by +80%. And we saved more than 1 hour a day to the BDRs.

Process

What did we do?

First we had an interview with the CEO and CTO of Athlos to understand the business requirements.

Then we analyzed existing sports travel booking platforms and general travel sites to identify market gaps and best practices.

And last, but not least, we conducted 6 interviews and a survey with club managers, Athlos clients and school administrators and HR professionals to understand their needs and pain points.

-> As a result we identified key features such as bulk booking, customizable travel packages, and shared payment method that we would add to the roadmap.

Why did we do it?

We followed a mobile-first approach. First we created low-fidelity wireframes to visualise the structure and flow of the website, we made sure that this new user flow was aligned with user needs.

We continued by creating high-fidelity prototypes. We designed the UI in line with the current style and branding of Athlos. We only made some subtle changes to accomplish consistency along the elements.

We decided not to make big changes in the UI to keep a cohesive brand experience. Because in two weeks of work, we wouldn't have time to rebrand.

How did we do it?

Due the lack of time we went for guerrilla testing with employees and colleagues, and also multiple A/B for small but important design decisions. This way we quickly identified main usability issues, iterated, and gather feedback on the design.

Once sent to deployment we made sure to document the whole process and results in order to keep the process iterative.

Process

What did we do?

First we had an interview with the CEO and CTO of Athlos to understand the business requirements.

Then we analyzed existing sports travel booking platforms and general travel sites to identify market gaps and best practices.

And last, but not least, we conducted 6 interviews and a survey with club managers, Athlos clients and school administrators and HR professionals to understand their needs and pain points.

-> As a result we identified key features such as bulk booking, customizable travel packages, and shared payment method that we would add to the roadmap.

Why did we do it?

We followed a mobile-first approach. First we created low-fidelity wireframes to visualise the structure and flow of the website, we made sure that this new user flow was aligned with user needs.

We continued by creating high-fidelity prototypes. We designed the UI in line with the current style and branding of Athlos. We only made some subtle changes to accomplish consistency along the elements.

We decided not to make big changes in the UI to keep a cohesive brand experience. Because in two weeks of work, we wouldn't have time to rebrand.

How did we do it?

Due the lack of time we went for guerrilla testing with employees and colleagues, and also multiple A/B for small but important design decisions. This way we quickly identified main usability issues, iterated, and gather feedback on the design.

Once sent to deployment we made sure to document the whole process and results in order to keep the process iterative.

Process

What did we do?

First we had an interview with the CEO and CTO of Athlos to understand the business requirements.

Then we analyzed existing sports travel booking platforms and general travel sites to identify market gaps and best practices.

And last, but not least, we conducted 6 interviews and a survey with club managers, Athlos clients and school administrators and HR professionals to understand their needs and pain points.

-> As a result we identified key features such as bulk booking, customizable travel packages, and shared payment method that we would add to the roadmap.

Why did we do it?

We followed a mobile-first approach. First we created low-fidelity wireframes to visualise the structure and flow of the website, we made sure that this new user flow was aligned with user needs.

We continued by creating high-fidelity prototypes. We designed the UI in line with the current style and branding of Athlos. We only made some subtle changes to accomplish consistency along the elements.

We decided not to make big changes in the UI to keep a cohesive brand experience. Because in two weeks of work, we wouldn't have time to rebrand.

How did we do it?

Due the lack of time we went for guerrilla testing with employees and colleagues, and also multiple A/B for small but important design decisions. This way we quickly identified main usability issues, iterated, and gather feedback on the design.

Once sent to deployment we made sure to document the whole process and results in order to keep the process iterative.

Concept and Development

Screen 1
Screen 2
Screen 3

Project Roadmap

Roadmap