Welcome back to our series on content strategy.
In part one, we learned what a component content strategy is. In part two we discussed the risks and benefits for creating a strategy. Now, I will share the best practices on implementing your component content strategy with Author-it.
In order to capture the authentic thought leadership behind these practices, I spoke to our very own expert, Tom Erber, Director, Content Strategy at Author-it. Tom’s expertise began when he managed a team using Author-it at HP. He designed a content strategy that resulted in over 80% reuse! Now, he is sharing that knowledge by designing and implementing component content strategies for some of the largest companies around the world. The following paragraphs summarize my discussions with Tom.
What is Author-it’s secret ingredient?
As we know from past blogs and our white paper on Why Components components are core to Author-it. These chunks of information are critical because they liberate writers from the symbolic chains of documents.
However, the challenge with changing from a document-based paradigm to that of components is in how you manage, hundreds, thousands or even millions of components that make up your documentation. The secret is the relational database that manages all of the relationships between components, allowing writers to quickly find and reuse existing content.
In one case study, an organization was challenged to produce a 100-document project with 50,000 words and translated into 7 different languages. The chart below shows that by utilizing a relational component strategy, the company was able to reduce the costly authoring processes by 81%.
Additionally, compared to traditional authoring processes, relational content strategies can provide organizations with an 80% improvement in content quality and consistency with a 28% improvement in time to market execution.
To mimic these results, consider the following best practices:
Best Practices with Author-it
Maintaining the integrity of information is important. Whether the content is restricted for legal or regulatory purposes, or perfectly written, reviewed and translated, you probably don’t want people to tamper with the content after it has been released. If you are using an unprotected folder structure that allows a variety of people to access it, you could be jeopardizing your work.
Author-it’s folder structure enables user & group security through Folder Action Permissions. Folder Action Permissions determine which actions a user can take with the components in a particular folder. For example, all users may be able to create content in a particular folder, but only certain users can edit, and only the creator can delete a component. Security can also be ensured with the workflow functionality in Author-it called “release states”. For example, in the “Draft” release state, you can set it up so that all users can edit, but once in the “Released” state, the information is locked. Ultimately, this helps ensure the security and integrity of your information for compliance, consistency and future reuse.
Consider the process for most organizations of authoring, reviewing and publishing: the initial inputs are from many authors, the review team is usually made up of different subject matter experts (SMEs), and the published output has to accommodate a variety of audiences. With all the variations and new inputs throughout the content’s lifecycle, even highly organized workflows can present opportunities for mistakes and bottlenecks.
However, working in Author-it allows workflows to be monitored and managed throughout the entire process. Authors are able to assign specific SME reviewers to specific components, thus controlling who is able to edit and review the content. Now, the product team is able to reuse a component that the SME helped collaborate on, ensuring accuracy and consistency. This process can reduce the SME’s time by 50% and increase the quality and consistency by 100% because there is a single source for each component.
Remember, Author-it’s secret ingredient is the relational database. This is the key to achieving 70-90% reuse.
Because components are managed in a relational database you are able to quickly find and reuse components when you are creating new documents. Simply insert the already written component into your document and move on to the next section. Even better, Author-it Xtend is a patented feature within Author-it that intelligently suggests similar or identical components as you are writing. So instead of searching the database for a component, the component comes to you. It’s easy to see how this greatly saves time, maintains consistent messaging and ensures compliance.
At the conclusion of this three part blog series, you can look back and understand how important a content strategy is. With Author-it, a content strategy can be effectively established and managed throughout the entire company. From components, to your finished published outputs, it is a solution with the world’s content problem in mind.
Check out our website to learn how you can work with us to start designing your Author-it Component Content Strategy today!