Meetwith
Meetwith
/
📝
Product Documents
/
archive
/
Group Meeting Scheduling Feature on MWW
Group Meeting Scheduling Feature on MWW
/
Product Requirements Document → Group Scheduling Feature on MWW
Product Requirements Document → Group Scheduling Feature on MWW
Product Requirements Document → Group Scheduling Feature on MWW
Product Requirements Document → Group Scheduling Feature on MWW

Product Requirements Document → Group Scheduling Feature on MWW

💡
This is a documented summary of the features requirements for the new feature implementation on MWW — the Group Meeting Scheduling.
Title:
Group meeting scheduling on MWW.
Change history:

Requirements Changes

Change History
Changes
Editor
Date of Change
First version of the PRD: Initial details,
Osinachi Patrick
Overview:
We aim to enhance the scheduling of group meetings on our product, MWW (Meetwithwallet). While we've already introduced a Discord bot that enables users to schedule meetings based on the first available time for all participants, we recognize the need to provide users with more flexibility in determining when they can convene for discussions on specific topics. As a point of reference, consider the functionality provided by Lettucemeet, which, despite its shortcomings, remains popular among users.
Our goal is to refine and expand our scheduling capabilities, allowing users to exercise greater control over when they can engage in conversations and collaboration. We understand that while the existing scheduling solutions has its merits, there are instances where users may prefer to choose a time that aligns more closely with their specific needs and preferences. With this in mind, I’ll be providing a detailed improved solution requirements in this document defining ways to implement a group scheduling feature on MWW to provide a more versatile and user-friendly experience.
Objectives:
What will this let the customer do? What are our high level internal goals for doing this project?
  • Implementing a new feature called TimeSync on meetwithwallet.
  • Provide a feature for frictionless time coordination for teams/group.
  • Transparency in team members availability.
  • Less meeting scheduling links for group meeting scheduling.
Success metrics:
💡
What are the success metrics that indicate you’re achieving your internal goals for the project?
  • Growth: Increase in the number of users for MWW (gain 2k new users 6 months after launch).
  • Increased Revenue: Grow the number of active PRO users from 11 to 500, six(6) months after launch.
  • User satisfaction: Address the identified user pain points we have gathered during user research. E.g in screenshot below:
      • notion image
Messaging:
  • Group meeting scheduling made easy.
  • Team meeting scheduling on auto-pilot.
  • We have developed an improved solution for users who are tired of the back and forth in group meetings scheduling.
Product Feature Storytelling: TimeSync
Timeline/release planning:

Timeline

Feature Implementation Timeline
User Persona(s):
I’ll get this from any initial interview or design process conducted for the product with some little adjustment.
User scenarios:
💡
This feature is basically for people want to seamlessly find the best time when everyone that needs to be in a meeting will be available and also quickly schedule the meeting for all. This feature is seen as a separate feature within MWW called TimeSync.
A user with an already existing account
  • A user can create an instance of a new meeting.
  • A user that already have an account would easily have to import the available time slots in their connected calendars.
  • If the user already has an account, with a team created, they can easily import their availability and team members availability and ping anyone who hasn’t connected their updated calendar to do so for easy import of availability.
  • A user can also share a meeting link with other participants if they don’t have any team created yet.
  • other users (guests) can also manually update their availability or by strong recommendation notified to import their availability from their calendar.
  • The host can see a chart summary of all time inputs and see what the popular available time is and can choose that.
  • Users can edit the availability they entered before submitting, and can edit till the meeting is scheduled.
  • The other users can enter their name and email address for notification/scheduling purposes if they wish to schedule immediately.
  • The host can easily pick time and schedule the meeting for all.
A user without an account yet — the current MWW doesn’t afford this, it’ll be a good edge if we consider this.
  • A user that doesn’t have an account would have to connect their calendar first and get the availabilities but they will have limitations with importing members from teams since they don’t have any account with team, so they just have to connect their calendars, update their availabilities and then share meeting link with other participants.
  • other users (participants) will have to connect their calendar to share their available time slots and they can easily change.
  • other participants can manually edit their available times with a tip banner to enter availability with calendar instead to avoid double entry of a particular time.
  • The users can input their details for easy scheduling of the meeting after they’ve identified a time.
