Trends in technical communication, 2014 edition
Our annual prognostication, along with an assessment of our predictions from last year.
Our annual prognostication, along with an assessment of our predictions from last year.
Having worked at two translation companies and on many projects requiring localization, I appreciate just how nimble LSPs (language service providers) can be. Their ability to track down translators with the necessary subject matter expertise and handle a vast array of file formats is truly remarkable. That said, localization efficiency is dependent on you, the content provider.
Does this sound familiar?
One reason for lack of accountability is the we-meeting. You know the one: “We need a new process for handling customer service issues.” Lots of discussion follows, but no clear direction is given, nor is any responsibility taken.
Bruce Clarke (The View from HR column) referencing consultant Kathleen Kelly
Content velocity is the speed at which we create and produce content, the speed of the publishing process itself, and the speed of change in content requirements—what we need to produce and the delivery mechanisms.
For remote work, file management in the cloud is way easy. Other methods, not so much…
It can be a mightily sucktacular experience when you discover what other people think technical communicators do.
Knowing you can rely on someone is vital to professional relationships. But when it comes to proposing process change, the words “trust me” are never, ever enough.
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.
Getting attractive PDF output out of XML is a serious technical challenge. But in some organizations, the PDF requirement is being used to prevent to unwanted workflow changes.