23.11.2013 Aufrufe

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

MEHR ANZEIGEN
WENIGER ANZEIGEN

Erfolgreiche ePaper selbst erstellen

Machen Sie aus Ihren PDF Publikationen ein blätterbares Flipbook mit unserer einzigartigen Google optimierten e-Paper Software.

Content Strategies<br />

CS 11<br />

Workshop<br />

Building a Business Case for Content Strategy<br />

Sarah S. O’Keefe, Scriptorium Publishing, Raleigh-Durham, USA<br />

Content people, as a group, are terrible at business cases. In discussions<br />

about content challenges, the content creators usually have a long list<br />

of valid complaints about bad tools, inefficient processes, and generally<br />

wasted resources. But at the first mention of a potential solution that<br />

costs more than $100, content creators respond, “Oh, they will never approve<br />

that. We never get any money.”<br />

It is true that “they”—which is to say upper management—do not respond<br />

well to requests for large sums of money. What they do understand<br />

is business cases, such as, “To prevent us from wasting Y amount<br />

of resources every year, we need X amount of money this year,” and X is<br />

smaller than Y.<br />

Building a business case requires you to quantify how an investment<br />

(in tools, technology, training, or anything else) will improve business<br />

results. It is not sufficient to claim that your content strategy will contribute<br />

to business goals; you must estimate the improvement and show<br />

that the results are worth the investment. It helps when your estimates<br />

are obviously erring on the conservative side and the savings shown are<br />

still compelling.<br />

Estimating the business value<br />

Increased content reuse and efficient localization are the most common<br />

ways to show value in a business case for technical content.<br />

For reuse, you contrast the cost of writing or maintaining a topic with<br />

the cost of reusing a topic automatically. If the proposed system can<br />

increase the amount of reuse, you have a clear cost savings. Typical tech<br />

comm estimates in this area are as follows:<br />

−−<br />

Current reuse: 5 percent<br />

−−<br />

Estimated reuse with new strategy: 20 percent<br />

If the cost of maintaining a topic is estimated at €100 and the organization<br />

has approximately 4000 topics, then a 15 percent increase in reuse<br />

results in savings of €60,000. If all of the topics are updated in a typical<br />

year, this is a yearly cost savings.<br />

For localization, you need to look at the cost of reformatting translated<br />

text. In less-efficient environments, that cost is approximately 50 percent<br />

of the overall content localization cost. But in this example, we will<br />

use a more conservative 25 percent:<br />

−−<br />

Cost of localization, per word: €0.10<br />

−−<br />

Percentage of localization cost associated with formatting: 25 percent<br />

Again, we assume 4000 pages of content being translated and 250 words<br />

per page. The cost is therefore €100,000 per target language. If formatting<br />

is automated, the organization saves €25,000 per target language in<br />

each localization pass.<br />

64<br />

<strong>tekom</strong>-<strong>Jahrestagung</strong> <strong>2012</strong>

Hurra! Ihre Datei wurde hochgeladen und ist bereit für die Veröffentlichung.

Erfolgreich gespeichert!

Leider ist etwas schief gelaufen!