Your Calendar Has Ghosts

The meeting starts at ten.

No one knows why.

The deck is open. The updates go round.

Nothing is decided.

Next week is already booked.

This is how a temporary need becomes a permanent tax. A launch gets messy, so someone creates a weekly call. The launch ends. The call remains. New people join and assume the meeting must matter because older people keep attending it.

Soon, the ritual has no owner, no live question, and no way to die. It survives on the strongest force in office life: nobody wants to be the first person to ask whether everyone is wasting their time.

You may think the problem is poor facilitation. So you tighten the agenda, shorten the updates, and add a timer. The useless meeting becomes brisk.

That is efficiency applied to a corpse.

A meeting does not earn its place by running well. It earns its place by doing work that needs these people, together, now. If that need disappears, a perfect agenda only makes the waste look disciplined.

Repetition Looks Like Importance

The first meeting probably made sense. There was uncertainty to cut, conflict to surface, or a decision too tangled for a thread. People left with clarity, so the organizer made it recur.

That small click changed the burden of proof. A one-time meeting must justify why it exists. A recurring meeting quietly demands that someone justify why it should stop.

Most people will not. Declining can look detached. Canceling can look careless. Asking for the purpose can sound like a challenge to whoever invited the room. So everyone pays a little time to avoid one awkward sentence.

The calendar turns that politeness into architecture. The box reappears, attendance becomes normal, and normal begins to feel necessary.

Atlassian's meeting audit starts by listing recurring meetings and deciding which should stay live, move to async work, or change. The useful part is not the template. It is the admission that calendar rituals need review because they do not review themselves. Their playbook recommends repeating the meeting audit as calendars fill again.

A recurring invite is not proof of recurring value. It is merely a machine that keeps producing an appointment.

Status Is Not a Reason

Ask why the meeting exists and someone will usually say alignment. That word is useful because it sounds important while hiding the actual job.

Alignment about what? A choice? A risk? A handoff? A change in direction? If the room cannot name the thing that becomes possible after the call, alignment may mean watching people read information that could have been written down.

Live time is expensive for a simple reason: it requires everyone to pay at once. A written update can wait for the right reader. A meeting interrupts every attendee at the same minute, then asks the rest of their day to absorb the cut.

This does not make meetings bad. Some work needs fast challenge, shared judgment, or a decision made in the presence of competing facts. The mistake is using the most costly form of coordination for information that does not need a room.

Atlassian's page-led meeting guidance gives live discussion a clear center: written context, a stated goal, and the key decisions prepared before the conversation. The page is not more paperwork. It is a test. If you cannot name the decision the room must move, the room may not need to meet.

This is where you feel the resistance. The weekly call keeps everyone informed. Without it, things might slip.

Good. Name what might slip. Give that risk an owner, a signal, and a place to be seen. If the only thing holding the operation together is compulsory attendance at a vague conversation, you do not have alignment. You have a ritual covering a missing system.

Put the Meeting on a Lease

Permanent meetings are born from temporary fear. Replace permanence with a lease.

Every recurring meeting should carry four terms:

• Job. Name the decision, conflict, or shared work the meeting exists to move.
• Trigger. State what must be true for the meeting to happen this time.
• Proof. Define what should exist when the meeting ends.
• Expiry. Set the date when the series must defend itself again.

Job prevents “alignment” from passing as an answer. Trigger stops the group from meeting when there is nothing live to resolve. Proof separates a useful conversation from a pleasant recital. Expiry restores the burden of proof to the meeting.

Imagine the weekly launch call. Its job is to clear decisions blocking the release. Its trigger is at least one unresolved issue that crosses team lines. Its proof is a named decision, owner, and next move. Its expiry is the release date.

If no trigger fires, cancel it. If the proof is never produced, redesign it. When the expiry arrives, delete the series unless a new job earns a new lease.

This is not radical. It is how you treat every other cost you respect. You would not keep paying for software because it was useful during a launch two years ago. The calendar escapes the same scrutiny because the bill arrives in pieces of human attention.

Let the Empty Space Stay Empty

Canceling the meeting creates a strange gap. People rush to fill it with a new channel, a new form, or an async ritual nearly as heavy as the call. Resist that reflex.

Replace only the job that still exists. If people need a status record, create one small written update with a clear owner. If they need decisions, define where a blocked choice goes and who can make it. If they need no replacement, let the hour disappear.

Atlassian's calendar redesign guidance uses a clean test: if a meeting is not collaborative, decision-driving, or valuable enough, consider declining and offer an async path when one is needed. The point is not to wage war on conversation. It is to protect time for work while keeping a deliberate way to stay informed.

The hardest part is not deleting the invite. It is accepting that an open hour does not need to announce what it produced.

A meeting is visible. Focus is private. That makes the meeting easier to defend in a culture that confuses witness with work. Eight faces on a screen look like coordination. One person thinking without interruption looks like nothing.

Let it look like nothing.

Tomorrow, open the oldest recurring invite on your calendar. Ask for its job, trigger, proof, and expiry. Do not improve it yet. First make it earn the right to exist.

Perhaps the meeting survives with a sharper purpose. Perhaps it becomes a short written note. Perhaps you press delete and feel the mild panic of removing something everyone had learned to obey.

The next Tuesday arrives. The box is gone. Nobody misses the update. No decision stalls. No hidden disaster appears.

Someone uses the hour to finish the work the meeting used to interrupt.

The calendar is quieter now. Not empty. Alive. Every meeting still on it has a job, and the ghosts no longer get a vote.