OPERATIONAL INFRASTRUCTURE

OPERATIONAL INFRASTRUCTURE

How to Learn From Your First-Time Event
How to Learn From Your First-Time Event
How to Learn From Your First-Time Event

A first-time event is valuable because it reveals what planning could not predict. The After Action Hour captures those lessons within seventy-two hours so the organization does not repeat the same first event next year.

A first-time event is valuable because it reveals what planning could not predict. The After Action Hour captures those lessons within seventy-two hours so the organization does not repeat the same first event next year.

We ran a thing for the first time recently. First of its kind for the organization, with a lot of moving parts, a lot of outside participants, and a load-in window that assumed everyone would arrive when they said they would.

It went well. It also taught us about nine things we did not know that morning, and roughly six of them were things nobody could have anticipated on paper.

What I care about is not the nine things. It is that within seventy-two hours all nine were written down, and the second one is already easier than the first will have been, permanently, for whoever runs it after me.

That is the entire return. Everything else about a first-time event is a wash.


You are not running an event. You are buying information.

Reframe what a first-time anything actually is. You are spending real money and real weekends to purchase a specific dataset: how this thing behaves in contact with reality.

That dataset has a shelf life of about four days.

Not because people are careless, but because the knowledge is stored in nine different heads in fragments, and each fragment feels too small to be worth mentioning. The person who realized the check-in table was Ocean Stride Advisory | Framer production copy 13 in the wrong place does not think that is a lesson. They think it is a Tuesday. Three weeks later, they could not tell you it happened.


If you do not capture it within a week, you paid tuition and skipped the class. And the tuition is not small. It is every hour of planning, every vendor conversation, and the goodwill of everyone who covered a gap on the day.


The After Action Hour

Sixty minutes. Within seventy-two hours. Everyone who was actually on the ground, including the people who were not in the planning meetings, which is where most of the value is going to come from.


Three questions, in this order, and the order is doing real work.

1. What did we not know that we needed to know? Gaps in information, not mistakes. This framing is deliberate: it produces answers immediately because nobody has to admit anything. You will get load-in realities, vendor behavior, the actual arrival curve versus the one on the schedule, and signage nobody could find.

2. What did we do twice? Duplicated effort is the cheapest thing to fix and the least likely to be reported, because doing something twice does not feel like a failure to the person doing it. Two people building the same list. A vendor called by three departments in one afternoon. This is where next year's hours come from.

3. What almost went wrong, and who caught it? The most valuable question of the three, and the one people skip because nothing bad actually happened. Near misses are your only free look at the failure. And naming who caught it does two things at once: it tells you where your real depth is, and it is the highest-return recognition available to you, because you are praising something invisible in front of the people whose opinion matters to you.


One page out. Not minutes. A page that a person who was not there could execute from.


Write the second one on the day of the first

The best version of this is not a meeting at all. It is a running note on your phone during the event.


Nobody has the presence of mind to run a structured retrospective on the walk to the car, but everybody has ninety seconds and a thumb. Timestamped fragments beat a polished recollection every time, because the fragment contains the detail you will not remember: that it was 6:40 am, that there were three people looking for one person, that the person they needed was parking a truck.


Then the after-action hour becomes an editing session rather than an archaeology dig.


The failure mode

Everybody remembers the day and nobody writes it down.


The warning sign appears eleven months later, and it is unmistakable: someone asks what time load-in was last year, and four people give four answers. At that point, you are not running the second one. You are running the first one again with better morale.

There is a second, subtler version. The lessons get captured but stored in a document nobody will look for, under a name only you would search. The after-action page belongs attached to next year's planning doc, on the day you create it, or it does not exist.


One thing to try this week: Put the after-action hour on the calendar before the event, as a real meeting with a real invite list. Booking it afterward never happens, because afterward everyone is relieved and nobody wants to sit in a room. — Michael J Washington, Ocean Stride Advisory

Issue 010
Issue 010