The Meeting That Should Have Been an Email Was Probably Also a Bad Meeting

Matthew Clement March 17, 2026 8 min read
The Meeting That Should Have Been an Email Was Probably Also a Bad Meeting
A Monday meeting in an ordinary Seoul office: one person presents from a laptop while others check phones, type, stare out of the window or rest a chin on a hand; one younger employee takes notes.

The Meeting That Should Have Been an Email Was Probably Also a Bad Meeting

The standard complaint about unnecessary meetings misses the more interesting problem. Most bad meetings are bad because of what happened before anyone entered the room. The complaint about meetings that should have been emails has become so common in professional culture that it has turned into ambient background noise: present in every workplace, acknowledged by everyone, acted on by almost nobody. The complaint is also slightly wrong, or at least incomplete. The meeting that should have been an email is a symptom. The underlying condition is the absence of clarity about what the meeting is for, which is the same condition that produces bad emails, bad presentations, and bad briefs. A meeting without a clear decision to make or a clear problem to solve is not a meeting. It is a gathering. Gatherings can be valuable: they build relationships, create alignment, and give people a sense of shared context. But a gathering scheduled in the format of a decision making meeting produces a specific kind of frustration: the people who came expecting to decide something leave without having decided anything, and nobody is quite sure whose fault that is. The fix is not to replace the meeting with an email. The fix is to answer one question before scheduling anything: what specific outcome will exist after this interaction that does not exist before it? If the answer is a decision, a meeting with the right people and a clear agenda is probably correct. If the answer is that someone will be informed, an email or a document is almost certainly better. If the answer is that people will feel more connected or aligned, a meeting might be right but should be framed honestly as what it is: a gathering, not a decision session. The email that should have been a meeting is also real. The thread that has accumulated fourteen replies and still has not resolved a decision that needed three people in a room for twenty minutes: that is a meeting that should not have been an email. The format is the last question, not the first. What outcome do we need? Who needs to be involved to produce it? How much synchronous interaction does that require? The format follows from those answers. Most workplaces get this backwards. → Short reads like this land in your inbox monthly on The Briefing. Subscribe using the link at the top of the page.

Frequently Asked Questions

When should a meeting have been an email instead?

A Worked Example: Rewriting One Meeting Invite

Here is the one question applied to a real kind of invite. Daeun leads an operations team of nine at a logistics platform in Pangyo. Every Monday at 10 there is a 60 minute 주간 회의 on everyone’s calendar. Half of it is people reading out updates that are already in the tracker. The other half is the one live problem of the week, which this month is whether to switch carriers on the Busan route before the year end peak. That decision has now been discussed on three Mondays and made on none of them.

One meeting invite, rewritten around a decision

An illustrative weekly meeting invite from a logistics team lead in Pangyo.

판교 물류 회사 팀장이 보내는 주간 회의 초대장. 수정 전과 후를 비교한 예시.

Before · 수정 전

Weekly sync. Monday 10:00, 60 min. All nine team members. Agenda: updates, AOB.

No outcome, nine people, and the real decision hidden under updates.

결과물이 없고, 아홉 명이 모이며, 진짜 안건은 업데이트 밑에 묻혀 있다.

After · 수정 후

Decide: Busan carrier from November. Monday 10:00, 25 min. Ops, finance, Jiyeon. Read first: two quotes, attached.

One decision, three people, one pre read. Updates move to a written note.

결정 하나, 참석자 셋, 사전 자료 하나. 업데이트는 서면으로 돌린다.

A CareerComms example.

The new invite does three things the old one did not. Its title states the outcome, so anyone who reads only the calendar knows what will exist after the meeting. Its attendee list is the people needed to make that decision, not everyone who might be interested. And the updates, which never needed anyone to hear each other, move into a short written note on Monday morning. The other six people get an hour back. How to write that note so it does one job is in One Email, One Job.

Choosing the Format Before You Schedule Anything

The questions above can be laid out on two axes: does this need a decision, and do the people involved need to hear each other in real time? Every recurring meeting on your calendar sits in one of the four squares.

Four kinds of work, and only one of them is a meeting

Place any meeting on two questions before it reaches the calendar.

일정에 넣기 전에 모든 회의를 두 가지 질문 위에 놓아 본다.

Needs a decision 결정이 필요한가 ↑

Email with an ask

A decision one person can make. Send a yes or no question with a deadline.

한 사람이 내릴 수 있는 결정. 기한을 정해 예, 아니오로 답할 질문을 보낸다.

Meeting

A decision that needs live disagreement. Few people, a short slot.

실시간으로 이견을 나눠야 하는 결정. 적은 인원, 짧은 시간.

Written update

Information only. A note or a shared document does it better.

정보 전달만 필요하다. 메모나 공유 문서가 더 낫다.

Gathering

Connection, not decisions. Hold it, but name it honestly.

결정이 아니라 관계를 위한 자리. 열어도 좋지만 솔직하게 이름 붙인다.

Needs people to hear each other 서로 들어야 하는가 →

A CareerComms framework.

Daeun’s Monday meeting was two squares pretending to be one: a written update in the bottom left and a real meeting in the top right. Splitting them is most of the fix. Gatherings deserve a word too, because in Korean teams they matter. A monthly team lunch or a short catch up builds the trust that makes the decision meetings work, and there is nothing wrong with holding one, as long as nobody is told it is a decision session.

The Korean Angle: Why the Status Meeting Survives

Korean companies have measured this problem. In a Korea Chamber of Commerce and Industry survey of 1,000 employees at listed companies, reported by 디지털타임스 in February 2017, staff rated their meetings 45 out of 100. They attended an average of 3.7 meetings a week at 51 minutes each, and said 1.8 of them were unnecessary. The most common reason, at 32.9%, was that the meeting existed only to check work and share information, and 61.6% said the boss dominated the talking.

