The admin tax on every session you run

Part of a single argument: the engagement gap is a workload problem.

Between having a good session designed and having actually run it sits a layer of logistics that nobody counts as work and everybody does. It is the most reducible cost in the whole cycle and the least examined, largely because none of it is interesting.

What the tax consists of

Getting people the link. Getting the two who cannot log in sorted out. Checking it works on the meeting room screen, which is a different screen from the one you built it on. Explaining how to join, again, to the same person. Handling whoever joined last month's session because that link was still in their calendar. Restarting the activity because it was left open from the previous run and now has stale results in it.

Individually trivial. Collectively a recurring tax on every single session, paid by the person least able to spare the attention, because they are the one about to stand up and present.

Why it falls almost entirely on engagement

This is the part that matters and the part that is usually missed.

A plain presentation has almost no admin tax. You open the file and you talk. There is nothing to join, no access to grant, nothing that can be in the wrong state.

Every interactive element adds a way for something to need sorting out. So the tax is not distributed evenly across formats. It is levied almost entirely on the engaged version, which means your organisation applies a structural, recurring penalty to exactly the behaviour it says it wants. Nobody designed this. It is simply what happens when the interactive path has more moving parts and nobody has counted them.

It is also where the fear comes from

Ask people why they avoid interactive formats and a surprising number will describe, not boredom or scepticism, but a specific memory of something failing in front of a room.

That is an administration failure, not a content failure. The poll that would not load, the half of the audience that could not join, the activity that showed last week's answers. Each one is a small technical problem and a large social one, because it happened in public while people watched.

Every step you remove from the setup path is a step that cannot fail in front of an audience. That is worth more than the time it saves, because it is what determines whether someone is willing to try again.

Judge tools by the eleventh session

Setup cost is paid once and dominates every evaluation, because evaluations happen at the beginning. The admin tax is paid every single time and almost never gets assessed.

When comparing options, ask what running the eleventh session costs rather than the first. The answers diverge sharply, and the eleventh is the one that decides whether the practice survives past the initial enthusiasm.

A tool that takes a day to set up and thirty seconds per session beats one that takes ten minutes to set up and fifteen minutes per session, and it is not close, but the second one demos better.

The target to aim at

Joining should require no account, no install, and no instruction beyond a link or a code. That is achievable, and where it is achieved participation rates move more than they do from any improvement to the activity itself.

For the person running it, the target is that setup is a single act with no state to remember. Anything that can be left in the wrong state from last time eventually will be, usually in front of the largest audience of the quarter.