Webcast recording: Balancing standardization against the need for creativity
In this recorded webcast, learn about three cases studies that show how companies balance standardization and creativity in XML publishing.
Your content strategy easy win
You have a content strategy plan. Management has agreed to fund implementation. Time for the happy dance, right?
A little celebration is in order. But you still have to prove your new strategy will work in the real world. Showing early success with an “easy win” during implementation will give you momentum.
Pokémon GO and community documentation
Yes, I’m playing.
Even if you aren’t twitchily checking your phone and resisting the urge to run outside to catch a Pikachu or Gyrados, you’ve probably heard all about the phenomenon of Pokémon GO. One of the most common criticisms of the game is that the in-app documentation is sparse at best. In response, the community banded together and began to document their theories and findings. You can readily find articles covering “eeveelutions,” theories on how to more easily capture Pokémon, and how to capture opposing gyms. It hearkens back to a time of meeting up in schoolyards to swap tips and rumors.
Business case/ROI
Content management
Content reuse
DITA
DITA XML—authors
Localization
Structured content
Translation
Reduce translation costs with XML
$0.21 per word.
That’s the average cost in the US to translate content into another language according to Slator, a translation news and analytics site. That number is not speculative; they analyzed the costs per word from over 80 actual proposals gathered by the US General Services Administration (GSA). You can view the source proposals here.
The Rocky Road to Dublin, er, DITA
For LavaCon Dublin, Sarah O’Keefe and I delivered a case study presentation on some of the roadblocks we have encountered in implementing DITA at ADP. This article summarizes the key points of the presentation. The presentation and this blog do not represent the views of ADP, LLC.
Is your content overhead or a customer delight?
Delight is the difference between what you and your team cost, and the revenue you directly (or indirectly) produce (or protect). This concept is as important to charities as hedge funds.
You may not think that “delighting” customers is part of your content creation responsibilities. But when customer delight is defined in terms of revenue and costs, it suddenly becomes a critical part of your job.
Content strategy patterns in the enterprise
What factors affect content strategy decisions? Every client has a different combination of requirements, and of course there are always outliers. But based on our consulting experience, here are some factors that affect content strategy decisions.
SubjectScheme explained
Your project is coming along nicely. You have your workflow ready, your style guides are composed, and things are looking up. However, you have complex metadata needs that are starting to cause problems. You need a way to ensure that authors are only using valid attribute values, and that your publication pipeline isn’t going to suffer. This is a situation that calls for a subjectScheme.
Localization testing: it’s not just translation
It takes considerable planning and effort to run a successful localization project, from following best practices to evaluating vendors to finding and fixing the weakest link in the localization chain. But the localization process does not end when you receive the translations. Localization testing is necessary for ensuring that your content and products are ready for a distributed global release.
Do you know a content strategy concrete head?
In lean management, a concrete head is someone resistant to change. In my years working on content strategy projects, I have noticed many people are resistant to changing how they develop and distribute content—sometimes without even knowing it.
