I spent Friday at the Content Strategy 2010 Forum (#csforum10) in Paris, which was a remarkable event for many reasons. First of all (and I am allowing my personal prejudices as a technical writer to come to the fore here) although this event was organised by members of the France Chapter and the Trans-Alpine Chapter of the STC, this wasn’t a bog-standard technical writing event at all: in fact, hardly any of the the speakers, and barely a quarter of the delegates would describe themselves as technical writers.
Next, although this event was held in France, most of the speakers were not from France or even from Europe. Many had travelled from the USA and Canada specially for this event which they recognised as being of ground-breaking and international importance. (As I write, I am aware that many of the speakers and delegates at #csforum10 are marooned in Paris, as a cloud of ash from an Icelandic volcano has temporarily grounded national and international air transport over much of Europe.)
My third point is this: despite the fact that this was not a tech writing event, and despite that fact that the focus of content strategists today is clearly on the web, the amount of common ground that content strategists share with technical writers and information designers, in terms of their own attitudes and approaches, as well as in terms of reactions to their work, is enormous.
Let me explain this point with some messages from a few of the speakers. Here’s how opening keynote speaker Rahel Anne Bailie defined content strategy:
[a] repeatable system that governs the management of content throughout the entire content lifecycle
This definition reminded me strongly of the “five-level publications-maturity model” promoted by Jo-Ann Hackos in Managing Your Documentation Projects, in which publications teams aim to be “organized and repeatable” at Level 3, and “managed and sustainable” at Level 4. Bailie pointed out that if a web site doesn’t easily allow a visitor to find what they are looking for they have a “broken experience” that reflects negatively on the site, the product and the brand. Isn’t that true of an online help system or user manual as well? Bailie also said that with so much social media around, anyone who has a “broken experience” can share their negative feelings with the world in seconds, and that’s true for negative feelings about tech pubs too. Content has to be central, said Bailie, and quoted Dorian Taylor:
The web doesn’t have content, the web is content
It is insight into human nature that is the key to the communicator’s skill. For whereas the writer is concerned with what he puts into his writings, the communicator is concerned with what the reader gets out of it. He therefore becomes a student of how people read or listen.
Bernbach could be describing technical writing best practices here. What is task-centric instructional writing about if not “concern with what the reader gets” from the text? If this is a key message for content strategists to get across to their clients, then clearly they are singing from the same hymn sheet as technical writers.
My last example comes from Colleen Jones of Content Science, who described how a public health agency client she worked with wanted to publish raw scientific articles on their website for the general public, and just leave them there. The information was accurate, but useless for the intended audience. It didn’t answer the questions that were driving people to visit the site in the first place. Her story was scarily familiar. I have met many subject matter experts who mistakenly think that everyone who is going to use their product is a clone of themselves and shares exactly their own interests in the underlying technology of whatever it is they are developing. If I had a pound for every time I’d told a product developer or a product manager that people reading the online help aren’t interested in all the technical details behind the product, they just want to know how to use the product to do their jobs, I could have retired on a generous pension by now!
These are just my first thoughts on the messages from Content Strategy Forum 2010 and their relevance for technical writers. In this post I haven’t mentioned all the excellent speakers I was privileged to listen to, and so I plan to return to this topic in the coming days.