Event platform management system
Modernising a legacy platform
Defining our core principles and future aspirations
My role
As a Product Designer, I joined an ongoing project in a fast-paced, agile environment, working closely with the Product and Business teams. I focused on making the experience more intuitive within existing constraints. Collaborating across teams, we uncovered key insights that guided design decisions. My deep understanding of the platform helped ensure our new feature fit seamlessly with existing functions.
đ€ Problem
The existing platform was difficult to use, and its content was poorly organised, limiting growth and innovation.
đ§ Objective
Redesign the outdated platform from scratch, incorporating existing features for the MVP, and ensure it meets higher standards such as UX best practices and accessibility.
The users and their roles
Super admins
B2B user: These users have full access to multiple features with a paid license. They are responsible for managing all their corporate events.
Admin user
B2B user: Assists the Super Admin user by providing support with a free license, but they have restricted and limited access to the platform.
Support
Intenal user: they provide support as admin users to clients in planning and managing events when challenges arise.
Attendee
B2B2C user: These are attendees who participate in the event, engaging in surveys and live polls.
Plus ones
B2B2C user: They are guests of the attendee and can only attend the event. They do not participate in live polls or surveys.
We interviewed 4 users for each role and and here are the three key takeaways
Studied the exiting product
I dedicated an entire week to using the product, gaining expertise in its functionalities and identifying challenges.
Researches & breinstorming
Once I understood the platform, I organised and documented my findings, asking numerous questions to brainstorm ideas and validate my design suggestions.
Design & validation
I collaborated with the team to develop solutions, ensuring expectations and requirements were aligned. We validated these through design reviews and real user testing.
Reviewing the exiting product
The dashboard on the right felt overwhelming at first it was hard to tell which elements were most important because there wasnât a clear hierarchy. Features were scattered everywhere, added over time based on client requests without a scalable plan, which made the product feel messy and chaotic.
Studyng the exiting structure
I documented the existing product in detail, creating site maps and infrastructure diagrams to understand every CTA and user flow. This helped identify pain points and informed the redesign with the right structure. It was challenging, as I needed to demonstrate to the product team why making significant changes was worth it even if it meant existing users would have to learn a new way of using the platform.
We conducted a workshop with five members of the support team to gather insights.
We found the support team was frustrated with malfunctioning tools, often having to find workarounds or even manually code solutions. Some features were time-consuming but straightforward to improve, while others were much more complex. For example, one key request was a website builder something I knew from experience would be a significant challenge to implement properly.
I focused on researching each feature thoroughly.
Some features were more complex than others, often presenting both UX and development challenges. It wasnât just about making things look nice it was about solving intricate problems with smart, scalable solutions. One example was the form builder, which needed to handle conditional logic while remaining flexible and performant, ensuring it could scale without breaking or limiting future functionality.
.png)
I created mock-up designs based on everything I learned from my research.
I designed screens and explored multiple solutions, ensuring each met both user needs and business requirements. We conducted user testing with the internal team and real users through an online service to observe pain points and areas of struggle. To ensure consistency and smooth collaboration with developers, I created a comprehensive design system. This also helped guarantee the product was user-friendly, accessible, and aligned with established UX standards.
.png)
Image Gallery
Extra screens for the form application builder.
