From Workshop to Follow-Through

A decision made well in a room, closed with an explicit read-back and a named owner exactly the way yesterday's article described, still has a shelf life if it never leaves that room in writing. Two weeks is roughly how long a spoken decision survives on memory alone before something starts to erode it. Someone's recollection of the exact wording quietly drifts. A new stakeholder joins the project midstream with no idea the decision was ever made. A related decision gets made in an entirely different meeting that contradicts it, and nobody notices the conflict because the original decision was never written down anywhere either person could have checked.

There is a common, understandable assumption that a facilitator's job ends when the meeting ends, that running the room well is the whole task and what happens afterwards belongs to project management or to whoever owns the individual action items. In practice, a decision that dissolves two weeks later because nobody wrote it down was never really closed in the first place. It was closed in the room and reopened by default the moment the room's shared memory of it started to fade, which makes the follow-up write-up part of the same job as the read-back, not a separate administrative task tacked on afterwards.

What the follow-up actually needs to contain

It does not need to be full minutes, and trying to make it full minutes is often exactly why it does not get sent, because a genuinely thorough transcript takes real time to produce and even more time for a busy stakeholder to actually read. What it needs is much smaller and much more likely to survive contact with a full inbox: each decision stated as a single sentence, the name of who owns whatever happens next, and the date it is due. Three or four sentences total for a typical workshop, sent within twenty-four hours while the room's memory of the session is still sharp enough to catch an error in the summary before it hardens into the record.

That message takes a few minutes to write and roughly fifteen seconds to read, and it does two things a room full of nodding heads cannot do on its own. It gives everyone who was not in the room, and everyone who was but is already three meetings further into their day, a written artefact to check the decision against later. And it gives anyone whose understanding genuinely differs a clean, low-pressure way to say so in writing, which is often easier for people than speaking up live in the room the way Wednesday's article described.

Sending the recap the same day, or the next morning at the latest, is doing more work than it might appear to on the surface. It is the point at which the room's actual memory of the session is closest to what was really said, before individual recollections have had time to drift apart on their own. It also sets a quiet expectation, over a few weeks of consistent workshops, that a decision made in this particular room will always show up in writing shortly after, which changes how seriously people treat the room itself. A workshop known for reliably producing a written record afterwards gets a different kind of attention and preparation from stakeholders than one where decisions are understood to live only in whoever happens to remember them correctly.

Closing out the week

This week started with a two-hour workshop that felt good in the room and fell apart three weeks later on a follow-up call, four people holding four different versions of what had been agreed. Everything since has been an attempt to close that exact gap from a different angle each day:

• Writing the decision as a sentence before the invite even goes out, so the agenda has something specific to work toward.
• Directing questions to specific people, so silence stops being mistaken for agreement, and one voice stops quietly running the whole room.
• Reading the decision back out loud with a genuine pause for correction, so it cannot be misremembered three different ways by three different people leaving the same meeting.
• And now, writing it down within a day, so the decision survives the two weeks after the room empties instead of quietly dissolving the way it did in the story that opened this week.

None of these four habits requires being a naturally commanding presence at the front of a room, and none of them is complicated on their own. What they require is treating facilitation as something closer to a craft with specific, repeatable moves, the same argument this whole series keeps returning to, rather than a personality trait some people simply have, and others do not. A quiet, precise facilitator who consistently does all four of these things will get a room to real decisions far more reliably than a naturally charismatic one who skips them, and that is genuinely good news, because it means this is a skill anyone reading this can build on purpose, one workshop at a time.

What I watch for now

When I am mentoring someone through their first few workshops, the question I ask afterwards is rarely "how did it go," because almost everyone answers that with some version of "good, I think," the same way the room in Monday's story would have described its own session. I ask instead for the exact sentence that was decided on the hardest item, and who owns what happens next. If they can produce that sentence without having to reconstruct it from memory, the workshop worked, whatever the general mood in the room happened to be. If they cannot, no amount of good energy in the session actually mattered, because energy is not what a workshop is for. A decision is.

Go out and be successful.

Oluwatosin Ogunkoya ·  Flotog BA Insights  ·  1:1 mentoring and coaching for BAs at every career stage  ·  www.flotogbainsights.com