Here’s our Interview with Diana Logan MISTC of Citrix Systems, on what it’s like to be a technical communicator.
For the ISTC’s YouTube Channel, Ellis Pratt (Cherryleaf) is interviewing a number of technical communicators.
Here is Adrian Warman (IBM Cloudant):
Here is Brian Harris (Red Gate Software):
There’ll be more interviews in the coming weeks.
We’ve been putting together some short length videos that we can use on the Cherryleaf website. These are “quick and dirty”, three to four minute videos, shot
behind in front of a green screen.
One explains why technical communication is changing:
Another looks at recruiting a Technical Author:
Each video takes a couple of hours to create, and we hope to add more over time.
Our post about how Microsoft is changing its writing style (Microsoft moves away from “robot speak” in its user documentation) generated a lot of interest, so I thought it might be useful to post some examples of it that we’ve spotted.
These examples are from Office 365 Premium Edition.
The quotation in the title is from Roger Hart’s presentation at last week’s TCUK14 conference. Roger is a product marketing manager who spent a few years as a Technical Author. In his presentation, Collateral damage: do marketing and tech comms have to fight when users get informed?, he explained some of the most powerful marketing content today is high quality user information – especially the content that Technical Authors produce.
One of the highlights from the Technical Communications UK 2014 conference was the keynote presentation from Microsoft’s Doug Kim. Doug is Senior Managing Editor for Office.com, and leads guidelines and best practices for Voice in Office. By Voice, he means the tone of voice and style of English used in the User Interface and user documentation.
The change in voice is something we explore on our advanced technical writing techniques course, so I was interested to see how Microsoft was addressing this topic. The good news for us is that Microsoft’s approach is consistent with what we advocate on the course (however, we will need to update the course before the next one in December to include some of the topics Doug discussed).
Since I wrote the post on Technical communication as a brand, we’ve been working on an idea we had for promoting the profession. The end result is another story, another free graphic novel you can download, called The CEO and the technical communicator.
It’s published under a Creative Commons licence, so anyone can forward it on, as long as they don’t modify it or sell it.
There’s a lot of factual evidence about the value of technical communicators to an organisation (such as the ROI calculators on our website), so we thought we’d see if we could appeal to the heart as well as the head by using a story-based approach.
Technical communication comes in many forms, so there were some challenges in coming up with something that was representative of the whole profession. Partly to get around this, the document shows people’s reactions to the content created, rather than showing the content itself. It also uses the word “content’ as a catch-all for document, manual, book, Help file, Web page, illustration, and so on.
We’ve also developed an ISTC-branded version that the Institute for Technical Communicators could use itself to promote the profession. We’ve sent it to to the ISTC Council for their consideration and comments. The document might be modified if they ask for any changes to be made; for example, we’re wondering if there should be greater emphasis on the writing aspect of the role.
You can download the Cherryleaf version from our website. Let us know what you think, using the comments below or by email.
We’re just starting to record the video inserts for a new online training course we’re developing. As I’ll presenting at the TCUK 2014 conference on on this topic, I thought I’d take a few photos in case they come in handy during my TCUK presentation.
We record the presenter actually presenting the slides, as this results in a more natural presentation style. The presenter sees the slides on the laptop, and we use the laptop’s camera for recording the video.
Previously, we’ve recorded to a white background, but for this course, we’re going to be using a green screen. We record the audio using a USB microphone and a digital voice recorder. This means we have two audio recordings of the presentation.
The presenter sees a copy of the slides on the laptop screen, which he can progress through using a remote control. He also sees the script via a teleprompter on a tablet.
The green screen (we use chroma-key to remove the background) is giving us more consistent results than having a white background.
It’s a comparatively low budget setup, and it seems to work.