But that was kind of the whole point.

For a while, I had someone actually recording status meetings and sending me copies.  Like an idiot, I kept them in my mailbox with a category flag intending to watch them at some point.  Then someone else thought it was a good idea and I started getting their meetings.  Then a third set.  After 10 weeks and approximately 30 unread/unlistened-to meetings, sometimes even recorders miss their own meetings, I just pushed them all into my archive.  Afterwards, I was paranoid that someone would say "Snarky, so in that meeting recording, I mentioned that you had a work item related to blah blah blah, what do you think about what was proposed?"  And then it would be obvious I wasn't listening to the recordings.

I realized that the real solution wasn't to live in fear, but to tell the individuals recording the meetings that it was an incredibly bad idea that put undue stress on the developers involved.  But like a typical Minnesotan, I was worried I'd hurt their meeting-recording feelings.  So I got smarter and just told them missed meetings were generally because developers were busy with priority one items, and forcing them to catch up adversely affected real velocity.  Our .85 (85%) velocity was inaccurate if we were forcing developers to attend meetings they'd missed because of other priorities we'd deemed more important.  We'd have to decrease to .75, or even .7 if every meeting was mandatory.  Fixed it.  And everyone was happy.

Title: But that was kind of the whole point.
Snarky: Since you weren't there yesterday, I've decided to start recording all of our meetings for you to review on your own time.  That way you won't miss out on any of our discussions.