With 2011 waning, people are contemplating what 2012 will bring for technical communication. Our profession is changing rapidly, so intelligent conversations about the future of tech comm are essential.
All that smart talk has absolutely nothing to do with this post.
Simple answers are appealing and are easy to remember. [Refrain from gratuitous political joke here, mostly.] But the real world is full of complex issues that are not easily reduced to soundbites. This also applies to technical communication and XML adoption.
In this webcast recording, Sarah O’Keefe discusses how the cost of developing content affects what is actually created. She leads with a discussion of Gutenberg and how we went from gorgeous, unaffordable, artistic books that took years to produce to more plebeian but affordable books. Then she considers today’s situation, with particular attention to the possibilities of video, information apps, and a look at what has NOT changed.
You know you’ve had a bad travel week when you cannot wait to compose the complaint letter to the airline. But sandwiched between flight problems, I had a great time in Wiesbaden at tekom/tcworld 2011.
The slides from my tekom/tcworld session on the economics of information are below.
In my junk mail, the capital letters were screaming in bright red: WE’RE NOT ARTISANS.
A wise man once told me that the goal of marketing is to frame the question so that what you are selling is the best possible answer. In the world of tech comm publishing, the default question has been: “What tool should I use?”
My 2011 predictions post included a brief mention of curation analytics. This week, we have news from MindTouch that supports my thought that accountability in technical communication will increase.
Content strategy is usually thought of in the context of web development. But today’s software is increasingly information-rich. Software is a content vector, and we need to manage the life cycle of that content. This webcast from guest speaker Ray Gallon adapts content life cycle management principles, taken from web-oriented content strategy, to software development cycles. Some examples from real experiences illustrate this adaptation.
