From the Cherryleaf podcast: The UK Parliament is one of the oldest organisations in the world. So how do you deliver a strategy to a body that has over 700 years of content? Cherryleaf’s Ellis Pratt interviewed Rosie Hatton, Strategy Digital Lead at the Parliamentary Digital Service, to find out.
- What is Parliament? 1’56”
- The content Parliament creates. 3’38”
- What is the PDS? 5’08”
- The I AM PARLIAMENT programme. 9’00”
- The PDS’s digital strategy framework, its assumptions and principles. 10’18”
- Having an open and agile digital culture in a traditional organisation. 13’08
- Working in a continuous interative process. 20’45”
- Sharing ideas with the Government Digital Service. 25’24”
- Where does the PDS’s content strategy fit within its digital strategy? 28’22”
- Tracking the impact of changes to laws on other laws. 37’01”
- The similarities between PDS and Open Source software projects. 41’55”
- Crowdsourcing a digital strategy. 43’30”
- Benefits management. 44’00”
- How to manage and sell change. 47’50”
Here is an interview we carried out with Mark Baker, author of Every Page is Page One. The interview is interspersed with audio snippets from Day 1 of the UAEurope 2017 conference.
- Caroline Loverage (Thermo Fisher Scientific). Teaching by Example: Worked Examples in the Documentation of Complex Systems
- Kelly O’Brien (Kayako). Practical Information Architecture: Building Templates For Better Content.
- Helena Pichler (Nominet). AsciiDoc to Responsive Webhelp: Agile documentation for small teams/
With thanks to Matthew Ellison and Mark Baker.
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.