From one workshop to a documentation habit
How a training log I started for my own sessions became something the team and partners used without being asked.
- 01
Session
- 02
AI meeting notes
- 03
Draft recap
- 04
My review
- 05
Log entry
“Culture is what people do when you're not in the room. Documentation is how you find out.”
Challenge
Every training session the team ran left nothing behind. A new hire couldn't repeat what a colleague had taught the month before. There was no way to see what had been covered, by whom, or whether it worked.
Who it was for
The career team, regional leads, and anyone who would join later.
What I built
- A training log with one entry format: session, date, format, facilitator, presenting need, objective, content covered, live outcome, materials, follow-ups
- A recap workflow: AI meeting notes feed a draft recap and a log-ready entry, which I review and clean before anything is shared
- A main-stage class for program participants on proving AI fluency in hiring (what I built, what broke, how I fixed it) with a facilitator guide, built in under two hours after I spotted a gap
Decisions and tradeoffs
- One format, no exceptions. Flexibility would have made the log easier to start and impossible to search.
- I logged my own sessions first and said nothing. The habit spread when people saw it was useful, not because it was required.
Outcome
The log grew from my sessions to include specialist-led and partner-led ones. The AI fluency class drew same-day recognition from leadership and an organization-wide shoutout.
What I'd do next
Turn the log into a lightweight internal course catalog so new staff can self-serve.