We’ve been busy bees recently, working on some new elearning courses that we plan to be introducing soon. Shortly, we’ll be offering an online course on DITA Fundamentals, and another on Content Strategy. Both courses have been written and are at the User Acceptance and Testing stage. Of these two, you’re likely to see the DITA course released first.
There are two more online courses in the pipeline, which we hope to release at some point in 2014. One relates to policies and procedures, the other to elearning/screencasting.
Our intention is to offer basic courses online, and advanced courses in traditional classroom format. Where there’s demand, we’ll also use Google Hangouts to deliver the advanced courses to overseas delegates.
Prompted by Scriptorium Publishing’s Sarah O’Keefe’s one bag method for travelling (she doesn’t check any luggage into the hold of an airplane), I’ve been looking at ways of reducing the weight I need to carry when flying to conferences or to clients. I’ve called this “ultralight conferencing”.
Screencast videos have become a popular means for delivering “how-to” information. One of the questions developers must address is, how long should you make your screencasts?
At last weeks’s tekom conference, I saw an interesting presentation by Melanie Huxhold and Dr Axel Luther of SAP on how they develop screencasts for SAP’s products (Produkt- und Lernvideos als ideale Ergänzung zur klassischen Dokumentation). In their presentation, Melanie said they had determined the ideal length for their videos by sending out a questionnaire to users, asking them what they preferred.
One of the kind things people were saying to us at the tekom conference last week was they enjoyed reading our free illustrated guide to DITA. Indeed, we’ve been bowled over by the response to this mini graphic novel and the number of people who have downloaded it.
This prompted us to complete a second illustrated guide we had “in the works” – on content strategy.
Again, this guide takes the form of a graphic novel:
One of the most recent developments in web page design has been the introduction of “long form” web pages. Will we also see the long form approach used in Help, or perhaps start to influence the way some Help pages are designed?
We’ve been on the road in recent days and weeks, visiting different documentation teams, and we’ve found there are distinct signs of change. In this post, I’ll look at how we’re starting to see the workflow for creating User Assistance beginning to change.
We found many documentation teams overstretched and starting to be asked how they could create content for new products that were coming along. Some organisations have decided they can only deal with this extra workload if they rethink the workflow for how content is created.
We’ve been on the road in recent days and weeks, visiting different documentation teams, and we’ve found there are distinct signs of change.
In previous years, most documentation managers have effectively been saying to us their organisations weren’t really clear about the value of documentation. As the Technical Publications team usually amounts to less than 5% of the IT budget, the successful companies have, in the past, not worried about this and left the documentation team to work out for themselves what they should be doing. However, for organisations that have been watching every percent in the budget, they’ve reduced the spend on technical documentation to the bare minimum. Of course, in a recession that’s been quite a few companies.
We’ve scheduled another Advanced Technical Writing Techniques public course – on Monday 2nd December.
Discover the advanced new writing styles emerging in technical communication. Don’t get left behind: past clients include technical communicators from Citrix, IBM UK, Lloyds Banking Group, Sage plc, Schlumberger and Visa International.