Pilot an async meeting in 14 days: a day-by-day plan, three numbers and a go/no-go memo

An async meeting pilot replaces one recurring meeting with recorded rounds for 14 days. Run two rounds, one per week, each with an agenda, a named owner per topic and a recording deadline before the old slot. Afterwards, three numbers decide: how many videos came in, how fast, and how much of them people watched.

The best candidate is a weekly status round that passes information on, with five to fifteen people and at least 3 people who each own a topic. Weekly, because two rounds fit into the trial. 3 owners, because a round with one speaker is a video message and tests nothing about collecting topics.

Leave out any meeting that must settle a disputed decision during the pilot. The one-question test in the hub guide sorts the rest: if the meeting has to produce "everyone knows X", it qualifies.

A pilot works when topics arrive early enough to watch, get watched, and the team does not ask for the old meeting back. The thresholds below are our rule of thumb; pass lines already written into a business case take precedence. Change them only before you see results. The baseline is minutes times attendees per week: a 45-minute meeting with 8 people costs 360 person-minutes, and the meeting hours calculator gives its year.

When a number lands between go and no-go, the survey comments decide. Its three questions go out on day 12, a day after round 2 is published: Did you miss anything from the live meeting? Would you like it back? About how many minutes did watching take you?

Capme Meetings, a platform for async meetings, shows the three numbers on the admin Overview tab as workspace totals; its shortest range, 30 days, covers the whole pilot. Take a fictional product team: eight people on the audience list, four topic owners, two rounds of four topics. After round 2, Overview reads like this.

Owners and admins open Trial summary to forward from Overview: plan, end date, speakers and viewers, recordings, the price and DPA acceptances. It shows no time saved, so attach your own calculation.

Two limits belong in the memo. Overview cannot filter by meeting, so other meetings in the workspace mix into the totals; keep the trial workspace to the pilot. And Capme has no comments, transcript or summary, so questions go to your team chat and only the survey measures what people missed. What admins see lists every figure.

The first recorded round usually fails on timing. Speakers wait for the deadline, so on day 3 Waiting on is full at noon. Pressing Remind everyone then gives them an afternoon; at 17:30 it gives them a rushed take. Capme reminds speakers only when the organiser presses the button, so put it in your calendar.

The second failure is length. Five minutes per topic turn into eight, and four topics become half an hour nobody finishes. Set two minutes for routine topics in round 2 and see whether watch-through moves; the guide on whether anyone will watch covers other causes. The third is a slot kept "just in case": people come, and the pilot measures a meeting with homework, so cancel it.

In a German company with a works council, agree the pilot with it before day one, because a tool that shows who watched what falls under § 87(1) no. 6 BetrVG. The Federal Labour Court reads that rule broadly: a system that is objectively able to monitor is enough, whatever the employer intends (BAG, 13 December 2016, 1 ABR 7/15, the Facebook-page decision). Choosing Totals only shows less, but the council still decides.

Plan a week for it; the guide to works councils and video tools has the letter. This is not legal advice.

14 days show whether the mechanics work, and they are too short to show whether the habit lasts. In a study of 96 volunteers who repeated a daily behaviour for twelve weeks, the time to reach the plateau of automaticity ranged from 18 to 254 days, "highlighting that it can take a very long time" (Lally et al., European Journal of Social Psychology, 2010). The British Psychological Society's summary puts the average at 66 days, and a weekly meeting repeats far less often than a daily habit.

We think the honest request is one quarter with a review date and an early-stop number, because two rounds prove the mechanics and only repetition builds the habit. The same study found that missing one opportunity did not materially affect habit formation, a fair answer to the colleague who skipped round 2.

When Capme's trial ends, the workspace keeps every recording and stops accepting new ones until a plan is bought. The first bill counts speakers only, and during the trial everyone you added is one, hence the switch on day 12. Keep the organiser a speaker, since organising needs a speaker seat. If the signer is late, everything stays watchable, admins can still make speakers viewers, and round 3 waits until the owner buys.

Team costs €12 per speaker a month, net, from 3 speakers: the example team's four topic owners, organiser included, need 4 speaker seats at €48 a month, and the smallest plan, €36, also covers a team with two owners (Solo is for one person). Business costs €18 per speaker from 10 and adds single sign-on, your own storage bucket and your own retention window; if IT has to see those, switch the trial to Business on day 1. Only the owner buys, monthly or yearly, and the trial summary shows both prices. A yearly plan can be paid on invoice by bank transfer. Plans and trials has the details.

The go/no-go memo is the one-page verdict after the trial, sent to the signer with the trial summary attached. The request before the trial is the business case for async meetings.

If the numbers fail, the memo names the line that failed and the meeting goes back into the calendar, ideally shorter by the topics that worked as videos.