From toilets to techcomm: tallying tool risks
I’m about to replace an old toilet, not-so-affectionately nicknamed the Lazy River.
Tag: content strategy
The true cost of incumbency bias
When selecting authoring and publishing tools, there is an unfortunate human instinct to cling to the familiar. This ranges from a slight preference for the tool currently in use to “You will pry this software from my cold, dead hands.”
Let go of your silo
In reality, collaborative authoring is little more than a euphemism for the idea that “anyone can write.”
That’s Tom Johnson’s take on collaborative authoring in his latest blog post. The writer in me sympathizes deeply because the “anyone can write” attitude is a direct challenge to the careers of professional writers.
New to tech comm? Expect the unexpected
When I started at Scriptorium a year ago, I knew almost nothing about tech comm. I knew what technical content was, having used it many times, but I’d never really thought about how it was produced.
Hug it out with your IT department: collaboration beyond content
The stereotypical technical writer working in isolation is an endangered species—if not already extinct.
Banishing our black berets
In my junk mail, the capital letters were screaming in bright red: WE’RE NOT ARTISANS.
You don’t have to bet the farm…
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?”
Webcast: Content strategy for software development (with Ray Gallon)
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.
Content monoculture
I’m having some trouble with the idea of “extending DITA” outside the world of technical communication. DITA is obviously important in the right environment, but should we be advocating the use of DITA for more and more content?
