GamePlan

GamePlan is a one-stop shop for planning, sharing, and managing meetups with groups.

Duration
10 Weeks
Oct 2019 - Dec 2019
My role
UX design
Interaction design
Prototype
Visual design
Tools
Figma
Adobe AI
Team
Shian Yang
Aaron Jenkins
Meg Delaney
Design Challenge
How might we make ongoing event scheduling, managing and communication more efficient for groups?
Introduction
In this project, I led interaction design and visual design. I created high-fidelity interfaces, designed micro-interaction, animated prototypes, as well as iterations. I also built up the visual system, including mood board, color theme, and fonts.

Problem
People are struggling to manage their schedules from different platforms, especially for group events with many participants. For the event or activity host, it's hard to collect every participant's availability and make an agreement to satisfy most of them.

It also hard to keep every group member to keep updating if there is anything that has to change the activity. People need to access multiple applications and services to arrange events, and that these processes consumed too much time.

Opportunities
Sometimes, it's more valuable to improve existing user experiences instead of generating new experiences.

This is a project where I showed a close understanding of users’ needs. It could help to make tangible improvements for the overall experience and simplify the complexity, even for a common problem.

Key features

Review Activity and Vote
Ongoing events section shows upcoming events and able to review details by clicking.
Participants can vote for the unlocked options to let the host better understand majority preference.
User Needs
The host want to collect participants' availability and try to reach everyone's preference and keep them on the same page.
Participants need a better way to communicate with the host to decide event's details like date, time and location.
Take Tasks or Add an Task
Participants can take their preferred tasks.
Participants can create new tasks based on their understanding of events needs.
User Needs
Users express frustration with separately tracking individual tasks through emails, lists and spreadsheets when planning and managing events.
Create an Event
The host can lock or Unlock options, and leave flexible options to vote by participants.
Add tasks for participants to take.
Add all the event details to let participants better access information.
User Needs
Users want to have a platform for them to show all the event details and be able to chat with participants.
View/Join Group Events and Chat with the Group
Users can view/join different groups linked with different platforms.
Users can save, review the upcoming events and join any of them.
User Needs
Users want to be able to see all events from different groups.

research


To understand existing frustrations and technical barriers to managing group events, we conducted several in-person interviews to better understand user's pain points and needs.

To address our design question, we wanted to know which existing tools and processes members of groups or teams currently used to schedule, manage and update events.
In-person interviews
I used semi-structured interviews to understand how users currently schedule activities and group events with teams and friends using existing tools.

I also used a combination of 5 Whys and open-ended questions to identify specific pain points that created extra steps when coordinating group events.
Findings

            1.

Different apps were used for specific tasks.
“Well, I normally use Google calendar for work, WeChat for social events as I can chat with my team” —— Participant 1

            2.

Challenging to make plans with more than six friends and keep them updated as plans changed.
“When you need to deal with a group, you know, it's pretty hard to let them know the event changed any details.” —— Participant 3

            3.

Being able to manage all personal and work events on one platform would enable them to plan better.
“Ah... I need to check different platforms to check my availability." —— Participant 2
Competitive Product Survey
We performed a competitive product survey to understand how existing products compared to our proposed product, and document gaps in those systems that contribute to the user pain points identified above.

We chose this method because we wanted to understand how our solution might fit into the existing world of collaborative planning, scheduling and messaging services.
Findings

            4.

Aside from mainstream apps like WhatsApp, iMessage, and GoogleCal, many alternative collaboration services targeted Enterprise users, which were not originally our primary stakeholders.​

            5.

These apps focused on things like productivity tracking (Wrike) and task allocation (Float), and did not directly compete with our proposed product.
Persona
Based on our research, we created three personas:

Drew, who is an urban socialite, cares about details in group activities.
Emily, who is a student, wants to organize her school work and personal activities.
Chris, who is a group leader, needs to manage his groups with weekly events.

user goals

Baseon personas, I summed up our target users' needs and goals:

Discuss their groups’ events in one place
See who can and can’t attend an event
Schedule events at times that work for everyone
Make sure everyone’s alerted when plans change
Gauge group interest before changing plans
Be able to talk to everyone attending the event

ideation

We brainstormed solutions and features based on our user research findings and various personas.

Clustered ideas and findings together were helpful in prioritizing and identifying which features and interactions would be most important to include.
Sketch
Turning our brainstorm of features and interactions into sketches helped to visualize and organize our ideas. Sketching multiple versions and iterations gave us options and variations that could help to piece together our initial design.
Low-Fidelity Prototype
The paper prototype included the tasks and features we identified as being the most important. Getting feedback on the paper prototype helped inform the interactions and user flow of our next design iteration.
Mid-Fidelity Prototype
The mid-fidelity prototype incorporated user feedback from testing the paper prototype, and allowed us to create a more interactive experience for users. At this stage, we were able to give users a better understanding of the look and feel of the app, as well as introduce more realistic interactions and task-flow experiences.

User testing insights & Iteration

1.

Users were unclear about the “open task” vs “add task” buttons and some tapped the subject header instead of the action button.
Also, they were unsure if they could select more than one task at one time.
“Can you explain what is open task? What's the differences between open task and add task?” —— Participant 2

Refine:
Made clickable buttons more clear, and differentiated buttons from subject header.
If multiple tasks are allowed, designed them as checkboxes instead of radio boxes.

2.

Users may have different availability on different day.
“Well, can I choose this date with different time? As I don't have time on this available date.” —— Participant 4

Refine:
• Changed the vote options design, which allowed user vote for several options based on their available time.

3.

Users wanted a way to see an event calendar for specific groups, as well as all events across their various groups.
“Can I filter my calendar to specific group?” —— Participant 3

Refine:
Added a drop-down menu on the calendar page that allows users to filter by group or select ‘All Groups’.

Design

Information Architecture

Proposing a new time for an event 

Users can propose a new event time by messaging the event owner or by interacting with the event directly.If the event is unlocked, the user can poll users for an alternative time and event participants can vote on the best option.If users vote to change the event time, the event details are automatically updated on each participant’s calendar.

Signing up for a task 

Users can assign themselves a task by selecting an open task or creating a new task.If the event is locked, the event owner can create the task and assign it directly to a user. The assigned task will automatically appear in the user’s to-do list.
User Flow

Takeaways

Scope

The challenge was not about creating a new experience, interaction, or tool, but instead designing a solution that would organize and combine familiar elements into one platform.

Barriers

Getting all members of a group to download the app and use it consistently remains an obstacle for efficiency and usefulness.