The follow-up nobody has time for

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

Follow-up is where a session stops being an event and becomes a change. It is also the part with no deadline, no audience waiting, and nobody chasing it. Those two facts are related, and the second one wins.

It has no forcing function

Preparation has a deadline: the session happens on Thursday whether you are ready or not. Delivery has an audience sitting in front of you. Follow-up has neither.

It competes with everything else in the week and loses every time, regardless of how much it is worth. This is a scheduling property rather than a motivation problem, which is good news, because scheduling problems have straightforward solutions and motivation problems do not.

Any intervention that relies on people intending to do follow-up will fail. The ones that work change when the work happens or how much of it there is.

What gets lost

The questions nobody answered. The topic where a third of the room turned out to be wrong. The suggestion that would have improved next month's session, made by someone who will now assume suggestions are pointless.

All of it was captured. That is the part that makes this waste unusual and particularly worth fixing: the expensive step, collecting the information, already happened and was already paid for. Only the cheap step is missing.

Most organisational waste is expensive work producing nothing. This is cheap work not being done, which strands the value of expensive work that was.

The self-reinforcing decline

Skip follow-up once and the effect is invisible. Skip it three times and your response rates start to fall, because people learn that answering changes nothing.

Lower response rates make the next session's data thinner, which makes follow-up feel less worth doing, which makes it easier to skip. Within a few cycles you have an engagement mechanism that nobody uses and everybody remembers as not having worked.

The failure gets attributed to the mechanism. It was actually a failure to close the loop, which is a different problem with a much cheaper fix.

Decide the follow-up before the session

This is the single most effective change available here, and it costs about twenty minutes.

If you know in advance what you will send and to whom, the session collects the right things and the follow-up becomes assembly rather than analysis. If you decide afterwards, you start from a pile of data with no question in mind, which is slow enough that it does not get done at all.

Most missing follow-up is not a follow-through failure. It is a preparation failure that shows up a week later.

Make the default state sent

The reliable version is one where the summary is generated and waiting, and the only human act required is a glance and a decision to send.

Anything requiring assembly from scratch loses to next week's deadlines, however good the intentions and however many times the team has agreed it matters. The intention is not the problem. The activation energy is.

Get that to near zero and follow-up happens by default, which is the only state in which it happens consistently.