This week we have a good long training session in preparation for a shift in tools. I can’t go into much detail, obviously.
Anyone who’s been in technical writing long enough will have taken part in a shift from one system to another. It’s when you get a new document-writing tool or a content management system (or both), and have to convert your existing set of documents into the new system.
Anyway, like I say, can’t go into much detail. It’s not an awful tool. It’s simple enough to use once you get the hang of it, and it has a lot of good features. It’s always a drag, the old migration.
Thing is, at the last place (ah, Konecr*nes. What precious fucking memories I have of your wonderful projects) we had a key user who knew how the tool worked and could do all the coding and bug fixes and messing around. And even he would occasionally run into a wall and have to contact the tool creators, who seldom returned his e-mails. And oh yeah, there was a certain amount of stress-related leave.
We’re looking at a similar system, and I’m happy enough to be a sort of a key user, maybe. And on top of that, I’m going to be writing some sort of process instructions because I apparently did such a good job writing process instructions for another tool (they were really just notes for myself!). Ah well, better leave it at that. I’m just pleased to be able to answer some of the questions that are popping up, and be useful.
It’s tough at the top, man.