Turn One Recurring Meeting Into a Focus Block

The recurring meeting is the easiest debt to pay down

Open your calendar and count the meeting hours in a normal week. Do not count the work that happens around them: the prep, the follow-up, the chat thread that starts because someone missed a point. A recurring invite that nobody reviews becomes a cost you pay without noticing.

Say the meeting is a standing status check, and ask what would happen if the next version were a short document. When nothing important changes, the meeting is likely a habit, not a need.

Look for the meeting that repeats, has a standing agenda, and still produces decisions. A summary, a status update, or a list of owners is easier to replace than to defend. Choose the meeting that keeps eating the same block every week, even if it is not the most important one.

Done looks like this: you can name the meeting, the reason it repeats, and the work it is blocking. If you cannot say what the meeting is for, that is a strong sign it can be replaced.

A visible block is stronger than a private intention

Cancel the recurring invite with a short note: the meeting is moving to a written update, and the same time becomes protected work time. Do not apologize for the change. State what changes, what stays available, and where the team can still reach you.

Create the replacement block in the same slot. For organizations that use Google Calendar, check that your account can create native focus-time events, because Google Calendar limits native focus-time events to work or school accounts. As of September 2026, Google Calendar’s native focus-time events are offered to Business Standard/Plus, Enterprise Standard/Plus, Education, and Nonprofits, while personal Gmail and Business Starter are not included. You can create a focus-time event only while viewing the calendar in Day or Week mode.

Name the block clearly. A vague title invites overlap. A clear title tells people what is happening and why the time is protected.

Set the block to decline new invites during that time, if your tool supports it. When it is done, the slot is visible, the old invite is gone, and the team knows the written update replaces the meeting.

The mistake is making the block private. Only you can see it, and the team treats it as a preference, not a rule.

A focus block can carry the boundary for you

Connect the block to Slack focus mode. In September 2026, Slack can turn a Google Calendar focus block into focus mode, pause alerts, soften sidebar badges, and allow optional VIP exceptions. Focus mode also tones down the sidebar: bold text disappears, badges are limited, and notification volume drops.

Allow the one urgent exception: Slack allows one urgent direct-message override per day while notifications are paused. Tell the team that this is for true emergencies, not for questions that can wait until the block ends.

The pings go quiet, but the line is still a human decision. The tool reduces noise; you decide what counts as urgent.

Post the block where the team can see it, with a plain note: this time is for deep work, and the written update is the replacement for the old meeting. The arrangement is easier to keep when it is visible, specific, and tied to a real output.

Once set, the block is connected, and the exception is known.

A focus block needs review before it becomes another meeting

Check the written update that replaced the meeting. Keep the block when it is still useful. If it has become a place where people dump unfinished thoughts, tighten the format or move the discussion to a normal meeting.

Adjust the block when the work changes. A focus slot that protects a project can become a waste of time once the project ends. Move it, shorten it, or close it with the same plain note you used to create it.

Keep the exception narrow. The urgent override is for the rare problem that would hurt the team while it waited. The block loses its meaning as people start using it for normal questions. Say so plainly, and return to the written update.