Status updates are read before the meeting. Live time is for the three things that actually need a room: decisions, blockers, and cross-team dependencies.
The weekly team meeting is the most common meeting in every organization — and the most commonly wasted. The default format is a round-robin: each person gives a verbal update while everyone else half-listens, waiting for their turn. Forty-five minutes pass. No decisions are made. Everyone leaves knowing roughly what they already knew, having contributed nothing they couldn't have written in five minutes.
The ED3 Team Weekly inverts this. Status is handled in writing before anyone enters the room. The meeting itself exists only for the things that require live human judgment: decisions that need the group, blockers that need escalation, and dependencies that need coordination. Everything else stays in the document.
"A weekly meeting where everyone reports status is not a team meeting. It is a performance of busyness for an audience of peers."
The template operationalizes three principles. Every weekly meeting exists for specific decisions, not a vague "sync" (P1). The agenda is built around decisions and blockers, not topics (P4). And status updates belong in documents, not in rooms (P6).
The compound effect matters more than any single meeting. A team that runs 50 weekly meetings a year this way reclaims roughly 25 hours of collective time — the equivalent of three full working days — just by moving status to writing. And the meetings that remain are sharper, because everyone arrives already informed.
Every team member updates their section in a shared document. The team lead reads all sections before the meeting and builds the live agenda from what surfaces. Nothing in the pre-read gets recited aloud.
The team lead has read all pre-reads and built the agenda from what needs live discussion. The meeting opens with decisions, not updates.
Decisions (15 min)
Pull from the "Decisions / Input Needed" sections across all pre-reads. Each decision gets stated, discussed, and resolved — or explicitly deferred with a date. If no decisions surfaced this week, this block shrinks or disappears.
Blockers (10 min)
What's stuck and what can we unblock right now? The lead assigns owners, escalates, or connects people. Anything that can't be resolved in the room gets a follow-up owner and a deadline.
Dependencies & coordination (5 min)
Cross-team handoffs, shared deadlines, or work that affects multiple people. This is the only part where "awareness" is a valid meeting purpose — because coordination requires real-time alignment.
Capture & close (5 min)
Record every decision and action item in the shared document, on the spot. Who owns what, by when. Next week's pre-read starts from this document — creating a running record of team decisions.
Typical Team Weekly (45 min)
ED3 Team Weekly (35 min)
Switching from round-robin to pre-read-first requires resetting one expectation: the meeting is no longer where people learn what happened. The document is. Here's how to make the shift stick:
Set a hard pre-read deadline. End of day before the meeting. If the document isn't filled in, the team lead follows up — not during the meeting, but before it. The pre-read is the price of admission.
Never read updates aloud. If someone starts reciting their pre-read, redirect: "We've all read it — what do you need from us?" This is the hardest habit to break, but it's the whole point.
End early when there's nothing to decide. If no decisions or blockers surfaced this week, the meeting can be 10 minutes. Don't fill time just because you booked 45 minutes.
Keep the running document. Each week's pre-read and decisions append to the same document. Over time, it becomes a searchable history of team decisions — far more useful than anyone's memory of what was said in a room.
Download the template
A clean, tool-agnostic version your team can adapt to Google Docs, Notion, Confluence, or wherever you collaborate.