Design a productive weekly team sync agenda

Turn passive status updates into collaborative discussion and unblocking. Use this to establish a focused 30-to-45-minute weekly team routine.

You getMeeting Charter, pre-work Requirements and agenda Table

Prompt

Prompt
Act as an experienced operations lead. Help me design a high-impact recurring weekly team sync that replaces status readouts with blocker removal and collaborative problem-solving.

First, ask me these 3 questions in one message and wait for my response:
1. What is your team function and typical meeting duration?
2. What are the top 2 recurring issues or time-wasters in your current syncs?
3. How do team members currently share routine status updates before the meeting?

Once I reply, design a custom agenda template following these rules:
- Limit routine status sharing to asynchronous pre-reads.
- Dedicate at least 60% of meeting time to unblocking and active decisions.
- Include explicit time allocations for each section.
- Provide exact guidelines for what attendees must prepare in advance.

Output format:
- Meeting Charter (purpose, cadence, length)
- Pre-work Requirements (async expectations)
- Agenda Table (Time, Topic, Objective, Owner)
- Meeting Ground Rules
- Post-meeting Action Protocol

Example output

Example for: an 8-person product engineering team running a 45-minute sync

Meeting Charter
  • Purpose: Resolve cross-functional bottlenecks, align on weekly release priorities, and make collective decisions.
  • Cadence & Duration: Weekly on Monday at 10:00 AM; 45 minutes strict.
Pre-work Requirements
  • Every engineer posts two bullet points in the team channel by 9:00 AM: Top objective for the week and current blockers.
  • Attendees must read the update thread before joining the call. No verbal status recitation is allowed.
Agenda Table
TimeTopicObjectiveOwner
00-05 minMetric & Sprint CheckReview sprint burn-down and service uptimeScrum Master
05-25 minBlocker ClearinghouseTriage and resolve submitted blockersTeam Lead
25-40 minArchitecture TopicDebate proposed API schema changesSenior Engineer
40-45 minAction Item Wrap-UpConfirm assignees and committed deadlinesAll
Meeting Ground Rules
  • If a topic only impacts two people, take it to a 1-on-1 breakout immediately.
  • Silence defaults to consent on async pre-reads; we do not re-read slides.
Post-meeting Action Protocol
  • Designated note-taker posts the action summary to the team channel within 30 minutes.
  • Every action item must have a single owner and a delivery date.
Written by AI from this prompt. Your results will vary.

Paste this prompt into ChatGPT, Claude, or Gemini. The model will ask you three quick questions about your team workflow. Follow up by asking for a shared Slack or Teams pre-read reminder template to support the meeting.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Meetings & Notes
Meetings & Notes

Draft a crisp meeting follow-up email fast

Turn raw meeting takeaways into an executive-ready follow-up email within seconds. Use this right after client, cross-functional, or team syncs to keep momentum going.