People plan events of all sizes and types every day. How do they all come together? Is it the work of an individual with super planning powers? Is there a team of people pulling together, pooling their knowledge? How can anyone pull off planning joyful and thoughtful events in our busy lives, when we are all scattered across the country or the world, trying to keep on top of everything that needs to be done?
I combined primary research via interviews of potential users with competitor research of similar products to be sure I had a good vision of who plans events, how they plan them, what tools they use, how they feel through the process, and what frustrates them.
I spoke with 4 participants who had recently planned events with others. All identified as female, and were in their 30s, 40s, and 50s. Some planned personal events such as kids' birthday parties or family reunions; some planned events as part of their job responsibilities.
One persona for this product is "Julie". Julie represents the user who is enthusiastic about hosting an event, although stressed by the planning coordination. She needs to engage other planners across distance on the tasks and decisions, but has trouble doing so. In some cases, her planners are not as tech savvy as she is, or they are too busy to schedule regular meetings with.
"Julie" wants to plan an event she is proud of hosting, guided by a clear vision of the event. She wants to be inspired and excited by event planning, not dreading it.
One persona for this product is "Julie". Julie represents the user who is enthusiastic about hosting an event, although stressed by the planning coordination. She needs to engage other planners across distance on the tasks and decisions, but has trouble doing so. In some cases, her planners are not as tech savvy as she is, or they are too busy to schedule regular meetings with.
"Julie" wants to plan an event she is proud of hosting, guided by a clear vision of the event. She wants to be inspired and excited by event planning, not dreading it.
Once I had a good idea of the motivations, goals, and pain points of potential users, I started to ideate on how to help solve the problems they face through Point of View Statements and turning them into How Might We...? questions.
I created a MoSCoW chart of all potential features to explore options for the product. From this, a list of "must-have" features was determined.
.png)
I outlined the site structure into three main sections behind the sign in gateway: events, communications, and account. The events pages house the majority of the features of the site. Communication is currently home to the group chat feature, but has room to grow to include future planned notifications, surveys, and guest communication features.
I outlined the site structure into three main sections behind the sign in gateway: events, communications, and account. The events pages house the majority of the features of the site. Communication is currently home to the group chat feature, but has room to grow to include future planned notifications, surveys, and guest communication features.
I created user flows which helped visualize all the decision points and potential pathways users might take to complete the must-have functions of the product. 6 user flows were created: Chatting with co-planners, Checking off to-do list tasks, Adding an image to the mood board, Creating a new event, Creating a new account, and Logging in
.png)
.png)
.png)
.png)
.png)
I created user flows which helped visualize all the decision points and potential pathways users might take to complete the must-have functions of the product. 6 user flows were created: Chatting with co-planners, Checking off to-do list tasks, Adding an image to the mood board, Creating a new event, Creating a new account, and Logging in
These were then streamlined into task flows.
.png)
.png)
.png)
.png)
These were then streamlined into task flows.
These flows guided the low fidelity mobile wireframes which traced the paths to complete each task, identifying how to pace users’ progress. These frames also tested the validity of the flows and helped iterate task processes. I was able to discuss these frames with some colleagues to get feedback on the general feel of of the flow, and various layout ideas, which ultimately made the next steps smoother.
After sharing with colleagues, some design elements were added, determinations about page variations were made, and first decisions about visual hierarchy and spacing were made.
.png)
After sharing with colleagues, some design elements were added, determinations about page variations were made, and first decisions about visual hierarchy and spacing were made.
.png)
Orange and pink/coral colors invoke energy and warmth, while also being grounded in earthy tones. Style should be excited but not untouchable or exclusive.
Core Brand Values:
Orange and pink/coral colors invoke energy and warmth, while also being grounded in earthy tones. Style should be excited but not untouchable or exclusive.
Core Brand Values:
In developing a logo and wordmark, I wanted to emphasize the product as bringing people together, hence the two party hats, while keeping the nature of the event somewhat vague.
Utilizing the brand logo, typography, and mood board, I created components for the various functions of the product and developed the high fidelity wireframes for key flows which would then be employed in usability testing.
.png)
.png)
Utilizing the brand logo, typography, and mood board, I created components for the various functions of the product and developed the high fidelity wireframes for key flows which would then be employed in usability testing.
I tested 4 tasks representing key functions of the product: Creating a new event, Adding an image to the mood board, commenting on the image, and starting a group chat.
Users responded positively to the appearance, feel, and functions of the prototype. Overall, they responded that the tasks were not difficult, the experience was enjoyable, they felt comfortable completing tasks using the site, and they were likely to use the product.
.png)
I tested 4 tasks representing key functions of the product: Creating a new event, Adding an image to the mood board, commenting on the image, and starting a group chat.
Users responded positively to the appearance, feel, and functions of the prototype. Overall, they responded that the tasks were not difficult, the experience was enjoyable, they felt comfortable completing tasks using the site, and they were likely to use the product.
In this video, I give a tour of the 4 flows tested during product development: Creating a new event, Adding images to a mood board, Commenting on an image, and Starting a group chat.
