Upon completion of testing, the knowledge engineering team is assembled and prepared to begin work on the content migration efforts. These knowledge engineering resources could be internal team members, outsourced from a third-party vendor or both.
Tip: If you intend to use knowledge engineering resources secured with a third-party vendor, allow at least 8 weeks to complete the SOWs, contracts, and knowledge engineer vetting process. Once the administrative steps are completed, knowledge engineers will be available when you need them.
What your knowledge engineering team does
The work that this team is responsible for differs depending on the migration option selected. For manual content migration efforts, the knowledge engineers assume responsibility to physically migrate the content in alignment with content standards and quality expectations. For a scripted migration effort, knowledge engineer resources assume responsibility to apply the specific content standards to each article after the automated migration scripts have been completed. This is necessary in some cases because formatting and content optimization is not always possible when scripting the migration.
Choosing the right knowledge engineering resource tool
It can be very challenging to coordinate the content migration efforts of a team of people without the help of a tool to keep it organized. Consider using a tool like Irrevo’s KnowledgeAQ to assign and monitor the progress of the team members. It is also helpful as a load-balancing tool. This is especially true when content migration involves content of varying complexity.
Tracking quality and output measures
Regardless of the tool you use to manage the work, plan to track quality and output measures for this team. If you outsource the knowledge engineering resources, request that the vendor provide this level of detailed monitoring to ensure that all team members are providing maximum value.
During this phase, the knowledge engineering resources are trained on all the aspects needed to complete the tasks they are responsible for in the project. This includes tool training and migration-specific tasks.
Tip: Have each knowledge engineer migrate 4-6 articles and then review together for quality and consistency. Address issues of inconsistency as they arise.