How rodeo committees lose institutional knowledge, and how to stop it

Three years in a row. Same event, same venue, same intermission surge at the same concourse choke point.

Year one: nobody had anticipated it. The supervisor on that zone handled it on instinct. Year two: that supervisor wasn't on that zone. The fix he'd improvised wasn't written anywhere. A different supervisor handled it a different way. Year three: the year-two supervisor was now the chair, watching from a different seat. Same surge. Same gap. Same improvisation.

Three events. Three chances to learn from the same experience. Three times the experience didn't transfer.

The sentence that tells you it's happening

"We had this problem last year too." Every person who has run events long enough has heard it in a debrief. It is the sound of institutional memory failure. The lesson existed. It never left the room where it was learned, or it left in someone's memory and evaporated when that person changed roles, retired, or forgot.

The committee that makes the same mistake three years running isn't incompetent. It's usually full of experienced people. It's a committee that converts experience into memory instead of into documents. Memory is perishable. Documents aren't. That gap is the difference between an operation that gets better every year and one that resets every year.

The debrief that actually changes something

Within 48 hours. Not two weeks later when the details have faded and the decisions have been rationalized into stories. The people who ran the operation, not everyone who was there — small enough that honesty is possible.

Four sections. What worked, named specifically, so it gets preserved on purpose. What didn't — the system, never the person: not "Zone B was a mess" but "the intermission move to Zone B was called too late and two posts were short during the surge." What we didn't plan for, which becomes a new protocol before the next event. And action items with an owner and a date on every one, because items without owners don't get done and items without deadlines don't get done before the next event.

A debrief that produces a list of things that went wrong is a historical archive. A debrief that produces owners and deadlines is a learning system.

Where the knowledge has to live

Not on someone's personal laptop. Not in their email. Not in their head. A shared folder the committee owns, organized by year and event, open to everyone with operational responsibility. When the person who built it walks out, the documents stay. Personal infrastructure the committee can't access isn't institutional memory. It's a single point of failure with a password.

And documents alone aren't enough. Documents transfer the what and the how. Mentorship transfers the why. An operator who has read the plan but never been told why the load-in is sequenced the way it is can execute it but can't adapt it when the event produces something the plan didn't anticipate. Both are necessary. Neither is sufficient.

The turnover audit nobody runs

Before the person who knows everything steps back, not after: "Walk me through every significant decision you make in the six weeks before this event. Walk me through every piece of information you hold that isn't written down." Record it. That recording is the foundation of the transition.

Most committees discover the gaps after. The person leaves, and within three months nobody knows how the load-in was designed, who the stock contractor's second contact is, or why the credential system uses the tiers it uses. Each discovery is expensive — a lost year, or an incident a written protocol would have prevented.

Year four at that choke point, for what it's worth: the problem was finally written down, a pre-intermission deployment was built into the run-of-show three weeks out, and the surge hit a managed corner instead of an unmanaged one. Three years of the same problem. One year of documentation. Zero recurrence.