جلسه‌ای که تصمیم ندارد، فقط زمان را مصرف می‌کند

More meetings do not necessarily mean better coordination. Sometimes the opposite is true: a high meeting load is a symptom of decisions without clear owners, so issues simply move from one conversation to the next.

A useful meeting should know why it exists before it starts. Is the goal to make a decision, collect information, remove a blocker or report status? Mixing all of these goals usually makes the meeting longer and the outcome less clear.

A common failure mode is that people enter with information and leave with even more information, yet nobody knows exactly who owns the final decision or what happens next.

For every important topic, three things should be explicit: what was decided, who owns it, and by when it should be executed. If any of these are vague, the same issue is likely to return at the next meeting.

Recording a decision is almost as important as making it. A few lines that capture what was agreed, the main reason and the responsible owner prevent dozens of different interpretations afterward.

Not every issue deserves a meeting. If the purpose is only to transfer information, a structured message or short report can be better. Meetings should be reserved for situations where interaction actually adds value.

A good manager does not necessarily eliminate meetings; they improve the quality of meeting outputs. A short meeting with no decision is still wasted time, while a longer meeting that resolves ambiguity can be worthwhile.

A simple test is this: if someone asks tomorrow, ‘What came out of the meeting?’, the answer should fit into a few clear sentences. If the answer is only ‘we talked’, the meeting probably did not finish its job.