Inspiration

While attending events in my organization, I found that events are organized manually. That person must do each task by phone call or through mails such as taking approvals from big guys (higher management people) for the event, services, trophies etc., find service providers and keep track of services manually on pen-paper or through any other way like notes or spreadsheet or excel sheet.

But which is very scattered info every other people will have, who is involving in event organization. Which will sometimes be led into delay or sometimes cancellation on not proper organization for the event.

So, I found this as an interesting challenge to design an app to create and manage event where all people in organization will have access to app to their respective task, making easier and enjoyable organizing an event.

The Challenge

How might we create an engaging and intuitive experience, so that creating and managing event will be hastle free and enjoyable job for everyone.

Problem Defined

I wanted to have some data to work with, so I did short interviews with 5 people involves in organizing event in team or at organization level regularly. This is the summary:

• All people said the process took too much of their time and is very complicated process.
• 4 people said they had problems remembering to follow-up mails/person, event reports.
• 3 people said its very time-consuming process and so at the end we fail to organize good event.
• 2 people said they didn’t know where to find services, whom and how to reach for event approvals.

While these are small numbers, it was more than enough for me and my personal project.

User Flow

To start with onboarding process I have to start with intial expectations from the app. So I created a user flow of creating an event.

User Flow for Creating Event View Full

• Anybody in organization will create and manage event and small level or higher level respective to their role in organization.
• That person will decide to give admin access in event team.
• Can create new event or reuse historical templates to save time.
• Created event will go to the event approver to approve event.
• Once received approval for event, admin will contact to service provider, take quotes from different service providers. Keep track of services.
• Admin will manage events and attendees, participants and each activity of the events.
• Everybody with access will update their tasks, can see events current status.
• Every event notification will be displayed on dashboard and system notification will send through Email.
• If any change in event (date/time/venue) will get notified to respective team from the same phase.

Understanding Users

Various segments across organization who involves in creating an event, by age groups, genders and people from different demographics.

I outlined which tasks is performed by which users. This helped to create user centric noun architecture and decide navigation flow.

Persona

I went for 2 different personas (who will organize event) among all users having different age group, designation and character traits. These personas mainly focus on creating and managing event.

Fictional characters created to represents user type.

Primary Noun Architecture

Primary nouns are the ‘things’ in application users can take action on or manipulate. From research above I jotted down primary nouns, its views, actions and attributes. It helped me decides number of pages, which format and how it will display.

Navigation Flow Diagram

From above research created navigation flow diagram for each user profile.

Information Architecture

From above Primary Noun Architecture and Navigation Flow Diagram I created Information Architecture of the site.

Information Architecture View Full

Lo-Fi Prototype

To clearly express and refine my ideas further, I created a low fidelity prototype

Visual Design

Learnings

• 'Empathy' is important while designing app for the user. It allows us to dig deep into our understanding of the user and create solutions that will not only solve a need, but effectively improve our users’ lives by removing unnecessary pain or friction
• Take small steps, because big changes can not be brought overnight, especially not just by an application alone. Accordingly, develop more strategically meaningful and realistically applicable tools that steer in the intended direction.