The Twenty-Minute Circle: A Small Ritual for Teams That Have Forgotten How to Talk

Every hybrid team has one. The Tuesday call that started as a quick sync in 2021, survived three reorganisations, and now runs to fifty-five minutes with eleven attendees, four of whom speak. It has no agenda because it has a format, and it has a format because nobody has had the energy to argue with it.

You can't just cancel it. Cancel it and the updates stop flowing, the quiet people vanish from view entirely, and someone's project quietly drifts for a fortnight. The meeting isn't there because people love meetings. It's there because it's currently the only mechanism holding the information together.

Kula Circles are a replacement mechanism. They borrow the idea behind the name — small groups, gathered deliberately, close enough that everyone gets to speak — and they fit into twenty minutes a week.

What a circle actually is

A circle is a small cross-functional group — six to nine people is the sweet spot — that meets for twenty minutes, once a week, with a rotating host and a written pre-read circulated beforehand.

The membership matters more than it sounds. Circles work best when they cut across functions rather than mirroring the org chart, because the value is in the collisions: the marketer finding out what support is drowning in, the engineer hearing about the customer complaint nobody escalated. Keep them stable for a quarter at least, otherwise you're just running a different meeting with different strangers.

What a circle is not: a decision forum, a project review, or a place to read out a list. Anything that needs a whiteboard, a budget holder and forty minutes should be its own thing, booked separately, with only the people who need to be there.

The pre-read does the heavy lifting

This is the part teams skip, and it's the part that makes the format work.

Everyone posts before the circle meets — same simple shape every week, so nobody has to think about structure. Three prompts are plenty:

• Shipped: what went out the door since last time.
• Stuck: what's blocked, and who could unblock it.
• Need: a specific ask, with a name attached.

Keep each entry to a couple of lines. The discipline is in the naming: an ask with a name gets answered, an ask addressed to the room gets admired and forgotten.

Asynchronous first has a quiet benefit for anyone who's been on the back foot in live meetings — the parent doing the school run, the person whose best thinking happens at 9pm, the new starter who hasn't worked out the room yet. Writing gives everyone the same starting line.

The host reads the pre-reads the morning of, not the night before. Anything that's clearly resolved in writing gets marked as such and doesn't come up live. That single habit is where most of the time saving comes from.

Rotating hosts, rotating perspective

The host changes every week. Their job is small and specific: read the pre-reads, pick the two or three threads that need a live conversation, invite the right person to speak first, keep the time, and post a four-line summary afterwards with owners and dates.

Rotating the role does three things. It distributes the admin so it isn't another invisible job for the same overstretched person. It gives people a reason to read the pre-reads properly. And it changes what gets noticed — a support lead hosting will spot different blockers than a finance lead will, and both are right.

The twenty minutes, minute by minute

Roughly: two minutes to confirm the agenda the host has chosen, twelve minutes on those two or three threads, four minutes on asks that need a live answer, two minutes to agree who's writing the summary.

No slides. No status round. If someone starts reading out what's already in the pre-read, the host is allowed — encouraged, even — to say so cheerfully and move on. Cameras optional, notes mandatory-ish.

It ends on time. Always. A ritual that overruns teaches people to protect their calendars, and then you're back where you started, with eleven attendees and four speakers.

Does it actually reduce meetings?

Test it honestly rather than declaring victory in week two. Three measures, all easy to pull:

Recurring hours per person. Count the calendar before and after, over a month. If circles are working, some of the smaller update calls start to feel redundant and get dropped. If nothing gets dropped, you've added twenty minutes rather than replaced anything — worth knowing.

Time-to-unblock. Pick the asks that appear in pre-reads and note how long they take to resolve. Written asks with names tend to move faster than the same thing raised vaguely in a big call, and the numbers usually show it within a month or two.

Who speaks. Count distinct voices in the live session. A format that pulls five people into a conversation rather than two is doing its job, particularly for the quieter half of the team who've been spectating for a year.

Where circles go wrong

The most common failure is size. Ten people becomes fifteen becomes a status meeting with a nicer name. Cap it and start a second circle instead.

The second is a host who treats it as a performance — preparing slides, presenting, filling every second. The host is a chair, not a compère.

The third is letting the pre-read become a report. If people are writing essays, they'll stop writing. Two lines per prompt, with the odd link, is the target, and the host should model it.

And the fourth: no follow-through. If the summary goes up and the owners and dates quietly evaporate, the circle becomes another talking shop. Post the summary where the team already is — Kula's feed works well for this, since the pre-read, the discussion and the resulting actions sit in one place rather than across three tabs and a chat thread.

Try it on a Tuesday

Pick six to nine people, pick a host, book twenty minutes for four weeks, and tell everyone the shape of the pre-read. Don't pilot it for a quarter — four weeks gives you enough signal to know whether the live conversation got sharper.

The first one will be slightly awkward. The second one will be better because the host will have cut something. By the fourth, someone will suggest cancelling a different meeting, and that's the moment you'll know the circle has earned its place in the diary.