Our weekly team sync used to run 55 minutes. It was a status-update parade: each person would summarize what they’d done that week while everyone else half-listened and waited for their turn. Nobody made decisions. Nobody left the meeting with new information they couldn’t have gotten from a Slack message.
We cut it to 25 minutes by changing the format entirely. The meeting now has a single purpose: make decisions that require the whole team’s input. Everything else happens async before the meeting starts.
The format
Here’s the exact structure we run every week:
Pre-meeting (async, due by 9am meeting day)
Every team member fills in a shared Notion doc with three fields:
- Flags — anything blocked, at risk, or needing a decision from the group. These become the meeting agenda.
- Wins — one sentence on something that shipped or progressed. This is optional and brief.
- FYIs — context others should know but that doesn’t need discussion. Read-only.
The Flags section is the meeting agenda. If nobody has flags, we skip the meeting. This has happened three times in six months — and those were good weeks, not lazy ones.
The meeting itself (25 minutes)
- Minutes 1–2: Scan. Everyone has the Notion doc open. Quick scan of wins and FYIs. No verbal read-through — everyone reads faster than they listen.
- Minutes 2–22: Flags. Work through each flag in order. The person who raised it has 30 seconds to frame the issue, then the group discusses and decides. Every flag gets one of three outcomes: a decision, an owner, or a follow-up action with a deadline.
- Minutes 22–25: Capture. The meeting facilitator (it rotates weekly) confirms all decisions and actions are written in the Notion doc. Anyone with an action item verbally confirms they’ve got it.
That’s it. No status updates, no “anything else?” open floor, no screen-sharing a dashboard everyone already has access to.
Post-meeting (within 1 hour)
The facilitator posts the decisions and action items in the relevant Slack channels. The Notion doc stays as the permanent record. Anyone who missed the meeting reads the doc — they get the same information as someone who attended.
Why this works
The format works because it separates information-sharing from decision-making. In a traditional weekly sync, most of the time is information transfer: “Here’s what I did this week.” That’s a waste of synchronous time — it’s exactly the kind of thing that should be written down and read at each person’s own pace. First Round Review’s writing on effective meetings makes a similar case: the highest-value use of synchronous time is discussion and decision-making, not broadcasting.
By moving status updates to the pre-meeting doc, the actual meeting becomes a 25-minute decision-making session. The agenda writes itself (it’s whatever the team flagged), and there’s no filler.
A few design choices worth explaining:
Fixed timebox, not fixed agenda length. We don’t expand the meeting if there are more flags. If we can’t resolve everything in 25 minutes, the remaining flags get moved to async or scheduled as a separate, focused discussion. This prevents meeting bloat.
Rotating facilitator. The facilitator’s job is to keep time, move through flags, and capture decisions. Rotating this role prevents one person from becoming the permanent meeting manager and gives everyone practice running a tight session.
Optional wins section. This is small but meaningful. A one-line win takes 5 seconds to read and gives the team visibility into progress without requiring a verbal presentation. We don’t force it — some weeks, some people skip it. That’s fine.
The Notion template
Here’s the structure of the doc we use. You can recreate this in Notion, Google Docs, or any shared document tool.
# Weekly Sync — [Date]
Facilitator: [Name]
## Flags (agenda items)
- [Name]: [Brief description of the issue/decision needed]
- [Name]: [Brief description of the issue/decision needed]
## Wins
- [Name]: [One sentence]
- [Name]: [One sentence]
## FYIs
- [Name]: [Context that doesn't need discussion]
## Decisions & Actions
- [Decision made] — owner: [name], deadline: [date]
- [Action item] — owner: [name], deadline: [date]We create a new doc each week from this template. Old docs are stored in a “Weekly Syncs” database in Notion sorted by date. This creates a searchable archive of every decision the team has made — useful when someone asks “when did we decide to do X?” six months later.
For more on structuring Notion as a team reference, see our Notion team wiki guide.
Common objections
“What if someone’s flag is complex and needs more than a few minutes?”
Then it gets pulled out of the weekly sync and scheduled as a separate, focused discussion with only the people who need to be there. The weekly sync isn’t the right venue for deep problem-solving — it’s a routing mechanism that identifies which problems need more time and who should be in the room.
“What if the team doesn’t fill in the pre-meeting doc?”
This happened in our first two weeks. We addressed it by making the doc the agenda — literally. If you don’t add your flags, they don’t get discussed. After people missed getting input on a decision they cared about, adoption was 100%.
“25 minutes feels too short.”
It felt short to us too, at first. But track what actually happens in your current meetings. If you subtract status updates, context-setting that could be written, and off-topic tangents, most hour-long meetings have about 20 minutes of real content. The timebox forces discipline.
“This doesn’t work for large teams.”
True — this format works best for teams of 4-10 people. Beyond that, you need to split into smaller groups with separate syncs, then roll up decisions to a leads meeting. The same format scales at each level, but you need the right grouping.
Transitioning from a longer format
If you’re currently running 45-60 minute weeklies, don’t switch cold. Here’s a two-week transition:
Week 1: Introduce the pre-meeting doc. Keep the meeting length the same but start with the doc and see how much faster status updates go when people have already written them down.
Week 2: Cut the meeting to 30 minutes. Use the flags-only format for the meeting itself. Async everything else.
Week 3 onward: Trim to 25 minutes once the team is comfortable with the format. Adjust the timebox based on your team size — a 5-person team might only need 20 minutes.
The pre-meeting doc is the critical piece. Once your team gets in the habit of writing things down before the meeting, the meeting naturally shortens because there’s less to say out loud.
What we got wrong initially
Two mistakes worth mentioning:
First, we tried having the facilitator also take notes during the meeting. This is too much for one person — you can’t manage the clock, direct conversation, and accurately capture decisions simultaneously. Now, the facilitator manages the session and writes decisions in the Decisions section during the meeting. Others correct or add to it in the 5 minutes after.
Second, we didn’t post meeting decisions back to Slack for the first month. This meant people who missed the meeting had to go find the Notion doc themselves, and often didn’t. The Slack post is a 2-minute task that dramatically increases decision visibility. It’s part of the facilitator’s job now.
The meeting format is simple. The discipline is hard. But once your team has done it for three or four weeks, the old hour-long status parade will feel like a relic. You’ll get more decided in 25 minutes than you used to in an hour — because you’re spending the meeting on the things that actually need everyone in the room.