Abstract Wikipedia team/Meetings plan
Appearance
Meetings Plan
[edit]Our team follows a structured weekly schedule with themed days to balance collaboration, deep work, and strategic alignment:
- Mondays – Focus on social connection with casual conversations and one-on-one meetings.
- Tuesdays – Work-in-progress (WIP) meetings, where we discuss ongoing tasks, blockers, and tactical decisions.
- Wednesdays – Team meeting to align on progress.
- Thursdays – Check-in and Retro, day focus on technical direction, and retrospective.
| Time | Monday | Tuesday | Wednesday | Thursday | Friday |
| 16:00 UTC | 1:1s Between Timezones | Weekly OKR Status | No Meetings Day | ||
| 16:30 UTC | Work In Progress | Engineering Check-in | |||
| 17:00 UTC | Social Time | Work In Progress | AW Team Meeting | ||
| 17:30 UTC | 1:1s Between Timezones | Future Plans | W1/2 Retro | ||
| 18:00 UTC | |||||
| 18:30 UTC | AW Weekly Triage |
Our meetings are designed to keep everyone informed, aligned, and engaged while respecting individual work time. We have a mix of synchronous and asynchronous discussions to accommodate different time zones and schedules. While attendance is encouraged for key meetings like team syncs and strategy discussions, we understand that flexibility is important. Essential meetings require participation from relevant team members, while others may be optional or have async follow-ups. We document meeting notes so everyone can stay updated, even if they can’t attend in real time.
| Meeting | Recurring | Purpose | Agenda | Attendance | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| PM | EM | UX | Eng | QTE | Comms | |||||
| Lead | All | |||||||||
| Weekly Team Meeting | Weekly | Share what we're each working on, how we’re feeling, align on our focus areas for the week |
|
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Weekly OKR Status | Weekly | Report on OKR status and contextualize work being done on the team. Identify and manage risks. |
|
✅ | ✅ | ✅ | ✅ | ✅ | 〰️ | 〰️ |
| Work In Progress | Weekly | Synchronous collaboration on quarterly projects. |
|
〰️ | 〰️ | 〰️ | 〰️ | 〰️ | 〰️ | |
| Engineering Check-In | Weekly | The engineering team meets to show each other their current work and problem-solve. |
|
〰️ | ✅ | 〰️ | ✅ | ✅ | 〰️ | |
| Retro | Bi-weekly | Talk about what's working well, what's not working well, what we can improve, etc. |
|
✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |
| Social | Weekly | A "water-cooler" where the team can talk socially about their lives and bond. |
|
〰️ | 〰️ | 〰️ | 〰️ | 〰️ | 〰️ | |
| Future Plans | Bi-weekly | A bi-weekly meeting for the team to discuss future plans |
|
✅ | ✅ | 〰️ | ✅ | 〰️ | 〰️ | |
| Volunteers' Corner | Monthly | Informal space on the first Monday of the month for volunteers and the AW team members for pairing, code review, talking about what volunteers have achieved or how to approach a task, which task is best to pick up next, etc. |
|
〰️ | 〰️ | 〰️ | ✅ | 〰️ | ✅ | |
| Natural Language Generation SIG[1] | Monthly | Face to face time with volunteers and AW team members working on or interested in Natural Language Generation. |
|
〰️ | 〰️ | 〰️ | ✅ | 〰️ | ✅ | |
Legend:
- "✅" = attendance expected
- "〰️" = attendance optional
- ↑ SIG = Special Interest Group meeting