I think I’m a strange cat, in that I actually enjoy technical writing. Something about trying to blend cold, ugly schematics and concise, clean text makes me happy. Whenever I’m building or fixing something for my kids or my house, I enjoy looking through the user’s guide that comes with the toy/tool/equipment/IKEA puzzle, and seeing what works in terms of documentation, and what doesn’t. In previous places, I’ve been tasked with working heavily in the documentation side, and I kinda miss being able to do that where I currently am. Unfortunately, a lot of that content is proprietary, and couldn’t come with me.
Regardless, I do have one example of a workbook/manual that was intended to be used in conjunction with an in-person leadership development workshop.
Staff had way too many documents to keep track of at any given time, so we made a manual with commonly used docs, including a screenshot of what the doc should look like, to serve as guidance while they were doing their tasks.
I left the gaps below on purpose to avoid repeating the same points on the slide deck (which I only use as a roadmap while teaching to avoid DEATH BY POWERPOINT). Instead, I’m trying to encourage staff and learners to pick up the points that we’re working through, and commit their own notes.