Meridian

Work & Life

The meeting that should have been a document

Writing things down is slower than talking and far better for thinking. Teams that adopt it never go back.

Priya Nair Work & Business Correspondent
  • Published
  • Updated
  • 2 min read
  • 2k views
  • 105 likes
  • 0 comments
Abstract artwork in plum tones with overlapping circles and fine horizontal lines
Illustration generated for Meridian
In this article
  1. Why writing beats talking for some jobs
  2. What belongs in a meeting
  3. How to make the switch
  4. Common objections
  5. The payoff

Everyone has sat in the meeting. Twelve people on a call, one person speaking, the rest half listening while answering messages. At the end, nobody is sure what was decided.

A small but growing number of organisations have quietly replaced many of these gatherings with something older and calmer: a written document.

Why writing beats talking for some jobs

Speaking is fast but fleeting. Writing forces you to organise your thoughts, and it leaves a record. A document can be read at the reader's pace, reread when needed and shared with people who were not there.

Writing also makes weak ideas visible. It is much harder to hide vagueness in a paragraph than in a confident voice.

What belongs in a meeting

Not everything should be written. Live discussion is better when emotions run high, when trust is being built or when a problem needs rapid back and forth.

  • Status updates: write them.
  • Information sharing: write it.
  • Brainstorming and sensitive conversations: meet.
  • Decisions: write the proposal, then meet briefly to resolve disagreements.
Use meetings for what only conversation can do.

How to make the switch

Start with a recurring meeting that mainly reports information. Replace it for four weeks with a short document in a shared folder and ask people to add comments before a set time.

Keep the format simple: what changed, what is blocked, what you need from others. Aim for something readable in five minutes.

Common objections

People worry that writing is slower and less personal. It is slower for the writer and faster for everyone else. As for the personal touch, many teams keep a short social meeting while dropping the status ones.

Another concern is that nobody will read it. That is usually a sign the document is too long, or that expectations were not clear.

The payoff

Teams report fewer interruptions, better handovers and decisions that people can trace months later. New colleagues can read their way into the context instead of asking for a recap.

Time saved is not the biggest benefit. Clarity is.

Did this help you think?

Keep reading

Conversation (0)

No comments yet. Add the first thought — thoughtful replies are always welcome.

Join the conversation

Never published.