When 15 minutes of messaging costs more than an hour-long call
Messaging feels cheap, but it has a threshold after which one short call saves hours. How to notice that threshold.
We are used to thinking written communication is cheaper. No need to align schedules, you can reply when convenient. That is true — up to a point.
Where messaging breaks down
Nuance and tone. Contentious points read harsher in text than they were meant. A person responds to the offense, not the meaning, and the thread balloons.
Many variables. When you need to discuss deadlines, budget, and scope at once, text becomes a ladder of quotes where nobody knows which version was answered.
Parallel branches. Three people reply to each other, and by message ten they live in different realities.
Waiting for answers. Every “question — pause — answer” loop costs an hour of idle time while the other side is busy.
A simple stopping rule
If a thread has more than 6–8 messages and you have not reached a decision, switch to voice. A 10-minute call closes what messaging drags out for half a day. The math is simple: 10 minutes of two people versus hours of scattered attention across everyone involved.
How not to lose the result of a call
The downside of a call is that it leaves no trace. So right after it, capture the outcome:
- write one line in the same chat: “Agreed: …”;
- create a task with an owner and a due date via
/task; - if needed, add the conclusion to the task description.
In Branzy a call starts from the same chat where the thread happened: video calls open in one click, and the outcome stays next to the discussion.
The reverse is also true
If a question is one-liner and needs no discussion, a call is overkill. Pick the channel by the complexity of the problem: simple — text; ambiguous or emotional — voice.