Groopl
Groopl is an innovative application designed to simplify event organization and gathering planning, ideal for occasions such as University Reunions and beyond.
With a suite of user-friendly features, Groopl empowers users to create and share events seamlessly.
Role
UI/UX Designer/BA (30%)
UI/UX Designer/BA (30%)
UI/UX Designer/BA (30%)
Market
US
US
US
Industry
Social Networking
Social Networking
Social Networking
Platform
IOS/CH Play
IOS/CH Play
IOS/CH Play
Challenge
The client wants to develop an application that can create events, manage participants, and facilitate connections all within one app, instead of using separate event apps along with chat, payment tracking, or social media apps.
The target users: ages 25-50.
Initially, the client intended to develop it as a web app but was later advised to develop it as a mobile app based on assessments related to costs and timelines, as provided by the PM
The client wants to develop an application that can create events, manage participants, and facilitate connections all within one app, instead of using separate event apps along with chat, payment tracking, or social media apps.
The target users: ages 25-50.
Initially, the client intended to develop it as a web app but was later advised to develop it as a mobile app based on assessments related to costs and timelines, as provided by the PM
Discover
Research methods & Gather Insight
The client wants to develop an MVP to test with their close friends first, so I have a few meetings to gather questions related to user behavior, such as the purpose of creating an event, the most important features when creating an event, what they want to manage, what makes them most likely to give up when creating an event, and if they can refer to any apps with similar models
The team collects all this information to start dividing the features into core and secondary ones and prioritizing them. Using Figjam for brainstorming, the client also shared some lo-fi versions of their ideas. We use all this information to start defining the features
Research methods & Gather Insight
The client wants to develop an MVP to test with their close friends first, so I have a few meetings to gather questions related to user behavior, such as the purpose of creating an event, the most important features when creating an event, what they want to manage, what makes them most likely to give up when creating an event, and if they can refer to any apps with similar models
The team collects all this information to start dividing the features into core and secondary ones and prioritizing them. Using Figjam for brainstorming, the client also shared some lo-fi versions of their ideas. We use all this information to start defining the features
Research methods & Gather Insight
The client wants to develop an MVP to test with their close friends first, so I have a few meetings to gather questions related to user behavior, such as the purpose of creating an event, the most important features when creating an event, what they want to manage, what makes them most likely to give up when creating an event, and if they can refer to any apps with similar models
The team collects all this information to start dividing the features into core and secondary ones and prioritizing them. Using Figjam for brainstorming, the client also shared some lo-fi versions of their ideas. We use all this information to start defining the features
Define
Problem Statement: The team has a general idea of the key features to be implemented in this MVP version. The priority is to get everything running well enough, with plans to improve after the launch based on feedback received. "Groopl allows event owners to effortlessly create events and share them with their desired guests. Whether it's a university reunion, a community gathering, or a social meetup, users can craft and distribute event details effortlessly.
IA & User Story Mapping: We divide the User Stories based on the actual needs of the users. Due to the limited budget, there is no BA on the project. I will draft the initial version, then review it with the PM before presenting the features to the client.
Business Requirements: We decided to include writing documentation in the backlog and focus on the user flow.
Problem Statement: The team has a general idea of the key features to be implemented in this MVP version. The priority is to get everything running well enough, with plans to improve after the launch based on feedback received. "Groopl allows event owners to effortlessly create events and share them with their desired guests. Whether it's a university reunion, a community gathering, or a social meetup, users can craft and distribute event details effortlessly.
IA & User Story Mapping: We divide the User Stories based on the actual needs of the users. Due to the limited budget, there is no BA on the project. I will draft the initial version, then review it with the PM before presenting the features to the client.
Business Requirements: We decided to include writing documentation in the backlog and focus on the user flow.
Problem Statement: The team has a general idea of the key features to be implemented in this MVP version. The priority is to get everything running well enough, with plans to improve after the launch based on feedback received. "Groopl allows event owners to effortlessly create events and share them with their desired guests. Whether it's a university reunion, a community gathering, or a social meetup, users can craft and distribute event details effortlessly.
IA & User Story Mapping: We divide the User Stories based on the actual needs of the users. Due to the limited budget, there is no BA on the project. I will draft the initial version, then review it with the PM before presenting the features to the client.
Business Requirements: We decided to include writing documentation in the backlog and focus on the user flow.
Develop
Wireframe & Prototyping: We designed low-fidelity wireframes to illustrate the updated layout and navigation, making iterative improvements based on user input. Afterward, we built a high-fidelity interactive prototype to evaluate the design
Build Style Guide: We developed a cohesive visual language and mascot collection, including color schemes, typography, and iconography, ensuring consistency throughout the app and for future updates.
User flow: Basically, the team has agreed on the user flow, so I’m creating it quickly to give everyone an overview.
Collaboration: We worked closely with developers and product managers throughout the design process. Their input and feedback were crucial in refining the design. Developers offered technical feasibility evaluations that guided design modifications, while product managers assisted in prioritizing features and ensuring the design aligned with the overall product objectives. This teamwork made sure that our design was both practical and in harmony with the broader vision, resulting in a more cohesive and effective final product
Wireframe & Prototyping: We designed low-fidelity wireframes to illustrate the updated layout and navigation, making iterative improvements based on user input. Afterward, we built a high-fidelity interactive prototype to evaluate the design
Build Style Guide: We developed a cohesive visual language and mascot collection, including color schemes, typography, and iconography, ensuring consistency throughout the app and for future updates.
User flow: Basically, the team has agreed on the user flow, so I’m creating it quickly to give everyone an overview.
Collaboration: We worked closely with developers and product managers throughout the design process. Their input and feedback were crucial in refining the design. Developers offered technical feasibility evaluations that guided design modifications, while product managers assisted in prioritizing features and ensuring the design aligned with the overall product objectives. This teamwork made sure that our design was both practical and in harmony with the broader vision, resulting in a more cohesive and effective final product
Wireframe & Prototyping: We designed low-fidelity wireframes to illustrate the updated layout and navigation, making iterative improvements based on user input. Afterward, we built a high-fidelity interactive prototype to evaluate the design
Build Style Guide: We developed a cohesive visual language and mascot collection, including color schemes, typography, and iconography, ensuring consistency throughout the app and for future updates.
User flow: Basically, the team has agreed on the user flow, so I’m creating it quickly to give everyone an overview.
Collaboration: We worked closely with developers and product managers throughout the design process. Their input and feedback were crucial in refining the design. Developers offered technical feasibility evaluations that guided design modifications, while product managers assisted in prioritizing features and ensuring the design aligned with the overall product objectives. This teamwork made sure that our design was both practical and in harmony with the broader vision, resulting in a more cohesive and effective final product
Deliver
Visual Design & Style Guide: The client did not have many specific visual requirements for the initial MVP, only needing to ensure consistent use of brand colors across screens and a user-friendly UX that was not too difficult to navigate.
User Feedback: During the design process, the design was updated daily, ensuring that feedback was consistently monitored and managed effectively to prevent any unforeseen changes or updates. Since the app had two distinct roles, I designed each role simultaneously and clearly delineated each flow based on the User Stories (which had been confirmed beforehand) to facilitate easy tracking for the entire team
Visual Design & Style Guide: The client did not have many specific visual requirements for the initial MVP, only needing to ensure consistent use of brand colors across screens and a user-friendly UX that was not too difficult to navigate.
User Feedback: During the design process, the design was updated daily, ensuring that feedback was consistently monitored and managed effectively to prevent any unforeseen changes or updates. Since the app had two distinct roles, I designed each role simultaneously and clearly delineated each flow based on the User Stories (which had been confirmed beforehand) to facilitate easy tracking for the entire team
Visual Design & Style Guide: The client did not have many specific visual requirements for the initial MVP, only needing to ensure consistent use of brand colors across screens and a user-friendly UX that was not too difficult to navigate.
User Feedback: During the design process, the design was updated daily, ensuring that feedback was consistently monitored and managed effectively to prevent any unforeseen changes or updates. Since the app had two distinct roles, I designed each role simultaneously and clearly delineated each flow based on the User Stories (which had been confirmed beforehand) to facilitate easy tracking for the entire team
New challenge
After the initial MVP release, Groopl allowed users to create events in public mode. However, after a period of testing, the common feedback (~60%) was that there were too many public events, which rendered the RSVP feature ineffective. Hosts were unable to track the number of attendees, and the cost management feature was also affected.
14% of users reported that events were fragmented because they were not part of any Group/Club.
The team will propose adding a Level 1 for Groups, with Level 2 being Events (within that Group). Additionally, we will set rules for Group settings (public/private). This will allow us to gather more information about user interests and clearly define target audiences to facilitate marketing efforts.
After the initial MVP release, Groopl allowed users to create events in public mode. However, after a period of testing, the common feedback (~60%) was that there were too many public events, which rendered the RSVP feature ineffective. Hosts were unable to track the number of attendees, and the cost management feature was also affected.
14% of users reported that events were fragmented because they were not part of any Group/Club.
The team will propose adding a Level 1 for Groups, with Level 2 being Events (within that Group). Additionally, we will set rules for Group settings (public/private). This will allow us to gather more information about user interests and clearly define target audiences to facilitate marketing efforts.
After the initial MVP release, Groopl allowed users to create events in public mode. However, after a period of testing, the common feedback (~60%) was that there were too many public events, which rendered the RSVP feature ineffective. Hosts were unable to track the number of attendees, and the cost management feature was also affected.
14% of users reported that events were fragmented because they were not part of any Group/Club.
The team will propose adding a Level 1 for Groups, with Level 2 being Events (within that Group). Additionally, we will set rules for Group settings (public/private). This will allow us to gather more information about user interests and clearly define target audiences to facilitate marketing efforts.
Define + Deliver
With the idea of adding Groups as Level 1, a new flow for creating Groups will need to be implemented.
User Mapping Story (divided into 2 roles):
Since we already have sufficient components and a style guide, we can skip the wireframing step.
Add additional User Stories for setting rules in the Group settings.
Create a prototype to quickly test the flow, ensure that the UX is good, maintain consistency between new flows, and importantly, save time for the user.
With the idea of adding Groups as Level 1, a new flow for creating Groups will need to be implemented.
User Mapping Story (divided into 2 roles):
Since we already have sufficient components and a style guide, we can skip the wireframing step.
Add additional User Stories for setting rules in the Group settings.
Create a prototype to quickly test the flow, ensure that the UX is good, maintain consistency between new flows, and importantly, save time for the user.
With the idea of adding Groups as Level 1, a new flow for creating Groups will need to be implemented.
User Mapping Story (divided into 2 roles):
Since we already have sufficient components and a style guide, we can skip the wireframing step.
Add additional User Stories for setting rules in the Group settings.
Create a prototype to quickly test the flow, ensure that the UX is good, maintain consistency between new flows, and importantly, save time for the user.
Impact
Feedback received: 4 out of 6 users who tested it felt that Groups provided them with greater privacy and made it easier to manage events and related information.
Develop a business model around the ability to subscribe to Groups you like.
With additional space for the community to connect, there is potential to develop additional sub-features.
Feedback received: 4 out of 6 users who tested it felt that Groups provided them with greater privacy and made it easier to manage events and related information.
Develop a business model around the ability to subscribe to Groups you like.
With additional space for the community to connect, there is potential to develop additional sub-features.
Feedback received: 4 out of 6 users who tested it felt that Groups provided them with greater privacy and made it easier to manage events and related information.
Develop a business model around the ability to subscribe to Groups you like.
With additional space for the community to connect, there is potential to develop additional sub-features.
Reflection
This was my first time participating in a project as a Business Analyst, so I initially faced some challenges in defining, organizing, and prioritizing features.
However, contributing to the project not only in the Design aspect allowed me to learn a great deal from the PM, the team, and the clients about evaluating the significance of different priorities in relation to the project's actual situation. Initially, it was a real challenge, but upon completion, I realized that I had acquired several new skills relevant to my role.
This was my first time participating in a project as a Business Analyst, so I initially faced some challenges in defining, organizing, and prioritizing features.
However, contributing to the project not only in the Design aspect allowed me to learn a great deal from the PM, the team, and the clients about evaluating the significance of different priorities in relation to the project's actual situation. Initially, it was a real challenge, but upon completion, I realized that I had acquired several new skills relevant to my role.
This was my first time participating in a project as a Business Analyst, so I initially faced some challenges in defining, organizing, and prioritizing features.
However, contributing to the project not only in the Design aspect allowed me to learn a great deal from the PM, the team, and the clients about evaluating the significance of different priorities in relation to the project's actual situation. Initially, it was a real challenge, but upon completion, I realized that I had acquired several new skills relevant to my role.