Lean content strategy
Lean manufacturing begat lean software development which in turn begat lean content strategy.
What does lean content strategy look like?
Lean manufacturing begat lean software development which in turn begat lean content strategy.
What does lean content strategy look like?
Metadata is one of the most important factors in making the most of your DITA XML-based content environment. Whether you’re converting legacy content into DITA or creating new structured content, it’s important to know what metadata (or data about data) your files will keep track of and why. Coming up with a plan for using metadata can be tricky, so here are some tips to make the process easier.
This premium post is a recap of a presentation delivered by Sarah O’Keefe at Localization World Berlin on June 4, 2015. It describes how and why to align localization strategy to the customer journey.
The new buzzword in marketing is the customer journey. What does this mean for localization?
General Stanley McChrystal offers sage leadership advice you can apply to your content strategy.
Here are your marching orders:
Keeping a content strategy implementation moving forward is important, but it isn’t always easy. You may have to deal with an extremely slow-moving project or unexpected delay. You may even have to put a project completely on hold. Here are some common obstacles that get in the way of progress, and some ways you can work to overcome them.
What’s the best way to minimize conflict when developing and implementing a new content strategy?
You’ve probably heard the announcement countless times: “Please locate the nearest emergency exit.” Chances are you ignore these exits most of the time, but you feel safer knowing they’re there. You wouldn’t go to a restaurant or movie theater or travel on public transportation that didn’t have an emergency exit—so why would you develop a content strategy without one?
In a recent blog post, Alan Pringle brought up the the importance of having an exit strategy, and I wanted to expand on that idea. Without a plan for what to do if your implementation doesn’t go as expected, your company could face tremendous costs—in terms of both time and money—trying to move on to a system that works.
It finally happened. A part of your production pipeline has failed too many times, and everyone is in agreement: you need a hero.
You’re probably hearing it more and more: silos are bad for your business. They discourage collaboration, lead to duplication and inconsistency, and prevent you from delivering a unified content experience to your customers. But what really happens when you try to break them down?
This guest post is by Carlos Evia, Ph.D., the director of Professional and Technical Writing at Virginia Tech.
The DITA Troubleshooting topic is one of the “new” features in version 1.3 of the standard. However, troubleshooting has been around the DITA world for some good eight years now.