Eventify is a user-friendly event planning tool designed to assist in seamlessly orchestrating mid-scale social gatherings.
View PrototypeYoung adults and millennials newer to trying to bring various social groups of people together for an event and making sure everything goes as planned
8 Months | September - May 2024
Role: UX Designer | UX Researcher | Developer
User Interviews Wireframe + Prototype Final Concept pitch
Mid-scale social events lack the resources and preparation guidance given to their larger/smaller counterparts. It is easy to often get lost in the planning process. Poor time and detail management cause people to feel overwhelmed, frustrated and lead to more event day problems.
How might we create a tool to give users a roadmap and guide for planning midscale events?
Productivity isn't always tied to mindfulness and self-reflection and giving yourself grace to focus but also to take breaks.
Lack of knowledge, preparation, and guidance coupled with poor time management often cause users' frustration and lead to more event day problems
Event tool to keep track of guests, event planning tasks and tips for successful planning. A new innovative way of planning for midscale events. It eliminates the hassle of figuring out each step on your own.
It’s important: the ability to track and plan in the same space.
Creating a separate site map for the Eventify MVP and prototype product was crucial. I knew the MVP would be the tips generator and the prototype in Figma would be fully developed with many flow and connections.
Site Map - MVP
Creating the MVP site map was simple. The two pages wouldn’t have an output besides the ones already there. The about page would be primarily text with no external connections. The main page is how the user would interact with the tip generator.
Site Map - Eventify Prototype
Creating the prototype product site map allowed me to determine the primary and secondary page levels, viewer state and actions to be completed on the pages. As the prototype functions primarily on user generated content, the different page states produced different actions.
Starting with the optimal and alternate paths for each event task. The tasks to complete are
MVP
Eventify Prototype
Knowing that more user tasks flows may come about during the prototyping phase, this document will most likely be updated later on.
Here is a glimpse at the initial draft of the research plan. Using agile methodologies, I am going to have to design, prototype, and research at the same time.
User Demographic Survey
Things I kept in mind while creating the user survey
While going over some survey data and looking for ways to edit my prototype, I began developing how I would gather user information about their event planning process. The flow for creating an event in the prototype began to take shape.
The next step in my research process is gathering information from my users in one-on one interviews. I hope this interview will help me gain a better understanding about the event process and what information is key for guests to know and planners to provide.
Here are some highlights and new idea recommendations based off the survey results.
Users want everything in one place. Some of the initial highlights to the product concept was combining many different functionalities of other applications into one.
Word of mouth is typically how many users find new tools/platforms to use. The idea of adding a “Recommend” Feature or button can help with application promotion. This could be as simple as adding this under the user account. Allows a user to recommend this platform for their friends to use.
Guest Users versus account users. The process/platform for a guest user will be significantly different than a planner
Design recommendations
Flows we hope to enhance with the interviews
“I want one place where I can keep all of my lists, all of my things that I need to happen, all the dates where things need to happen. And then multiple people can access it, and then easy for me. And it's easy for the guests” - P1
“for an event planning tool I would need for it to be….quick and easy. I don't have enough time in my own day to really manage whatever little calendar I've already like somehow managed to make work for me” - P2
Navigation Redesign
Adding multiple new features will require the navigation design to change.
We don’t want users to get lost in the system. So adding consistent indicators of system status is important.
Options
System design
System can have a modular design for planners to add sections to their event dashboard view
Main flow - Anna is a superuser of the system. She is every group, page and event creates a new group (The Spot Restaurant) and event (The spot grand opening). This view goes through all sections and capabilities of the system.
Alternate - Jocelyn Davis - a new user that goes through the process of creating events and joining a group. She does not have access to everything right away. through this pov you discover the system.
Alternate - Devin Jones - A guest user. Devin does not have an account but has been invited to
Creating the product branding was important establishing the identity and visual style. This allowed me to set the initial aspects of branding that would later tie into future product marketing materials.
This created the identity of Eventify. This also allowed me to set some of the initial UI elements of the product. While many of these were from my initial sketches, it “broke the ice” of jumping into Figma to start designing.
These wires were created based off my initial sketches
Adding the gradient, colors and branding. This page is what I’m going to use as inspiration for the rest of the product design.
I began changing the prototype flow processes and UI to incorporate some changes from the research. Based on the design recommendations above, some sketches were created before I jumped into designing in Figma.
Before finalizing the design and prortpye for the pitch, Computing day provided an additional opportunity to conduct usability testing. Here are the voices/recults from the session.
The prototype also began to increase in fidelity and flow interactions. Editing flows for continuity, polishing the prototype and making finishing edits
1. Event Dashboard
The event dashboard serves as a home base for the user planning an event. Event helping hands also have access to the dashboard. While overwhelming, the dashboard is meant to be customizable for what an event will need. Each widget serves a specific purpose and thus having them appear on the dashboard after event creation allows the user to start inputing information.
2. Add Widget Function
The importance of the “Add widget” functionality is key to the customizable nature of the dashboard. A dinner party may need a “Potluck” widget while a birthday party may not. Having the ability to Add a widget to your dashboard lets the user enhance their planning experience. While some widgets like the tasks and countdown aren’t removable, they allow the user to customize further within them.
3. Create event flow
Creating an event was previously a 5 step process. Through an iteration, I added an extra step. The new final step asks the user how much help they want with the event. This would later help the system give them better tips, know how frequent to check in and provide less guidance on how to use the dashboard. The only circumstance where the user wouldn’t receive any guidance is if they select “I’ve got this! I don’t need nay help”. In design it’s important to give users an “out” but if they wanted help, the Tips is always present.
The main concern with this version of the prototype was making sure the connections worked out. My goal for the prototype was to have all the pages connected and create alternate views.
