I was asked to take part in the ContentHug series of interviews on technical communication and content strategy.
It was fun and challenging, going through the questions.
ContentHug’s Vinish Garg is interviewing a number of consultants involved in technical communication and content strategy, and asking them essentially the same questions. By reading the interviews, you can see where there are areas of agreement and where there are a variety of opinions. In general, there is a fair bit of consensus. They are worth reading.
Here’s the latest Interview, with John McNamara of IBM, on what it’s like to be a technical communicator:
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.
I was due to be recorded/interviewed first thing this morning over the phone for a piece a BBC local radio station was going to do about instructions and how get written. I was standing in for the President of the Institute of Scientific and Technical Communiators (ISTC).
However, a producer called this morning to tell me they couldn’t stand up the facts that had prompted them to look at this subject (regarding some instructions in a Homebase product), and they’d decided to shelve/postpone the item. I also suspect the Charlie Hebdo killings have (rightly) taken precedence over other stories today.
I’d spoken one of the producers the day before. What they were interested in knowing was, how do instructions get written? She said she wouldn’t know where to start or what to do. We chatted about the technical writing process: how technical communications learn about a product; how they work out what topics need to be written; and how the instructions themselves are organised.
It was nice for them to have contacted the ISTC, and perhaps it will be something they pick up again in the future.
The July 2013 edition of tcworld magazine contains an interview with Cherryleaf’s Ellis Pratt on technical communication and social media.
The magazine also includes an article by Sarah Maddox (now at Google) on how technical communicators can use Twitter in technical communication.
We’re not certain when/if the online version will be uploaded to the tcworld site, but we’ll add a link to the article as soon as we can.
Update: You can view it online.
Cherryleaf’s Ellis Pratt was interviewed recently for an article for AccountingWeb called Don’t be a boring accountant: Lessons from a technical author. The article has been published today.
It explores what accountants can learn from Technical Authors in how to avoid being seen as boring, whilst still maintaining their credibility.
The full article is available to registered AccountingWEB members only. It’s free to register.
In Data Quality Pro Journal, Dylan Jones interviews Ellis Pratt, Director at Cherryleaf, about how to improve Healthcare data quality through policy and procedure management. According to Dylan,
“One of the single most common root-causes of poor information quality is outdated documentation and a lack of governance in the way policies and procedures are managed. Nowhere is this more critical than in the healthcare sector.”
Ellis shares a range of practical techniques and methods to help improve policy and procedure documentation within the healthcare sector.
Article – How to improve Healthcare data quality through policy and procedure management.