How to Prepare a Weekly Team Meeting When Nobody Has Time

Most weekly meetings are prepared the same way. On Friday afternoon, one person opens last week's deck, scrolls Slack and the board for anything that looks important, and writes a slide for each team. They are guessing at work they did not do, and they are usually guessing well enough that nobody complains.

The result arrives on Monday as a finished document. Everyone else reads it for the first time in the room, which is the moment they stop being participants and become an audience.

It is tempting to treat this as a workload problem and hand the deck to someone with more time. That misses what actually goes wrong. The person assembling the deck has to compress work they only half understand, so nuance disappears and the slide says shipped the integration when the real news is that the integration shipped without the retry logic and someone should decide whether that matters.

Atlassian's survey work found that a small number of voices dominate most meetings, and that people frequently leave without knowing what happens next. Those are self-reported perceptions rather than measurements, but they match the mechanics of a single-author deck: the author speaks, everyone else confirms, and decisions that needed the person closest to the work never get made.

We think preparation is where participation is decided. By the time the meeting starts, the question of who is involved has already been answered by who wrote the material.

Distributed preparation is not free. Ten people writing three lines each is a real interruption on a Friday, and it needs chasing in the first month, because writing something that will be read out on Monday is more exposing than sitting quietly in a call.

It also produces a rougher meeting. A single author makes the week sound coherent; six contributors make it sound like six people's weeks, because that is what it was. In our experience that roughness is the point, but it reads as a downgrade for the first few weeks, and it is worth saying so out loud before you start.

Some meetings should stay authored by one person. Anything with an external or board audience needs a single voice and a consistent argument. Announcements about restructuring, redundancies or strategy changes should be written and delivered by the person accountable for them, not assembled from contributions.

The same is true of teams in genuine crisis: when an incident is running, coordination beats participation, and one person holding the thread is faster. And in teams below roughly five people, the overhead of a preparation rhythm exceeds what it saves — just talk to each other.

Distributed preparation earns its keep in the recurring meeting where several teams need to hear from each other, and where the current version has one narrator and a silent room.

Try it once. Write the agenda as decisions on Thursday, ask three people for three lines each on Friday, and let them speak to their own material on Monday. If the meeting is worse, you have lost thirty minutes and learned something about your team's appetite for writing.

Keeping the rhythm going is the harder half, which is where a structure helps: Curact collects the week's changes, asks each named person for their own lines, and assembles what comes back into the meeting. The rhythm matters more than what runs it.