Functional Requirements:
💡
These are the distinct, prioritised functionalities of this new feature in MWW along with a short explanation as to why the features are important.
User with an Existing Account:
  1. Create a New Meeting Instance:
      • The user must have the ability to create a new meeting instance, specifying the meeting's title, description, and participants.
  1. Import Calendar Availability:
      • Users with existing accounts should be able to easily import their available time slots from their connected calendars, which may include Google Calendar, Apple Calendar, or other compatible calendar services.
  1. Team Availability Import:
      • If the user has created a team within their account, they should have the option to import their team members' availability as well. The system must provide a feature to prompt team members who have not connected their calendars to do so for easy availability import.
  1. Share Meeting Link:
      • Users can share a meeting link with other participants. This link should grant access to the meeting details and scheduling options, even for participants who do not have an account or a team set up.
  1. Manual Availability Update for Guests:
      • Non-account holders (guests) should be able to manually update their availability. The system should strongly recommend them to import their availability from their calendar if applicable.
  1. Availability Chart Summary:
      • The host should be able to view a chart summarizing all participants' time inputs and identify popular available times. This summary should assist in scheduling the meeting.
  1. Edit Availability:
      • Users must have the ability to edit the availability they've entered before the meeting is scheduled. This editing should be possible until the meeting is finalized.
  1. Name and Email Entry for Guests:
      • Participants who do not have an account may enter their name and email address for notification and scheduling purposes when scheduling the meeting.
  1. Schedule the Meeting:
      • The host should have a straightforward process for picking a time and scheduling the meeting for all participants. The system should handle the scheduling and send notifications to all participants.
User without an Account:
  1. Calendar Connection for Availability:
      • Users without an account should be able to connect their calendars to access their availability. This is a critical feature, and the system should provide guidance on how to connect popular calendar services.
  1. Limited Team Functionality:
      • Users without an account cannot create teams. Therefore, they will have limitations in importing team members' availability.
  1. Sharing Meeting Link:
      • Non-account holders should be able to share a meeting link with other participants, allowing them to access the meeting details and scheduling options.
  1. Manual and Calendar Availability Editing:
      • Participants, including those without accounts, should be able to manually edit their available times. To avoid duplication, the system should provide a tip banner encouraging users to enter availability through calendar integration.
  1. Participant Details Input:
      • Users without accounts should be able to input their details, such as name and email address, to facilitate scheduling of the meeting after identifying a suitable time.
Acceptance Criteria:
💡
This serves as a set of guidelines to determine whether the work has been successfully accomplished and align with the intended goals and expectations.
Using a prototype to run a validation test, in form of interviews to ensure that users will be willing to pay for this.
Ensure that the proportion of YES from willing to pay clients are more than the proportion of NO and NOT SURE.
Ensure a highly performant release — with less bugs after the beta testing.
Test with 20 users to ensure stability.
Designs:
Open issues:
💡
What factors do you still need to figure out?
  1. Do we need to implement a feature on MWW that allows users that aren’t logged in to still go ahead and schedule this meetings? I think this low barrier to use is what gives Lettucemeet some users.
Q&A:
💡
What are common questions about the product, and answers to those questions? This is a good place to note key decisions.
Questions and Feedback (Stakeholders → Product Team)
💡
Here stakeholders can ask their questions and get answers, detailed responses and feedback to their questions from the product team.
  1. [Question 1]
💡
  1. [Question 2]
💡
  1. [Question 3]
💡
Questions and Feedback (Product Team → Stakeholders)
💡
Here the product team can ask their questions and get responses and feedback to their questions from the stakeholder.
 
  1. Will the product need a new design or this feature will be sitting on the current design?
💡
  1. [Question 2]
💡
  1. [Question 3]
