We’ve noticed a few slidedecks and blogs recently that have been looking at the value of technical communication in marketing a product successfully. With the trend towards earning revenues over a lifetime (rather than in a single upfront payment), the marketing strategies employed by organisations is changing.
Scott Abel has posted a slidedeck called “The Future of Technical Communication is Marketing”, which you can see below:
I’ve had some time in the last few days to initiate some the ideas mentioned in my post Marketing the technical communication profession. This relates to improving the marketing of the Institute of Scientific and Technical Communicators. Most of the work we do for clients is confidential, so it’s a pleasant change to be able to talk about a project as it’s progressing.
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).
HyperCard was a hypertext program that came with Apple Macintosh in the 1980s. It allowed you to create “stacks” of online cards, which organsiations used to create some of the first online guides. It also contained a scripting language called HyperTalk that a non-programmer could easily learn. This meant HyperCard could do more than just display content: it could be used to create books, games (such as Myst), develop oil-spill models, and even dial the telephone.
Most of the Technical Authors I have met don’t have a good thing to say about Microsoft SharePoint. In many ways, it represents how not to publish content online. It is seen as encouraging people to move print-optimised documents (Blobs) around, rather than units of content (Chunks), and users are typically left to rely on search to find which document contains the information they are looking for.
For all those issues, SharePoint may still have its place – for managing documentation projects.