A lot of events they cater to take place internationally thus the attendees would generally fly down and book a hotel. Each of these would have to be booked separately via different services by the user.
Having worked on the MVP for the front end design during my internship helped me gauge what the event management system would require.
I researched about travel and hotel packages from travel companies to know the requirements to create a package.
The internal interviews with the operations team lead to the user journeys for package inventory management.
To create a package - a compilation of almost everything you need to enjoy your event hassle free. Along with my product manager, I drafted the information architecture based on our research and the customer end packages previously designed.
I wanted to include functionality such that it can be most customisable:
- Create a package: User is able to create packages for all events.
- Edit a package: user should be able to make changed to an already saved package.
- Change status of the package: as you change the status of the package, the changes are reflected on the customer site. The user decides when to keep the packages created to be live or expired etc.
- Edit all the data: For the Super Admin to be able to pick the tickets available and edit all the available data in the system.
Since it's a package for events exclusively hosted on AirAsia REdTix, tickets in a package are compulsory. A package can be created with addition of flights, hotels, merchandise which are optional.
User can set the time and the date when the packages go live. They can choose whether to display the package on the live site or not.
The destination will be set to that of the venue of the event. I cannot be changed.
Other packages would be hotel, merchandise and additional perks
The user can view and manage the pages through the dashboard
The packages tab on the customer's end looks like this:
There were multiple things that were to be included in the packages such as flights, tickets, hotels, merchants. each of them have a lot of details to be included. Creating a flow that can include all the details whilst not making it tedious for a user to create. Not knowing the logistics of the flights and hotels caused re-iteration of design strategy. The event management system is a complex system which with the help of my design manager I understood it and created more solutions for the event management system. It was a complex user journey and overthinking didn’t help.
We were able to provide a one stop solution for all event goers. This was implemented to multiple events such as Ultra Singapore, Rugby World Cup - Japan.
While ideating user flows for this project, I would overthink a lot. That would stress me out. On one such occasion, my design manager told me to calm myself and that overthinking in this case had led to multiple plausible user journeys but to get to the right ones I need to calmly access my thoughts, consider all scenarios and create a solution.