💡
Other considerations:
This is a catch-all for anything else, such as if you make a key decision to remove or add to the project’s scope.
Meetwith
Meetwith
/
📝
Product Documents
/
archive
/
Group Meeting Scheduling Feature on MWW
Group Meeting Scheduling Feature on MWW
/
Product Requirements Document → Group Scheduling Feature on MWW
Product Requirements Document → Group Scheduling Feature on MWW
Product Requirements Document → Group Scheduling Feature on MWW
Product Requirements Document → Group Scheduling Feature on MWW

Product Requirements Document → Group Scheduling Feature on MWW

💡
This is a documented summary of the features requirements for the new feature implementation on MWW — the Group Meeting Scheduling.
Title:
Group meeting scheduling on MWW.
Change history:

Requirements Changes

Change History
Changes
Editor
Date of Change
First version of the PRD: Initial details,
Osinachi Patrick
Overview:
We aim to enhance the scheduling of group meetings on our product, MWW (Meetwithwallet). While we've already introduced a Discord bot that enables users to schedule meetings based on the first available time for all participants, we recognize the need to provide users with more flexibility in determining when they can convene for discussions on specific topics. As a point of reference, consider the functionality provided by Lettucemeet, which, despite its shortcomings, remains popular among users.
Our goal is to refine and expand our scheduling capabilities, allowing users to exercise greater control over when they can engage in conversations and collaboration. We understand that while the existing scheduling solutions has its merits, there are instances where users may prefer to choose a time that aligns more closely with their specific needs and preferences. With this in mind, I’ll be providing a detailed improved solution requirements in this document defining ways to implement a group scheduling feature on MWW to provide a more versatile and user-friendly experience.
Objectives:
What will this let the customer do? What are our high level internal goals for doing this project?
  • Implementing a new feature called TimeSync on meetwithwallet.
  • Provide a feature for frictionless time coordination for teams/group.
  • Transparency in team members availability.
  • Less meeting scheduling links for group meeting scheduling.
Success metrics:
💡
What are the success metrics that indicate you’re achieving your internal goals for the project?
  • Growth: Increase in the number of users for MWW (gain 2k new users 6 months after launch).
  • Increased Revenue: Grow the number of active PRO users from 11 to 500, six(6) months after launch.
  • User satisfaction: Address the identified user pain points we have gathered during user research. E.g in screenshot below:
      • notion image
Messaging:
  • Group meeting scheduling made easy.
  • Team meeting scheduling on auto-pilot.
  • We have developed an improved solution for users who are tired of the back and forth in group meetings scheduling.
Product Feature Storytelling: TimeSync
Timeline/release planning:

Timeline

Feature Implementation Timeline
User Persona(s):
I’ll get this from any initial interview or design process conducted for the product with some little adjustment.
User scenarios:
💡
This feature is basically for people want to seamlessly find the best time when everyone that needs to be in a meeting will be available and also quickly schedule the meeting for all. This feature is seen as a separate feature within MWW called TimeSync.
A user with an already existing account
  • A user can create an instance of a new meeting.
  • A user that already have an account would easily have to import the available time slots in their connected calendars.
  • If the user already has an account, with a team created, they can easily import their availability and team members availability and ping anyone who hasn’t connected their updated calendar to do so for easy import of availability.
  • A user can also share a meeting link with other participants if they don’t have any team created yet.
  • other users (guests) can also manually update their availability or by strong recommendation notified to import their availability from their calendar.
  • The host can see a chart summary of all time inputs and see what the popular available time is and can choose that.
  • Users can edit the availability they entered before submitting, and can edit till the meeting is scheduled.
  • The other users can enter their name and email address for notification/scheduling purposes if they wish to schedule immediately.
  • The host can easily pick time and schedule the meeting for all.
A user without an account yet — the current MWW doesn’t afford this, it’ll be a good edge if we consider this.
  • A user that doesn’t have an account would have to connect their calendar first and get the availabilities but they will have limitations with importing members from teams since they don’t have any account with team, so they just have to connect their calendars, update their availabilities and then share meeting link with other participants.
  • other users (participants) will have to connect their calendar to share their available time slots and they can easily change.
  • other participants can manually edit their available times with a tip banner to enter availability with calendar instead to avoid double entry of a particular time.
  • The users can input their details for easy scheduling of the meeting after they’ve identified a time.
