Establishing implementation goals and metrics


The first implementation step is to identify your success criteria. Based on your business case, you can define what will make the project successful.

Table 1. Setting goals
Business case Example success criteria

Localization cost

Hold localization cost steady while adding two more languages.

Reduce lag time in localization content from four months to two weeks.

Improved search efficiency

Improve call center response times.

Increase call volume by 10 percent without increasing staff.

Marketing support

Increase web site engagement.

User community and loyalty

Increase number of registered users and active users by 20 percent over the next year.

Increased collaboration

Add 15 active users from engineering community.

Content reuse

Increase percentage of reused content in source documents from 10 percent to 20 percent.

Each organization has different goals, expectations, and metrics. The key is to spell out the targets before the project begins.

The initial project specification should also include the following:

  • A list of required deliverables and deliverable paths (for example, HTML created using XSL transformation on XML files)
  • Any tool-specific requirements that affect the elements and attributes to be defined
  • A high-level description of the planned workflow

After defining goals, you can develop success criteria. This allows you to evaluate the project’s success when it is completed. Your criteria should include specific metrics. These might include items such as the following:

  • Number of deliverables per writer before and after implementation
  • Percentage of information reuse achieved
  • Time required to do “final polish” on deliverables

Once the business goals are established, and you have defined measurable success criteria, it’s time to consider who will do the actual implementation work.



Add comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.