Deciding What Deserves A Call And What Deserves A Message

Your calendar is full of meetings that could have been three sentences. Meanwhile the one thing that genuinely needed talking through has been going back and forth in a thread for four days.

Here is the test. Call when two or more people already disagree, or when the decision is expensive to undo. Message for everything else. Two questions, asked before you book anything, and most of the argument about meeting culture goes away.

The two questions

How many people currently disagree?

If nobody disagrees, you are sharing information. Information travels fine in writing and travels better, because people can read it twice.

If two people disagree, writing usually makes it worse. Each reply gets longer and more careful, positions harden, and tone gets read into sentences that had none. Ten minutes on a call beats two days of paragraphs.

How expensive is this to undo?

Cheap to undo means try it and see. Change a label, adjust a schedule, rename a file. Write it down and move.

Expensive to undo means a call. Choosing a database, committing to a delivery date with a client, changing how a team is structured, agreeing a price. These are decisions where being slightly wrong costs weeks.

The rule, written so anyone can quote it

Put this somewhere the team can point at:

If two or more people already disagree, or the decision would be expensive to undo, book a call. Otherwise write it down.

A rule only works if people can repeat it without looking it up. This one fits in a sentence, which is the point.

What this looks like in practice

Message:

• Status updates. Anything that answers "where is this".
• Sharing a document for comment.
• Any question with one correct answer.
• Announcements. Everybody needs the same words, and a call gives each person a slightly different version.
• Anything the person receiving it will need to refer back to.

Call:

• Two people have replied with different views and neither has moved.
• A decision that commits money, dates or headcount.
• Feedback on someone's work that goes beyond a small correction.
• Anything where you are unsure how it will land.
• The first conversation about a hard problem, where nobody knows the shape of it yet.

The case writing handles better than people expect

There is a habit of booking a call because it feels faster. It is faster for the person booking it and slower for everyone else. A call booked for Friday afternoon in the UAE reaches half a team, because Friday is a half day.

Writing has three advantages that a call cannot match. The people who were asleep can read it. The decision exists afterwards in a form you can search. And a person who needs a minute to think gets that minute, instead of agreeing in the room and disagreeing afterwards.

If your team spans places and time zones, that last point matters more. A call at a time convenient for half the team quietly makes the other half spectators, which is why four hours of overlap is plenty once calls are reserved for disagreement.

The case a call handles better

Disagreement, ambiguity and anything with feelings in it.

When two people disagree in writing, each is arguing with a version of the other's position that they reconstructed from text. On a call you can ask "what are you actually worried about" and get an answer in ten seconds. Text takes a day to do that.

The same is true for anything vague. If nobody can state the problem in a sentence yet, a call is the right tool for finding out what the sentence is.

Two habits that make both work better

End every call in writing. Whoever called it writes three lines: what we decided, who does what, by when. Without this the call has no record and the same discussion returns in a month.

Give every message a deadline. "By Thursday" or "no reply means yes" turns a message into a decision instead of a thread. Pick a day both sides work, which across Kerala and the UAE is not always the day you assume. Most messages that turn into meetings do so because nobody said when a reply was needed.

When you cannot tell

Default to writing first. Write the question, state the options as you see them, and say who you need an answer from. Half the time you get one and it is over. The other half, you now have a written starting point for a much shorter call.

The mistake is going the other way. A call booked without a written starting point spends its first fifteen minutes getting everyone to the same page, which is the part writing does best.