Making localization “better”
This post is the first in a series about the value proposition of localization strategies. You can also see a presentation on this topic at LavaCon this October.
Localization issues are a primary reason companies seek help with a new content strategy. One of the most common questions we hear is, “How do we make our localization process better?”
When we’re asked this question, we turn the question around. What is wrong with your current localization process? What would you like to improve? How do you define “better?”
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.
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.
Considering the true costs of customized structures: DITA specialization
Balancing the standardization of structured content against creative requirements is not just about formatting. When companies choose an XML standard, such as DITA or DocBook, they must evaluate whether to use the default structure or modify it to better fit requirements. The discussion about such changes is a creative process itself. When should a company change default structures?
The second wave of DITA
You have DITA. Now what?
More companies are asking this question as DITA adoption increases. For many of our customers, the first wave of DITA means deciding whether it’s a good fit for their content. The companies that choose to implement DITA find that it increases the overall efficiency of content production with better reuse, automated formatting, and so on.
Top eight signs it’s time to move to XML
How do you know it’s time to move to XML? Consult our handy list of indicators.
Sturm und DITA-Drang at tekom
This year’s tekom/tcworld conference reinforced the ongoing doctrinal chasm between North American technical communication and German technical communication.
I am speaking, of course, of the proper role of DITA in technical communication. If any.
The commodity trap
In a recent post on lean content strategy, I wrote about a focus on waste reduction:
After creating a nice automated XML-based process, waste in formatting is eliminated, and we declare victory and go home. Unfortunately, the organization is now producing irrelevant content faster, and the content organization is now positioned as only a cost center.
Is your content perceived as a commodity?
Lean content strategy
Lean manufacturing begat lean software development which in turn begat lean content strategy.
What does lean content strategy look like?