Functional Requirements:
💡
These are the distinct, prioritised functionalities of this new feature in MWW along with a short explanation as to why the features are important.
User with an Existing Account:
  1. Create a New Meeting Instance:
      • The user must have the ability to create a new meeting instance, specifying the meeting's title, description, and participants.
  1. Import Calendar Availability:
      • Users with existing accounts should be able to easily import their available time slots from their connected calendars, which may include Google Calendar, Apple Calendar, or other compatible calendar services.
  1. Team Availability Import:
      • If the user has created a team within their account, they should have the option to import their team members' availability as well. The system must provide a feature to prompt team members who have not connected their calendars to do so for easy availability import.
  1. Share Meeting Link:
      • Users can share a meeting link with other participants. This link should grant access to the meeting details and scheduling options, even for participants who do not have an account or a team set up.
  1. Manual Availability Update for Guests:
      • Non-account holders (guests) should be able to manually update their availability. The system should strongly recommend them to import their availability from their calendar if applicable.
  1. Availability Chart Summary:
      • The host should be able to view a chart summarizing all participants' time inputs and identify popular available times. This summary should assist in scheduling the meeting.
  1. Edit Availability:
      • Users must have the ability to edit the availability they've entered before the meeting is scheduled. This editing should be possible until the meeting is finalized.
  1. Name and Email Entry for Guests:
      • Participants who do not have an account may enter their name and email address for notification and scheduling purposes when scheduling the meeting.
  1. Schedule the Meeting:
      • The host should have a straightforward process for picking a time and scheduling the meeting for all participants. The system should handle the scheduling and send notifications to all participants.
User without an Account:
  1. Calendar Connection for Availability:
      • Users without an account should be able to connect their calendars to access their availability. This is a critical feature, and the system should provide guidance on how to connect popular calendar services.
  1. Limited Team Functionality:
      • Users without an account cannot create teams. Therefore, they will have limitations in importing team members' availability.
  1. Sharing Meeting Link:
      • Non-account holders should be able to share a meeting link with other participants, allowing them to access the meeting details and scheduling options.
  1. Manual and Calendar Availability Editing:
      • Participants, including those without accounts, should be able to manually edit their available times. To avoid duplication, the system should provide a tip banner encouraging users to enter availability through calendar integration.
  1. Participant Details Input:
      • Users without accounts should be able to input their details, such as name and email address, to facilitate scheduling of the meeting after identifying a suitable time.
Acceptance Criteria:
💡
This serves as a set of guidelines to determine whether the work has been successfully accomplished and align with the intended goals and expectations.
Using a prototype to run a validation test, in form of interviews to ensure that users will be willing to pay for this.
Ensure that the proportion of YES from willing to pay clients are more than the proportion of NO and NOT SURE.
Ensure a highly performant release — with less bugs after the beta testing.
Test with 20 users to ensure stability.
Designs:
Open issues:
💡
What factors do you still need to figure out?
  1. Do we need to implement a feature on MWW that allows users that aren’t logged in to still go ahead and schedule this meetings? I think this low barrier to use is what gives Lettucemeet some users.
Q&A:
💡
What are common questions about the product, and answers to those questions? This is a good place to note key decisions.
Questions and Feedback (Stakeholders → Product Team)
💡
Here stakeholders can ask their questions and get answers, detailed responses and feedback to their questions from the product team.
  1. [Question 1]
💡
  1. [Question 2]
💡
  1. [Question 3]
💡
Questions and Feedback (Product Team → Stakeholders)
💡
Here the product team can ask their questions and get responses and feedback to their questions from the stakeholder.
 
  1. Will the product need a new design or this feature will be sitting on the current design?
💡
  1. [Question 2]
💡
  1. [Question 3]
💡
Other considerations:
This is a catch-all for anything else, such as if you make a key decision to remove or add to the project’s scope.