Knowles Knowledge Centre•Terminology

Email vs Chat, Meetings and Shared Documents

Four channels, heavily overlapping, chosen by habit rather than by cost. Here is what each one is good at — and which to reach for when.

The four are not synonyms, but nor are they cleanly separate choices. Chat resolves something small now, between one or two people, and leaves little behind. A meeting settles something that needs several people present at once. A shared document holds something several people change over time. Email asks named people for something and leaves a record, and costs every recipient a share of their attention whether or not they were needed.

Choosing the wrong channel is not a semantic problem. It leads to a disagreement about judgement being conducted in writing across nine people, or to a document that eleven people are editing by attachment.

Comparison guide•For HR and L&D teams•Updated September 2026

About this guide

Published byKnowles Training Institute
PurposeSelecting the channel that costs the pair least
Use beforeSetting a team’s norms about what goes where

The four channels

Each has a defensible use. The trouble starts when one is chosen by reflex.

ChatResolving something small, now, with one or two people: short turns, presence, fast loops, almost no record. Its output is a quick answer, and its unit is the exchange. It is cheap when it replaces an email and expensive when it interrupts.
MeetingSettling something that needs several people in the same moment: real-time disagreement, a decision reached in front of everybody who is bound by it. Its output is a decision, and its unit is the hour. It is the most expensive channel per minute and sometimes the cheapest overall.
Shared documentHolding something several people change over time: one current version, comments beside the text, a history of what changed. Its output is a current artefact, and its unit is the version. Its great advantage is that it costs nobody’s inbox anything.
EmailAsking named people for something, with a record: an addressed ask, a date, a stated default, a closing line. Its output is a response and a trail, and its unit is the message. It is nearly free to send and is paid for by everybody who opens it.

Inclusions, exclusions and overlaps

What each channel covers, what it explicitly does not, and where it shares ground with the others.

Includes

Excludes

Overlaps with

Chat

Small questions, quick confirmations, immediate unblocking

A record anybody will find in six months

Email, for anything that needs addressing

Meeting

Disagreement, judgement, decisions several people must own

Anything one person could simply decide

Email, for the decision record afterwards

Shared document

Drafts, registers, anything with many contributors over time

Getting a specific person to do a specific thing by a date

Email, for the ask that points at it

Email

Addressed asks with a date, a default and a record

Real-time disagreement; collaborative editing; chatter

All three of the above, by default

The fourth row is the reason for the confusion: email will carry anything, badly, and is the channel that requires no decision about which channel to use, which is exactly why so much of what belongs in the other three ends up in it.

Why the terms get confused

This is a known problem with a name.

The US Institute of Education Sciences calls it the jangle fallacy: assuming that two things are different because they carry different names. “Email etiquette,” “business writing,” “written communication” and “correspondence skills” describe substantially the same territory with different emphasis and different marketing.

Two practical consequences follow. First, a provider offering “business writing” and one offering “email etiquette” may be selling the identical course, and comparing them on the title tells you nothing. Second, an organisation searching for one term will miss relevant provision listed under another.

The reliable test is not the label. Ask what the channel costs in aggregate and what it leaves behind — an interruption with no record, an hour of several people, a version everybody can see, or a message in nine inboxes with a trail. Two providers using different vocabulary will answer that very differently, or one of them will not answer it at all.

Choose this when…

The decision matrix. Match the situation on the left to the channel, not the other way round.

If the situation is…

…then the need is

Typical intervention

One person can answer in a sentence and you need it now

Chat

One exchange, no record kept, and no third party involved

People disagree about judgement and have to own the outcome

Meeting

An hour with everybody bound by it present, then a one-line record

Several people will change the same thing over weeks

Shared document

One current version with comments, and no attachments in anybody’s inbox

Named people must do something by a date, and it must be traceable

Email

The ask, the date and its reason, a stated default, a closing line

Somebody has to be told something difficult

Not the cheapest channel

A conversation. The expense is the point, and writing it will cost more later

Nobody knows who owns the decision

Not a channel problem

Settle the ownership; the traffic is a symptom and every message is well written

The last two rows exist because the two commonest errors are using the cheap channel for something that needed the expensive one and treating unclear ownership as a communication problem. A method for testing the second is set out in how to identify whether email is costing your team more than it saves.

What goes wrong when the channel is mis-selected

Three failure patterns account for most of the wasted attention in an organisation.

1

Conducting a disagreement by email

Email has no turn-taking, no tone and no interruption, so a disagreement in it proceeds by each party restating a position more fully to a widening audience. Nothing about the medium is suited to it, and the audience makes retreat expensive for everybody. The hour-long conversation that would have settled it was the cheap option, and it was declined because an hour has a visible price and nine people reading a thread for a week does not.

2

Circulating a document that several people must change

An attachment becomes a version, and eleven people with versions produce a reconciliation nobody has volunteered for. The inbox cost is incidental; the real loss is that nobody can say what the current text is. A shared document answers the question at no cost to anybody’s attention, which is why this error is almost always a matter of habit rather than of judgement.

3

Using email because no choice was required

Email is the channel you reach for when you have not asked which channel this is. That is its defining property and the source of most of its volume: every other option requires a decision, and email requires only an address. The remedy is not restraint but a rule a team has made about what goes where, which converts the choice from an act of discipline into a default.

A practical warning about provider language

Providers choose whichever label is currently attractive, and the same content is sold as business writing, email etiquette or written communication depending on the year. Judge a proposal on whether a team’s recipient counts and reply counts change afterwards — never on the title.

Frequently asked questions

?
Is chat just faster email?No, and the differences cut both ways. Chat is cheaper when it replaces a message that would have reached nine people, and considerably more expensive when it interrupts somebody mid-task for something that could have waited an hour. It also leaves almost no record, which makes it the wrong channel for anything a third person will need later.
?
Should meetings replace email threads?Where there is genuine disagreement about judgement, usually yes, and the arithmetic supports it: an hour with six people costs six hours and settles the matter, where a thread costs comparable attention and settles nothing. Where somebody simply has to be told something, a meeting is the expensive channel and email is correct.
?
Which channel should a team standardise on?None, and the standardisation that matters is about the boundaries rather than the channel: what never goes in email, what always does, who closes a thread. A team that has agreed three rules of that kind will have a quieter inbox than one that has moved to a new platform, which is the move organisations usually make instead.
?
Do shared documents reduce email?Only where the email they replace was carrying versions, and only if the notifications are turned down. A document platform that mails every comment to every contributor has recreated the thread with extra steps, which is a configuration decision rather than a property of the tool.
?
Can one channel do all four jobs?Email can, badly, which is the whole problem. It will carry a quick question, a disagreement, a draft and an ask, and it costs every recipient the same whichever of those it is carrying. Scope each to the channel that costs the pair least, and agree the boundaries as a team rather than relying on individual judgement.

Conclusion

The four channels describe overlapping territory with different emphasis.

ChatQuick, now, no record
MeetingSeveral people, at once
Shared documentOne current version
EmailAn addressed ask, with a trail

The practical value of getting this right is not precision for its own sake. Each channel implies a different cost, a different record and a different set of people who pay for it.

Email is the channel chosen when nobody asked which channel this was.

The five-stage structure underlying the method is set out in what an email costs the person who opens it. Organisations that have established that sender behaviour rather than an expectation is the constraint can review the Writing Effective Emails Training Course in Singapore.