Meeting Overview

• Date: January 21, 2025
• Attendees: Amir (Co- Lead), Elizabeth (Strat Apprentice), Kata (Strat Apprentice), Chen Yi (Strat Apprentice), Gelon (PM Lead), Rachel (UXD Apprentice), Philip (UXR Lead)
• Purpose: Get updates on teams progress.

Goals

• Strategy Team introduced to Team Leads.
• Establish Product Strategy Roles and Responsibilities.
• Define Sprint Plan for project.
• Establish Communication Plan for the project.
• Remove team blockers for the project.

Action Items

PS Team Action Items

PS Team Action Items

Notes

Key Discussion Points

1. Introductions and Team Structure:
   • Team members introduced themselves, sharing their roles, backgrounds, and interests.
   • Core strategy team includes Amir, Katar, Elizabeth, and Jenny, with contributions from UX and Product apprentices.
   • Note-taking responsibilities were discussed, with the potential for rotating responsibilities to ensure inclusivity.
2. Team Resources and Communication:
   • Figma: Established as the central repository for team and project resources.
   • Discord: Reinforced as the primary channel for real-time communication; Katar to join Discord.
   • Proposal to allow apprentices to attend leads meetings as observers to improve communication and transparency.
     • Context: Observing leads meetings can provide apprentices with better visibility into decision-making processes and improve overall communication.
3. Enhancing Inclusivity in Feedback and Input:
   • Several strategies were proposed to incorporate feedback from all team members including apprentices:
     • Opening leads meetings to apprentices: While not active participants, observing these meetings could improve transparency.
     • Regular all-hands meetings: Create a forum where all team members can share ideas and provide input.
     • Asynchronous feedback opportunities: Utilize shared documents or Slack channels for team members who cannot attend meetings to contribute ideas.
     • Rotating note-taking responsibilities: Involving apprentices in note-taking ensures visibility into discussions and decisions across the team.
   • Key Takeaway: Creating multiple participation channels ensures more informed and inclusive decisions across the team.
4. Sprint Planning and Responsibilities:
   • Emphasis on two-week sprints, with Sprint Zero currently underway.
   • Strategy team tasks include:
     • Reviewing the product kickoff document and prioritization matrix.
     • Brainstorming solutions and preparing for client workshops.
   • Feedback from UX Design: A shared brainstorming board was created in Discord to compile questions and ideas for client meetings.
5. Client Meeting Preparation:
   • Scheduled for Thursday, including a dedicated 15-minute Q&A session.
   • Questions for the client to be compiled in the shared Figma board.
   • Discussion on assigning strategy team members to ask questions during the client meeting.