What a thirty minute meeting actually costs six people

It does not cost thirty minutes, and it does not cost three hours either. The real number is larger, it is almost never counted, and the biggest part of it does not add up neatly at all.

The UnaTask team, Building UnaTask. Aug 21, 2026. 5 min read.

Somebody puts a thirty minute sync at eleven in the morning and invites six people. On the calendar it costs three hours of company time, which sounds tolerable, and that is roughly where the arithmetic usually stops.

Three things that sit around it

The meeting itself. Thirty minutes each, three hours across six people.
The approach. The stretch before it, too short to start anything real, spent half waiting. Call it ten minutes each, another hour.
The residue. Degraded attention on whatever comes next, because part of you is still in the room. Another ten minutes each, another hour.

That already doubles the nominal cost, from three hours to five. Those minute figures are reasoned estimates rather than measurements, and it is worth saying so plainly: the direction is well supported by the research on task switching, the exact size for your team is not. Use it to make an invisible cost arguable, not as a number to quote at somebody.

The fourth thing, which is the real one

A morning that could have held one ninety minute block now holds two short ones. This is the cost that matters, and it does not add up neatly, because it is not additive. It is a change of shape.

A meeting in the middle of a morning does not take thirty minutes out of it. It takes the morning out of it, and hands back two fragments.

Two forty minute gaps are not equivalent to one eighty minute stretch. For anything demanding they are worth considerably less: the fixed cost of getting into the work is paid twice, and forty minutes does not reach half the depth that eighty does. You cannot recover the difference by being more focused in the fragments.

Three rules that follow directly

Push meetings to the edges. The same meeting at 09:00 or 16:00 costs a fraction of what it costs at 11:00, because it removes time from the day instead of cutting the day in half. Applied to a team's recurring meetings, this single change is usually the largest gain available, and it costs nobody anything.
Cluster rather than spread. Three meetings in a row cost one interruption. The same three spread across a day cost three, and destroy every block between them. A stacked afternoon looks worse on a calendar and is cheaper in practice.
Count the room, not the meeting. Before adding the sixth person, ask what the invitation costs them given everything above. Optional attendance is a real answer, but only if declining is genuinely normal on your team rather than technically permitted.

Why this is a team problem and not a personal one

Almost everything written about time blocking quietly assumes you control your own calendar. Most people do not, and telling them to try harder is not advice, it is an accusation.

If any colleague can drop a meeting into any open slot, your blocks are decoration. You can defend them by declining, which spends a little social capital every single time, or you can change the structure once so the calendar declines on your behalf. Only the second one still works in a fortnight.

The cheapest version: blocks that are visible and marked busy, with a title specific enough for a colleague to judge urgency. "Deep: Q3 pricing model", not "Busy". The specificity is what makes it socially survivable, because "Busy" invites the question and a named piece of work usually answers it.

The version that works better than any individual habit: one recurring window where the team does not schedule internal meetings. Not tries not to. Does not. When it is your personal rule, protecting it makes you the difficult one. When it is the team's rule, protecting it makes you compliant. Same behaviour, opposite social cost.

The last part of the guide is entirely about blocking time with colleagues who can book you. Free PDF, no email, and every number in it traced to the paper it came from. Get the full guide