Catalist

Transforming the way people manage events

In a nutshell

Ever organised an event?

Then you would know what a challenging task it is! The purpose of this app is to support event organisers  with the logistical aspects of event management so that they can focus on curating memorable experiences for people.

Yes, but how does Catalist work?

As a gateway between multiple teams working on an event and by providing them a platform for hassle free communication so them can work to achieve their goals on time and in an efficient way.
Who is it for?

Target Group

This app was created to facilitate student councils in universities that are responsible for organising events. I worked with them to briefly understand what challenges they face, to then create an app that streamlines the process of event organisation and management.
DETAILS

Role

  • UI Designer (Major)
  • UX Designer (Minor)

Key Responsibilities

  • Research (Interviews)
  • Interface Design
  • Library Creation
  • Prototyping

Login and Create Event

Add Tasks Details

the frustrations

Some Insights

After a couple of interviews with university event organisers, contractors, and independent teams, I collected some of their pain points in the event management journey. This helped in identifying key features for the app.

1.

Too many Cooks

Too many people involved in the process, difficult for me to keep track of all of them and what they are doing.

2.

Water over the Bridge

I only find out if there is a problem with a task if I inquire myself. A lot of times people reporting issues to me do not get a hang of me until it is too late.

3.

Where can I find that?

Visual and Media content is rarely organised. If I have to show the latest status of a stage for example, it will take forever for me to find it.

4.

Scattered Resources

It's a bit hard to communicate via messages or WhatsApp groups, who is responsible for what, especially when a task arises spontaneously.
the frustrations

Information Architecture

User flow was created to define taxonomy through the grouping of related content. It was an important step as it helped me ensure that the content is where users would expect to find it.

Initial Screens

I created lo-fi wireframes of the app first to visualise the user flow and to test the important user actions. Additionally, decisions about the final components and interactions, depended on the feedback from the development team upon validation

Visual Guide

Setting up a style guide in the initial stages of made it easy to maintain and update UI elements in the high fidelity screens.

What Does the User See?

Once the style guide and user flows were approved, it was time to put the two together and create high-fidelity screens.

Splash Screen & Log In

The splash screen is the first screen which pops up when the user launches the app. The log in process is what follows the splash screen which is kept simple.

Events

After signing up the user lands onto the events screen which lists all the events the user is managing. On this screen the user has an option to add a new event or navigate to any event to view the activities.

Teams & Activity Board

When the user navigates into a specific event they can view the activities of each team and track their progress. There is a board for each team which displays the tasks, requests and alerts assigned to that team.

Activity Details

By clicking on the activity the user can further expand it to add more details to it or track the progress of that activity. The user has the option to comment on the acitvity or change the activity status by selecting from predefined statuses.
Final Thoughts

Reflection on the Process

Catalist showed me how important good communication is for planning events. This project helped me improve my sprint research skills and understanding of how to identify the most important aspects of a project to expedite the onboarding process for myself as a UI designer.

The Focus on Interface Design

Designing Catalist's UI was especially rewarding. I focused on creating a consistent experience by developing detailed style guides and UI libraries. I think what would've made the process faster, was to use an existing design system