Glisser started when the founder realised that whilst a lot of his marketing budget was being allocated to events, it was difficult to measure whether that money was actually being well spent. Event effectiveness was still being measured based on attendee numbers, and calculated by how many unused name badges were left on the desk at the end of the room. They were being assessed using paper feedback forms because nobody filled in post event surveys.
Glisser’s founder calculated that inputting the data from the paper feedback forms into the company CRM system would take his team almost 400 days! Whilst at the same time £1,000s were being spent printing copies of slide decks to leave on seats for attendees, only for them to be thrown away when last minute changes were made to the presentation.
It turns out he wasn’t alone. Forrester Research indicates that business-to-business companies spend nearly a quarter of their marketing budget on events. Despite big budgets, very little is being spent measuring, analysing and proving event ROI. The aim of this project was to collect and use event data to give event managers a way to prove that their events are successful.
As the Head of Design at Glisser, the complete design lifecycle was my responsibility, from gathering requirements directly from clients, to helping with front-end testing. I worked as the sole designer in a team of five developers, as well as a testing team in Kharkiv, Ukraine. Without a Product Manager I was also expected to take on responsibility for documentation.
For wireframing and prototyping I used Sketch and Adobe XD. The platform was built using Node.js with Web Sockets for the backend, Angular 6 with TypeScript, SCSS, and Bootstrap 4 for the frontend.