GovExec Events

Designing and scaling an event management system

A summary of how we scaled and integrated an event management system for a growing media business.

Project ACTIVITY
2023 / 2024
Project Roles
UX Design, UI Design, Usability Testing, Usability Research

Background

In a year of acquisitions, our event management product faced a pivotal challenge. How could we scale to support an ever growing list of feature requirements and facilitate (sales and marketing estimated 120 events to us) an ever growing number of events? As the lead product designer, the following are those efforts to transform this tool into a scalable, credible, and efficient platform that became the foundation of our rapidly growing events business.

As product designer, I was responsible for maintaining and improving our in-house event management product experience and design; used primarily to enable teams to establish and manage their online meetings and event presence.

Some background, the company I worked for 'M', was acquired and by lets say, 'G'. Our team was combined with the G team as part of the acquisition. Our newly combined team would then need to integrate those seven additional businesses (mentioned above) into the company but specifically, integrated into the event management system.

Product Screenshots

The existing platforms were audited. This represents 1 of roughyl 14 different audits that would be completed.

Iteration was the name of the game here. We had straightforward requirements and utilized multiple rounds of review and iteration to get to our final solution.

Iteration was the name of the game here. We had straightforward requirements and utilized multiple rounds of review and iteration to get to our final solution.

Final designs implemented within the event template.

Product Screenshots

The existing platforms were audited. This represents 1 of roughyl 14 different audits that would be completed.

Iteration was the name of the game here. We had straightforward requirements and utilized multiple rounds of review and iteration to get to our final solution.

Final designs implemented within the event template.

Problem Statement

The product users cannot fulfill diverse event requests to execute different event types and needs to scale to support our growing business while prioritizing accessibility.

The product users cannot fulfill diverse event requests to execute different event types and needs to scale to support our growing business while prioritizing accessibility.

Strategy

Our strategy centered on identifying potential new components needed to support the introduction of new users to the platform. Ensuring a successful roll out was critical to establishing credibility with the newly acquired businesses. By incorporating input from these teams, we developed a comprehensive list of product requirements and features tailored to their needs.

PROJECT OBJECTIVES
In preparation for this initiative, we defined three primary objectives: 

  • Improve product efficiency while increasing product adoption

  • Strengthen and validate product credibility with newly integrated businesses

  • Evolve our product with a focus on scalability to support a fast growing events business

Mobile design lander

Strategy

Our strategy centered on identifying potential new components needed to support the introduction of new users to the platform. Ensuring a successful roll out was critical to establishing credibility with the newly acquired businesses. By incorporating input from these teams, we developed a comprehensive list of product requirements and features tailored to their needs.

PROJECT OBJECTIVES
In preparation for this initiative, we defined three primary objectives: 

  • Improve product efficiency while increasing product adoption

  • Strengthen and validate product credibility with newly integrated businesses

  • Evolve our product with a focus on scalability to support a fast growing events business

Mobile design lander

Execution

Using an iterative stakeholder focused design process, we designed approximately 20 components that have been successfully deployed and integrated into the product.

This project addressed both front and back-end interfaces, with additional time dedicated to collaborating with the product engineers to ensure designs aligned with and accommodated the unique requirements of each brand.

There were roughly 14 brands at minimum that had to be accounted for within the product.

Product Screenshots

Desktop event lander without branding and assets

Desktop event lander with branding and assets - Design is complete and finished at this stage.

Product Screenshots

Desktop event lander without branding and assets

Desktop event lander with branding and assets - Design is complete and finished at this stage.

Challenges

The biggest challenge in this initiative was the need to continuously reengage product stakeholders as we scaled to onboard multiple newly acquired businesses. Each new acquisition faced the decision to either remain with an external event management system or integrate with and contribute to the development of our internal product, requiring us to effectively demonstrate the value and advantages of our solution.

There were also scheduling and business reprioritization challenges. A few times business requirements would change that had us abandon components that were deemed out of scope. I always attempted to leverage the work we had accomplished and utilize what we had learned on the new problems or components but it was not fun with unfinished designs.

Results & Metrics

Results
& Metrics

Our team successfully designed and scaled an event management app, growing its user base from 25 to over 300 users and increasing annual events from 24 to more than 200. Over a two-year period, the software facilitated the production of over 500 events.

Additionally, we brought all major company events underneath a single platform, successfully integrating the various brands and businesses that had been acquired.

Skeleton design

Extra
Reading

As we developed and scaled the event product it became clear one of the biggest design limits was the large event registration form all users are required to complete to gain access to either the in-person event or online portion of the event. An ideal solution would have us reduce the number of fields and make the registration as short as possible.

Since we were not certain of the fields we could cut, audits were completed. And to no ones surprise, all the form fields were the most important information, nothing could be removed. I kid, but seriously we couldn't convince anyone to let their form data be moved off the form.

Since we could not reduce the number of items, we opted to explore converting the single form into a multi step form. This would at least give us the opportunity to capture portions of the data as the user steps through the form. We also had aspirations that it might reduce form failures as well.


Mobile agenda component example

Multi step forms were explored to reduce user registration time and failed registrations or partial registrations. We wanted to reduce the number of form inputs a registering attendee is presented to fill in and also increase the quality of lead data we are capturing. Audits were completed of the existing forms. User journeys were mapped out in various configurations.

To start to identify how we might regroup the form inputs we needed to understand the different users completing registration. We ultimately leveraged user personas to identify the different form sections.By identifying each attendee group we could better understand how each part of the form would be used by our sales and events teams.

I ran interviews and round table chats with the different individuals in our company that most interacted and had knowledge of the attendees. We needed to validate the user research we used to create the initial profiles against practical real world experience.

Some of our assumptions were just off.

Once the profiles were created we presented them to the different groups within the company.

I think the most notable unexpected use of the personas was with the events team, implemented them as part of their new employee onboarding process.

Multi step registration flow example

mobile multi form design example

mobile multi form design example


Extra
Reading

As we developed and scaled the event product it became clear one of the biggest design limits was the large event registration form all users are required to complete to gain access to either the in-person event or online portion of the event. An ideal solution would have us reduce the number of fields and make the registration as short as possible.

Since we were not certain of the fields we could cut, audits were completed. And to no ones surprise, all the form fields were the most important information, nothing could be removed. I kid, but seriously we couldn't convince anyone to let their form data be moved off the form.

Since we could not reduce the number of items, we opted to explore converting the single form into a multi step form. This would at least give us the opportunity to capture portions of the data as the user steps through the form. We also had aspirations that it might reduce form failures as well.


Mobile agenda component example

Multi step forms were explored to reduce user registration time and failed registrations or partial registrations. We wanted to reduce the number of form inputs a registering attendee is presented to fill in and also increase the quality of lead data we are capturing. Audits were completed of the existing forms. User journeys were mapped out in various configurations.

To start to identify how we might regroup the form inputs we needed to understand the different users completing registration. We ultimately leveraged user personas to identify the different form sections.By identifying each attendee group we could better understand how each part of the form would be used by our sales and events teams.

I ran interviews and round table chats with the different individuals in our company that most interacted and had knowledge of the attendees. We needed to validate the user research we used to create the initial profiles against practical real world experience.

Some of our assumptions were just off.

Once the profiles were created we presented them to the different groups within the company.

I think the most notable unexpected use of the personas was with the events team, implemented them as part of their new employee onboarding process.

Multi step registration flow example

mobile multi form design example

mobile multi form design example


Thanks for checking out my site.

Thanks for checking out my site.

Thanks for checking out my site.

An Em Kay P Website. 2025

An Em Kay P Website. 2025

An Em Kay P Website. 2025