Calculating the ROI for XML and DITA
I delivered this presentation on October 2 at Lavacon 2010 in San Diego. Many thanks to the noble souls who showed up at 8 a.m. (!) on a beautiful Saturday (!!) morning.
I delivered this presentation on October 2 at Lavacon 2010 in San Diego. Many thanks to the noble souls who showed up at 8 a.m. (!) on a beautiful Saturday (!!) morning.
By default, managers and executives see technical communication as a cost center, similar to a QA department or a Human Resources group.
“Necessary evil” is not where you want to be for great career success.
This year is shaping up as the Year of the Many Datasheets. Several customers approached us with variations on this theme:
In this webcast, Sarah O’Keefe of Scriptorium surveys DITA’s publishing options and weighs their practical implications.
In our latest hiring round, I’m seeing something new: candidates with existing social media networks. If we hire one of these candidates,
Anne Gentle, in the post Writing Engaging Technical Documentation, says this:
I love it when I hear people say, “I no longer work for development. I work for the user.”
Based on a quick Google search, things don’t look too hot for publishing:
Thanks to Peg Mulligan for hosting my guest post at her blog Content for a Convergent World. I wrote about the evolving role of the gatekeeper and the implications for technical communicators. Read the whole thing.
Content is like food. At its best, it’s a carefully choreographed experience, like dining at a fine restaurant.