That most common reason is the bottom left square of the grid, held in person. It survives partly because 보고 in a Korean team is also a way of showing presence to the person above you, which I wrote about in How Korean Workplace Hierarchy Actually Works. And silence in the room is not always agreement, as the part of Korean professional communication nobody puts in the training manual explains, so a decision meeting where the senior person does most of the talking may never surface the disagreement it exists for. The practical move is to keep the 보고, but in writing, and protect the meeting for the decision.

Turning a Status Meeting Into a Written Update

The FAQ below suggests proposing the change as a two week experiment. Here is what that experiment looks like when you actually run it.

Trial a written update in four steps

A two week experiment for any recurring status meeting.

반복되는 현황 공유 회의에 적용해 보는 2주짜리 실험.

01

Name the outcome

Write the one decision the meeting exists to make, or admit there is none.

이 회의가 내려야 할 결정 하나를 적는다. 없다면 없다고 인정한다.

02

Move the updates

Updates go in a shared note by Monday 9:00, three lines each.

업데이트는 월요일 9시까지 공유 문서에 한 사람당 세 줄로 올린다.

03

Keep a short slot

Hold 25 minutes only for decisions the note raises.

문서에서 나온 결정 사항만 다루는 25분을 남겨 둔다.

04

Review together

After two weeks, decide as a team whether to keep it.

2주 뒤, 이 방식을 계속할지 팀이 함께 정한다.

A CareerComms framework.

The step people skip is the last one. Deciding together is what makes the change stick in a hierarchy, because it turns the senior person’s agreement into the team’s decision rather than a junior colleague’s complaint. There is outside evidence that cutting meetings can help. In a study of 76 companies, each with more than 1,000 employees, published in MIT Sloan Management Review in January 2022, the authors reported lower stress and less micromanagement after companies introduced days with no meetings, with the best results at companies that had three such days a week.

Most teams will not go that far, and do not need to. Moving one status meeting into writing is enough to show whether the format was the problem. If the people on the call are hard to read, Group Dynamics helps you read who actually decides, and if the meeting has to happen on screen, How to Look Present and Confident in a Korean Video Call covers the rest. For the note itself, Copy Check gives the draft an honest score before it goes out.

The inbox your message lands in

What an average knowledge worker receives on a normal workday.

평범한 하루, 사무직 한 사람이 받는 메시지의 양.

Email
117

Average emails received each day, most skimmed in under a minute

하루 평균 이메일. 대부분 1분 안에 훑고 넘긴다

Messages
153

Average Teams messages received per weekday

평일 하루 평균 팀즈 메시지

Interruptions
275

Pings a day from meetings, emails and chats

회의·이메일·채팅으로 인한 하루 방해 횟수

Focus
2min

Average time between interruptions during core hours

핵심 업무 시간 중 방해 사이의 평균 간격

Source: Microsoft Work Trend Index, Breaking down the infinite workday, June 2025. Microsoft 365 signals to 15 Feb 2025; survey of 31,000 workers in 31 markets.

The volume behind that instinct is now documented. Microsoft’s 2025 Work Trend Index puts the average knowledge worker at 117 emails a day and 153 Teams messages per weekday, interrupted every two minutes during core hours. In Korea the engagement side of the picture is worse: Gallup’s State of the Global Workplace 2026, South Korea data finds 13% of employees engaged, against 20% globally, which is the audience your meeting invitation lands on. A meeting should have been an email when the purpose is one way information transfer, when no decision needs to be made in real time, when the participants are not all required to hear each other, or when the output is a status update rather than a conclusion. If you cannot name a decision the meeting exists to make, the meeting is probably an email.

Why do bad meetings persist even when everyone complains about them?

They persist because meetings are measured by presence rather than outcome. The status meeting that accomplishes nothing is still on the calendar next week because cancelling it would require someone to admit it accomplishes nothing, and the cost of that admission is higher than the cost of another hour of everyone’s time. This is a communication and incentive problem.

What makes a meeting actually worth holding?

A meeting is worth holding when a specific decision needs to be made, when real time disagreement needs to surface, when relationship building requires physical or video presence, or when the information is sensitive enough that it should not exist in written form. Outside those cases, most meetings can be replaced with a well structured document or email.

How do I propose turning a recurring meeting into an email?

If you want to tighten the written communication you do send, the Copy Checker is worth a run… or work with us on the communication systems that determine how your team’s time actually gets used.

Propose it as an experiment, not a permanent change. Something like: for the next two weeks, let us trial replacing the Monday status with a written update, and reconvene to decide. This reframes it as a low cost test rather than a challenge to the meeting’s necessity. Most teams discover the email serves them better and quietly keep it.
Cite This Article

CareerComms. “The Meeting That Should Have Been an Email Was Probably Also a Bad Meeting.” CareerComms, 2026, https://careercomms.com/meeting-that-should-have-been-email/.

Quotation with attribution and a link is welcome. Republication without permission is not.

STAY SHARP

Get career frameworks, not career advice.

Practical tools and structured thinking for your next career move. New posts, tools, and resources — no fluff, no filler.

Get updates →

Try it now, no signup

The Countdown, Korean

The interview countdown built for Korean companies: what they ask, in the order they ask it.

Open the tool →

The Briefing, Twice A Month

One idea, one tool, one thing happening in Seoul. No filler, unsubscribe in one click.

Subscribe free →
CareerComms
CareerCommsTwenty five years in business communication, marketing and branding, twenty four of them in Seoul. Written by a university lecturer and consultant; the frameworks here are the ones we teach with. About · For companies

Similar Posts