PLATFORM
TIMELINE
TEAM
Whova already provided organizers with detailed reports on registration, attendee demographics, and engagement. But for organizers running recurring events, comparing performance meant navigating between different event dashboards, exporting data, and building comparisons manually.
Even for a single event, organizers had to navigate multiple reports to find the information they needed. Comparing events added another layer of manual work, especially when preparing performance report for leadership.
EVENT STATS ACROSS DIFFERENT FEATURES
As I worked through the requirements, I saw three layers of opportunity. Together, these would make Whova more valuable throughout the recurring event lifecycle.
Existing behavior
New Value
What was worth comparing in the first release?
With data spread across the platform, bringing everything into one report wasn't realistic or necessarily useful. Working with the PM, I prioritized 10+ core metrics using organizer interviews, existing requirements, and frequently exported reports.
We focused on three areas:
01
Are tickets selling better?
Gross/net sales
Tickets, add-ons sold
Whova contributed revenue
Registration sources
02
Attendee demographics
Who is coming?
Unique attendees
Returning attendees
Attendee categories
Industries
Affiliations
Locations
03
Event engagement
Are attendees participating more?
Session RSVPs vs. check-ins
Session feedback
Before exploring layouts, I aligned with engineering on what we could realistically support. These constraints pushed me toward a more focused, scalable reporting experience.
The initial requirement was to show all metrics on one page. But once I mapped everything into Whova's admin layout, the report became difficult to navigate. Engineering also confirmed that loading all metrics at once would be costly.
I explored three directions:
DATA PRESENTATION
FINAL SOLUTION
An overview with focused tabs.
01
At-a-glance overview:
Surface key metrics across all three categories, with direct links to each tab.
02
Focused tabs:
Keep detailed comparisons easy to navigate without loading everything at once.
Organizers try to turn the comparison into a clear story they can share.
How might we make the comparison easier to report?
Comparing numbers was only part of the job. Organizers still had to identify the key takeaways and put together reports to share with others.
DATA INSIGHTS
Highlighting what changed
I added lightweight insights to help organizers spot meaningful differences without digging through every chart. Since we couldn't always tell why something changed, I kept the insights factual rather than making assumptions.
REPORT EXPORT
Making reporting accessible throughout the event
Generating full PDFs during an event would add significant backend load. After discussing the constraint with engineering, I kept export available through two alternatives rather than disabling it:
Need something now? Download individual charts.
Need the full report? Request the finalized PDF by email after the event.
Sometimes the data pointed to problems Whova already had solutions for. I wanted to connect organizers with those features without turning the report into a promotional surface.
I established three principles for recommendations:
Contextual: Place suggestions near the relevant metric.
Relevant: Don't recommend features already in use.
Focused: Recommend one useful action at a time.
DESIGNING FOR THE EVENT LIFECYCLE
I mapped when different metrics become available and what organizers need at each stage. This helped me decide when a recommendation would actually be useful.
CUSTOMER REQUEST
"The insights about app adoption, doc views, personal messaging, etc.↵
I have to manually create this for my CEO after every event."
"Would love way more information in this report — Are our attendees sending more messages? Are our exhibitors and sponsors getting more impressions than the year before? Impact of passport contest?"
"I would like to see more than two events compared to each other. Four or more would be great so we can make a trend line."
"Percent of attendees who used the event app".
" Registered vs. attended."






















