Do we need this meeting?

Before you send or accept any invite, ask one question: what will be different when this meeting ends? Good answers are concrete: a decision made, a problem solved, a shared understanding, a stronger working relationship. If the honest answer is "everyone will know the numbers", a written message does that better.

Writing beats a meeting for pure information. People read it when it suits their shift and time zone, it takes minutes instead of half an hour of seven people's time, and it stays findable later.

Roman from tutor operations wants a weekly 30-minute call to share tutor no-show numbers with Support. That's informing. A better deal: a short weekly written update, and a meeting only when the numbers raise a question the two teams must decide together. Declining the numbers altogether loses useful information, and sending a coordinator in your place only moves the wasted half hour to someone else's queue.

Most meetings serve one of four purposes, and each has a format that fits it.

Decide: a small group with the person who owns the decision and the people who prepared the options. Iryna choosing between two weekend rotas needs a short call with her and the two people who drafted them, not the whole team.

Solve: two or three people who know the problem, working on it together. A refund that keeps failing for one payment method needs a working session for those few.

Inform: usually a written update, with a call only for news that needs a human voice, such as a difficult change. A new rule for outage refunds is information: write it down.

Connect: one-to-ones and a regular team call where people talk about more than tickets. How a newcomer is settling in belongs in a one-to-one.

When a meeting tries to do all four for everyone, it does none of them well. Name the purpose first, then pick the format.

A stand-up is a coordination check: a few minutes in which people say who's stuck and who needs whom today. Its purpose is narrow on purpose: it spots blockers and connects people, and the work itself happens after it.

Meetings drift. A stand-up starts as ten minutes of blockers; then someone reads out their whole status, then a tricky case gets solved in front of seven people, then announcements arrive. Each addition seems useful, and together they change the meeting's type without anyone deciding it. Klasna's stand-up, meant to be short, now runs far longer for seven people across two time zones.

The fix is to separate the purposes again. Status is informing: write it down. Problem-solving is a separate session for the two or three people who know the case, right after the stand-up. Announcements go in the channel. What stays in the stand-up is what genuinely needs everyone at once: blockers and who helps with them. Module 5's case audits Klasna's stand-up with numbers.

The urge to invite everyone comes from kindness: nobody likes being left out. But a seat in a meeting isn't the same as being informed, and every extra person costs queue time.

The rule is simple: invite the people the meeting needs, meaning whoever decides, whoever knows the problem, and whoever must act on the result. Everyone else gets the written summary within the hour. Being informed doesn't require being in the room.

Time zones raise the cost. At Klasna, two coordinators work two hours behind Kyiv, so a 9:00 meeting is 7:00 for them. Olha's point is fair: if they aren't needed, don't make them get up for it. When they are needed, rotate the meeting time or ask for written input the day before, so the burden of early hours doesn't always fall on the same people.

Leaving someone out isn't a judgement about them. Say so: "You'll get the summary within the hour, and you can add questions there."

A meeting without roles drifts: nobody watches the clock, nobody writes down what was agreed, and people leave unsure whether a decision was made or who made it. Three roles fix most of that, even in a small team call.

The owner sets the purpose, sends the agenda, keeps time and closes the meeting. The note-taker captures decisions and action items as they happen and posts them afterwards. When the meeting has a decision to make, the decider is named before it starts: Iryna for the weekend rota, say, with the two people who drafted the options there to advise.

Naming the decider in advance matters most. If people think the decision belongs to the group, they treat the meeting as a vote and feel overruled when someone else decides. If they know from the start who decides and that they are there to advise, the discussion is more honest and the outcome is easier to accept. Module 7 goes deeper into who decides.

Write the agenda as questions, not topics. "Refunds" invites a tour of everything anyone thinks about refunds. "Do we allow refunds for lessons missed during a power outage, yes or no, by Friday?" invites an answer, and tells everyone when the item is done.

Next to each question put who brings it, how many minutes it gets, and a link to anything people should read first. Send the agenda a day ahead. People on other shifts and in other time zones can then prepare, or comment in writing if they can't join live.

Two habits spoil an agenda: one-word topics, which invite wandering, and an agenda shared only when the meeting starts, which shuts out anyone who would have prepared or commented in advance.

And sometimes the pre-read answers the question before the meeting. Then cancel the meeting, post the answer and move on. A cancelled meeting with the work done is a win, not a failure of planning.

The last five minutes of a meeting decide whether anything happens afterwards. Every agreed step becomes an action item with three parts: one owner, a concrete next step, and a date.

Each part prevents a familiar failure. One owner, because two owners blur responsibility: "Taras and Bohdan will look at the backlog" usually means each waits for the other. A concrete step, because "improve the refund process" isn't something anyone can start today. A date, because "soon" and "next week" aren't dates.

The test applies even when the step is only "find out": "Olha checks with Roman which payment method fails, by Wednesday" is an action item; "someone looks into refunds" isn't. A good example from Klasna's summary: "Maryna drafts the reply template for outage refunds and shares it in the thread by Thursday 14:00."

Read the list back before the meeting ends, so each owner hears their step and can object while everyone is still there.

A meeting isn't finished when the call ends; it's finished when the people who need its result have it. The tool for that is a short written summary posted within the hour, not minutes of who said what.

The summary has two parts: what was decided and the action items, each with one owner, a concrete step and a date. Iryna puts it plainly: "I don't need minutes. I need what was decided, who does what, by when."

In a distributed team this is what keeps meetings fair. At Klasna, two coordinators work two hours behind Kyiv, people join from abroad, and power cuts interrupt calls. A summary lets anyone who missed the meeting, or dropped out of it, catch up in two minutes, in their own time. A recording is not a substitute: it takes as long as the meeting to watch.

How it fits together: a meeting earns its place with a purpose, the right people and roles, an agenda of questions and an ending with owner, step and date. Next, Channels and async work: what goes in a channel, what goes in writing, and what you hand to a tool.