Engageathon

A mobile application to help organizations put together events, and reward users for attending these events.

Iterations

Problem Statement

Scope

Tools

Pain points

How can event organizers reward engagement with attendees?

To promote community involvement, Engageathon aims to connect organizations and audiences.

Project Scope

Role

As Project Manager it was my responsibility to take charge on the "whys" and "hows" of our team's decisions. In my additional role as the Design Lead I planned the UI interface, gathered feedback with user research, and applied this research to high fidelity designs.

Timeline

Together our entire team needed to meet a 8 week deadline to deliver the final product. To meet such a deadline, it was imperative to meet regularly and check in with each other on our progress in every step along the way.

Team

Our project had four designers, four people in development, five people in marketing, and three people working on data. Altogether my team comprised of twelve people.

Tools

My four preferred tools were Adobe Photoshop to create raster designs, Adobe Illustrator to create vector designs, Figma to compile all our designs into screens, and Miro to draft the team's decisions and plans.

Tools

Style guide

Our style guide gave our team a visual direction.

Roadmap

Our week-by-week roadmap structure was used to help our team stay on track based upon department assignments.

Flow chart

This chart was used to help the team understand the flow between screens and how the flow is impacted by user decisions.

Persona

Our persona was used to guide user-focused decisions.

Pain points

The colors

The Engageathon project struggled for days to decide on a color palette. User research was conducted to gather feedback on different color palettes to be cross referenced by our marketing team across color trends in the mobile app market. In the end, we decided to go with blue and yellow because we felt the opposing hues are the most appealing and visually digestible.

Naming users

The Engageathon team was initially divided on how to name our users. Some people felt that "attendee" was the most accurate term. Others felt that "ENGAGEr" was a more active term that could grab attention. After testing, users responded more favorably to the "Engager" term with standard capitalization, and agreed that it better captured the essence of the project.

List of causes

The team struggled to decide on how we would organize the list of causes and passions. Early concepts implemented a box grid system with logos, as it was believed this would be the most visually appealing way to deliver visual information to the user. In our user testing we ran into issues where this was not intuitive. The team decided to go with a sorted list that implemented a hierarchy of categories.

Impressed? Look over the iterations again!

Review the iterations