Brodden: Case Study (Event Planning and Promotion Application)

Problem/Task:

How can we create an event planning app that only focuses on art, food, and music events. These three artistic avenues rise above language, class, religion, and gender differences. We are tasked with creating an app that’s user-generated and focuses on cultivating artistic expression, and real-life experiences that bring us together and broaden our cultural awareness.

Testing and Research Method:
Design Sprint

Sprint Questions

Some of the main obstacles faced in this phase of the design sprint were focusing our efforts on practical requirements for an application that address two user types. We wanted to address what that would look like for both users, and if this application could separate itself from some of the competitive markets while addressing the needs intended for both user types.

Key Concerns

1. One of the main requirements was a 30-question questionnaire for the onboarding process. How can we come up with a creative way so this isn’t daunting to where users give up on the onboarding process?

2. Can offer a unique experience that Timeout, Eventbrite, and apps like Meetup can’t or haven’t yet?

3. What apps does our user use currently to promote and how can we match some of these functions and possibly improve and streamline the experience?

4. What are the benefits and key features that engage each user type (tastemaker, general user)?

5. Is promoting free events a sticking point or should we implement monetary features like ticket sales?

6. Are we limiting ourselves by focusing on artist community social events planning?

Competitive Analysis Key Findings

timeoutlogo.png
eventbritelogo.jpg
meetup.png

Pros

  1. Competitor’s general market is far too open.

  2. Focusing on Culinary, Music, and Art can trim this market and give us a unique specialized approach.

  3. Live streaming real-time experiences through the users who attend events could create a unique community experience.

  4. Simplifying our navigation and providing consistency could provide users with a better overall experience.

  5. An event promotional tool that helps tastemakers manage and create content could help separate the app from competitors.

  6. Users could attract followers, become influencers, and help tastemakers promote their events and community

Cons:

  1. The 30 Question onboarding process in the project brief is far more demanding than any researched competitors. Trimming down the questions during the onboarding process will speed up the onboarding process.

  2. We might have to complete another round of iteration and research focused on encouraging users to engage in online experiences after attending events offline.

  3. Simple review system for events might place limits on communities. This app should engage users, like Facebook, Twitter, and LinkedIn.

  4. Another iteration focused on inclusive standards might need to be conducted to explore these variables.

User Personas

This phase was critical before we could attempt to develop a map for two different user types.

  1. Users would need a platform that would allow them to drill down on local events, and track their unique interests and what’s happening around them. The ability to possibly interact with like-minded taste consumers might be another direction of cultivating communities.

  2. Tastemakers would need an application that would serve as a promotional tool. The platform should be able to track and manage multiple events and RSVP attendance and actual attendance. They would also need the ability to cultivate a community around their specific niche.

User

Tastemaker

Goals Icon.png

Long Term Goal

In 2 years, we want to be the go-to application for events promoting music, art, and culinary events in every major city in the US.

How Might We?

During our “How Might We” exercise we focus on empathizing and defining the approaches to our application. During our ideatIons, the brainstorming and writing exercises would help us gain greater insight before creating our mapping and lay some foundations for approaching these questions. 

Mapping

Mapping allows me to see how our basic user maps would look. This also gave us the opportunity to apply the how might we questions to the user experience. This gives us the ability to reference if we are answering our initial concerns during the mapping phase of our sprint.

Screen Shot 2020-06-30 at 10.59.30 PM.png

MVP (Minimal Viable Product)

  • App store accessible (android)

  • Onboarding registration for users (customer and tastemaker).

  • Tastemaker dashboard profile

  • Customer dashboard profile

  • Event publishing system

  • Event Editing Tool

  • Calendar system

  • social interactive mediums (stand-alone social media platforms)

  • Event change notification and update system.

  • Customer Feedback chat or form system.

Customer Feedback systems: We might want to categorize feedback or rank concerns so we understand the key pain points when using the application for future builds and protocols.

Low Fidelity Wireframes

The low-fidelity wireframes were a way for me to organize and test my ideas. Using a wireframe template allow me to spend more time testing different layout, and content approaches. In the end, the focus came down to connecting and fostering an interactive community between all the potential users.

low fidelity wf.png

High Fidelity Design (Android)

  1. Event summary block

  2. Add dates and check who already RSVP.

  3. Live stream your entire event or sections of your itinerary.

  4. Add sections of event itinerary to your calendar and share event on other social media platforms.

Event Page

Event_filter.jpg
Eventlisting.png
EventPage.jpg
Event_profile.jpg
Event_Calendar.jpg
Previous
Previous

Paws to Pals: Case Study

Next
Next

Consultation and Design