/meet Command

Introduction

Demo video

🔥 Video will be uploaded soon. Stay connected with us

The /meet command is designed to help you perform Q&A over a Google Meet's transcript. This means you can use it to analyze and extract information from the transcript of a Google Meet session, making it easier to review discussions, decisions, or any important points covered during the meeting.

How to use

1. Initiate the Command: In your Google Chat, type /meet followed by the details of the Google Meet session you want to analyze. This could include a link to the meeting or a specific request for transcript analysis.

2. Specify Your Query: Clearly state what information you need from the Google Meet transcript. For example, you might want to extract decisions made during the meeting, summarize key points, or find specific discussions.

Example

    /meet Analyze the Google Meet transcript from today's team meeting and summarize the key decisions.

3. Receive Results: Hana will process your request and provide you with the relevant information extracted from the meeting transcript. This can include summaries, identified action items, or answers to specific questions you posed.

Examples

• In above scenario Nav archer has shared link of recent meet.
• And asked Hana “Hana create a list of action points from this meeting for @Pranay Kayarkar” by using /meet command.

/meet command triggered by @Nav Archer

Question: Hana create a list of action points from this meeting for @Pranay Kayarkar

Here are the action points from the KT session on Discord Server Changes presented by Pranay:

1. Onboarding Flow for New Users:
   - Create an onboarding flow with questions for new members.
   - Ensure questions are clear and concise to avoid overwhelming new users.

2. Channel Setup:
   - Include at least seven channels in the server.
   - Ensure five channels are open for everyone to read and send messages.

3. Moderation Settings:
   - Implement moderation settings to prevent inappropriate messages.
   - Regularly monitor and adjust moderation tools as needed.

4. Content Posting and Engagement:
   - Regularly post updates and engage with the community.
   - Consider the type of content that will be posted in different channels (e.g., product updates, tech news).

5. Competitor Analysis:
   - Analyze competitor servers to understand their community engagement strategies.
   - Look into servers of similar products to gather ideas for improvement.

6. Channel Optimization:
   - Convert the support channel to a forum channel for better engagement.
   - Rename and reorganize channels for clarity (e.g., product announcements, tech news).

7. Webinar Planning:
   - Plan a webinar to introduce new features and gather feedback.
   - Decide on the platform for hosting the webinar and ensure it can accommodate the expected number of participants.

8. Documentation and Resources:
   - Update the resources section with relevant documentation and quick links.
   - Ensure all channels have clear and useful content to aid users.

9. Server Management:
   - Assign a dedicated server manager to oversee updates and community engagement.
   - Ensure regular communication and updates are posted on the server.

10. Feedback and Improvement:
    - Collect feedback from users and implement necessary changes.
    - Regularly review and improve the server based on user engagement and feedback.

Pranay, please ensure these action points are addressed and implemented to improve the Discord server's functionality and user engagement.

• In above scenario Nav archer has shared link of recent meet.
• And asked Hana “hana what is the outcome of this meet? Create a conclusion and next steps for everyone” by using /meet command.

/meet command triggered by @Nav Archer

Question: hana what is the outcome of this meet? Create a conclusion and next steps for everyone

Sure @Nav Archer, here's the conclusion and next steps from the meeting:

### Conclusion:
1. Sprint Planning Rhythm:
   - The team has decided to set up recurring meetings on the last day of each sprint to plan for the next sprint.
   - Meetings will be held every Monday, marking the first day of the sprint, to check the backlog and plan tasks.

2. Sprint Duration:
   - Each sprint will be two weeks long, starting from August 5th to August 18th.
   - The subsequent sprints will follow a similar two-week cycle.

3. Task Allocation and Story Points:
   - Tasks will be assigned story points based on their complexity and estimated effort.
   - A guide was discussed to standardize story points: 
     - 1 story point: Tasks taking 2-3 hours.
     - 2 story points: Tasks taking 1-2 days.
     - 3 story points: Tasks taking 3-4 days.
   - Tasks larger than 3 story points should be broken down into smaller tasks.

4. Retrospective Meetings:
   - Retrospective meetings will be conducted to review the progress of the previous sprint.
   - The team will discuss what went right, what went wrong, and what can be improved.
   - Action items from retrospectives will be documented and tracked.

5. Tracking and Reporting:
   - A Notion template will be used for tracking story points and task progress.
   - The team will aim for a target of 25 story points per sprint, adjusting based on performance and capacity.

### Next Steps:
1. Set Up Recurring Meetings:
   - Schedule recurring sprint planning meetings for every Monday.
   - Ensure all team members are invited and aware of the schedule.

2. Task Assignment:
   - Assign story points to tasks for the current sprint.
   - Break down larger tasks into manageable pieces with appropriate story points.

3. Retrospective Preparation:
   - Prepare for the first retrospective meeting by documenting the progress and challenges faced in the current sprint.
   - Use the Notion template to record findings and action items.

4. Monitor Progress:
   - Continuously monitor task progress and adjust story points if necessary.
   - Ensure all team members are updating their task status regularly.

5. Review and Adjust:
   - After the first few sprints, review the process and make adjustments to improve efficiency and accuracy in task estimation and completion.

By following these steps, the team can ensure a structured and efficient sprint planning and review process, leading to better project management and delivery. If there's anything specific you need further clarification on, feel free to ask!