Background

Eventbrite organizers depended on a legacy, brittle, and outdated dashboard implementation. It was based on using an old, proprietary Python templating and ORM system. In practice, its code used a large set of "global" variables that were hard to track and used directly in the template files.

Here is what it looked like before:

The result was a page with a high impact and traffic numbers, but nobody wanted to touch, update, or modify it slightly. It was a multi-state and multi-variable UI problem that wasn't easily testable.

Role

As the Organizer Reporting team, this page became part of our ownership. I proposed doing a series of iterative improvements over the dashboard, avoiding extensive rewrites and documenting and refactoring its logic. It was clear that it was a tricky one, but the impact was evident.

I hypothesized that, by cleaning up the look and feel of the dashboard, our event organizers would increase their confidence in trust in the event performance tracking experience.

Results

We increased dashboard visits by 15%, receiving overwhelmingly positive feedback from Product and event creators (via account managers).

I extracted logic out of the templates and created a testable vanilla JavaScript module that could load our Britecharts charts and get inputted most of the information necessary. These refactorings made the future maintenance of the page a lot less costly while allowing us to evolve the product.