A calendar can be quieter and a project can still be a mess. That is the part of the usual advice about how to reduce meetings that gets missed. Removing a standing call saves a visible block of time. It also removes the place where people used to discover blockers, negotiate priorities, and confirm decisions. If those jobs are not reassigned, the work comes back as confusing messages and emergency calls.
The useful target is not “zero meetings.” It is fewer meetings that merely transfer information, and better meetings when conversation is actually necessary. You can make that change with a small audit, a written update people can act on, and a clear route for decisions. No new software is required.
How to reduce meetings without losing decisions
Before canceling anything, ask what the meeting produces. A status call is supposed to produce a shared understanding. A review is supposed to produce feedback or approval. A kickoff is supposed to uncover assumptions. A difficult conversation may need trust and immediate clarification. Treating all four as interchangeable leads to bad substitutions.
This quick test helps decide the format for a specific agenda item:
- Is this mainly information? If the answer is yes, make it a short written update that people can read on their own schedule.
- Does one named person have authority to decide? Send that person a decision brief with a response date. Do not schedule five people because one signature is needed.
- Is the disagreement unclear, sensitive, or emotionally loaded? Keep a live discussion. Written messages are not automatically better when nuance matters.
- Do people need to create or troubleshoot something together? Keep a focused working session with the relevant people, rather than a ceremonial progress report.
- Would delayed replies create an actual deadline risk? Define an escalation path. Async communication is not a license to let a blocker sit unnoticed.
This is consistent with Atlassian’s “Think Before You Sync” play, which recommends choosing synchronous, asynchronous, or combined collaboration based on the work to be done. The decision test above is AWL’s own practical adaptation, not Atlassian’s five-question list.
Audit one recurring meeting before touching the whole calendar
Start with a meeting you can influence, ideally a recurring project check-in with a familiar group. Review the last two or three occurrences. For each, record what actually happened rather than what the invitation said would happen. A meeting called “alignment” might have been 20 minutes of status reading and five minutes of a real decision.
Copy this table into a document or spreadsheet. One row is one recurring meeting, not one attendee.
| Meeting | What changed last time? | Essential live work? | Replacement or change | Owner and review date |
|---|---|---|---|---|
| Monday project check-in | Three status reports; one blocked approval | Approval only | Written update plus decision request | Project owner; two weeks |
| Client discovery call | Uncovered conflicting goals | Yes | Keep; circulate questions beforehand | Project lead; next call |
| Weekly design review | Feedback on annotated files | Sometimes | Collect written comments first; call only for unresolved items | Reviewer; after two cycles |
Illustrative entries only; they are not records of an AWL audit.
Do not use “no decision” as the only test of usefulness. Relationship-building, difficult feedback, and identifying a problem early can be valuable outcomes, even when there is no action item to check off. Also consider who would lose access or context if the meeting vanished.
For a larger organization, Atlassian’s meeting-audit play offers a team workshop approach. A solo operator or small client team can use the smaller table above without adopting the entire process.
Choose the replacement: a small format comparison
Replacing a meeting with “just send me an update” is too vague. Decide what information must be available, where it lives, and when a reply is due.
| What the meeting did | Better first option | When to keep a call |
|---|---|---|
| Routine project status | One weekly written status note | Several blockers must be resolved together |
| One-person approval | Decision memo with options and deadline | Approver needs a live walk-through |
| Document feedback | Comments linked to exact passages | Comments expose conflicting interpretation |
| Project kickoff | Pre-read plus focused kickoff | Usually: the conversation surfaces unknowns |
| Emergency troubleshooting | Named escalation route, then incident note | Immediate coordinated action is required |
When people work in different time zones, the response window matters as much as the channel. AWL’s guide to working across time zones with clients explains how to define overlap and handoff expectations rather than treating every message as urgent.
Copyable weekly async status update template
Use one update per project, not a collection of disconnected “just checking in” messages. Keep the note scannable enough for a reader to identify what changed and whether they owe you something.
Project: [project name] · Week ending: [date]
Status: [on track / at risk / blocked, with one-sentence reason]
Completed: [meaningful outcome, with link to the actual file]
Next: [next action, owner, target date]
Needs a decision: [specific question, two realistic options if useful]
Decision owner / reply by: [name and date, including time zone if needed]
If no reply: [what will pause, or which safe default was explicitly agreed]
Source of truth: [project document, task, or folder link]
“At risk” is better than “all good” when a client approval is late. The note should not quietly assume that silence means permission to proceed with paid work, scope changes, or irreversible decisions. A default can be used only when it was agreed beforehand and is appropriate for the decision.
If you want a more compact email-only format, see AWL’s asynchronous communication guide. The key is that the reader can answer the request without reconstructing the entire project from old threads.
Copyable decision brief for work that should not need a meeting
A status update says where work stands; a decision brief asks someone to choose. Mixing them together makes important requests easy to miss. A small decision brief can be as simple as this:
Decision needed: Approve the revised landing-page headline?
Context: The current headline does not name the target audience; the rest of the page is unchanged.
Option A: Keep the current headline. No revision required.
Option B: Use the clearer audience-specific headline attached here.
Recommendation: B, because it makes the page’s intended reader easier to identify.
Trade-off: B needs one copy update and a final proofread.
Owner / response date: [name] by [date, time zone]
If undecided: Hold publication and raise it at the next agreed check-in.
This is a hypothetical copy decision, not a tested outcome. For material changes to budget, legal commitments, permissions, or customer data, choose an appropriately documented approval path. A simple emoji acknowledgment may not be enough.
Good work documentation makes the chosen option retrievable later. Record the date, who approved, what was approved, and where the final artifact lives. You are replacing an implicit memory of a conversation with a usable record.
When a meeting stays, send a shorter invitation
A meeting can be smaller without being less respectful. Tell participants what must happen in the room and let them read the context in advance. Avoid inviting everyone who has ever touched the project.
Subject: Resolve two launch blockers (20 minutes)
Decision or output: Agree on the owner and sequence for the two blockers.
Read first: [current status document]
Agenda: 5 minutes confirm facts, 10 minutes resolve options, 5 minutes assign next actions.
Needed: [decision maker] and [person with technical context].
Afterward: A short decision note will go to the wider group.
Use the duration as a starting estimate, not a promise. A delicate discussion may need more time. If someone with necessary context cannot attend, collect their input first or reschedule rather than forcing a premature decision.
Run a two-week experiment, not a permanent meeting ban
Try the new process with one recurring status meeting for two cycles. The goal is to find out whether the work remains clear, not to announce a percentage reduction in meetings. These are steps to try, not results AWL has measured.
- Before week one: Ask the meeting owner and affected participants for agreement. List what the meeting currently accomplishes, how urgent issues should be escalated, and where updates will be posted.
- Week one: Replace the meeting with the weekly status template. Keep a short optional discussion window for genuine unresolved questions. Track whether a decision stalled.
- Midpoint: Ask two questions: “Did you know what changed?” and “Was it clear when you needed to act?” If either answer is no, fix the update format.
- Week two: Repeat with clearer ownership, fewer background details, and an explicit response date. Do not add a second tool unless the first place genuinely cannot hold the information.
- Review: Compare the time spent in the original meeting with the time needed to write, read, clarify, and follow up. Also note delayed approvals, surprise blockers, and stakeholder frustration.
A simple review record might look like: Meeting removed? yes/no; New writing and follow-up time? estimate from actual work; Missed decision? yes/no and why; Participants still informed? feedback; Next action? keep, revise, or restore. Do not label the experiment successful merely because the calendar has an empty slot.
What could go wrong when you reduce meetings?
Everyone receives an update, but no one owns the decision
Make the decision owner and requested response explicit. The phrase “let me know your thoughts” often hides the fact that approval is required. If several people must approve, list them and the order in which they should respond.
The async thread becomes an endless miniature meeting
If three rounds of writing reveal that people disagree about the problem itself, switch formats. Schedule a brief call with the smallest useful group and put the result back in the shared record.
A stakeholder loses visibility when the meeting disappears
Keep a consistent home for updates and include the relevant audience. Ask which part of the old call helped that person, then preserve that function. Some clients genuinely value regular relationship contact; an occasional purposeful call may be better than forcing every interaction into a document.
Urgent work sits in a slow response queue
Agree on what “urgent” means, the contact path, and a fallback if the owner is unavailable. Reserve urgency for real deadline or safety consequences rather than labeling every preference urgent. The distinction is particularly important across borders and time zones.
A practical checklist before you cancel the next meeting
- ☐ I know what the existing meeting accomplished, not only what its title claimed.
- ☐ A named person owns each decision, blocker, or approval formerly handled live.
- ☐ Participants know where the written update will appear and how often.
- ☐ Requests have context, a due date, and an agreed escalation route.
- ☐ Sensitive or ambiguous work retains an appropriate live discussion.
- ☐ The trial has a review date and a way to restore the meeting if clarity gets worse.
If this feels like more structure than the meeting required, remember the alternative: people were already spending time reconstructing the same context verbally. The point of the written process is not to create paperwork. It is to make the next action findable without another call.
For background on why an async-first approach requires deliberate communication rather than silence, see AWL’s asynchronous work guide. A useful outside reference is Atlassian’s research-informed discussion of replacing status and decision meetings. Those sources support the general approach, but the templates and two-week trial described here are editorial suggestions, not a published benchmark.
The decision to make today
Pick one standing call you own. Identify the one thing it must accomplish this week. If a written update, decision owner, and reply date can accomplish that job, trial the replacement and check what breaks. If the meeting is where the real problem is understood, keep it and make it more focused. That is how to reduce meetings while leaving the work, and the people doing it, better informed.
