My org has no technical writers that I am aware of. We have a massive wiki with tons of obsolete info, I guess we have an inclination to create instead of maintain documentation. Internally, in my small team we are attempting to stop using our internal wiki as much as possible and put our documentation as close to the code as possible, in markdown files within our repo. This makes us more likely to maintain it.
One thing that made me cringe. You mentioned recording your team meetings. In this age of remote work - all meetings are online, you CAN NOT record everything. If you do its a waste of storage resources because I wager less than 5% of it ever gets listened to again. My advice, don't record random everyday meetings/conversations. If you are going to record, take the time to edit and make a finished product.
Thoughts.
My org has no technical writers that I am aware of. We have a massive wiki with tons of obsolete info, I guess we have an inclination to create instead of maintain documentation. Internally, in my small team we are attempting to stop using our internal wiki as much as possible and put our documentation as close to the code as possible, in markdown files within our repo. This makes us more likely to maintain it.
One thing that made me cringe. You mentioned recording your team meetings. In this age of remote work - all meetings are online, you CAN NOT record everything. If you do its a waste of storage resources because I wager less than 5% of it ever gets listened to again. My advice, don't record random everyday meetings/conversations. If you are going to record, take the time to edit and make a finished product.