Diff for Making the Business Case for DITA

Fri, 2008-04-18 00:48 by Bob DoyleFri, 2008-04-18 00:50 by Bob Doyle
Changes to Body
Line 1Line 1
 
<p class="rightalign">
 
<p class="rightalign">
 
<a href="/wiki/is-content-management-important">Content management</a> <br />
 
<a href="/wiki/is-content-management-important">Content management</a> <br />
-
<a href="/wiki/is-structure-important">Structure</a> <br />
+
<a href="/wiki/is-structure-important">Content structure</a> <br />
 
<a href="/wiki/is-content-reuse-important">Content reuse</a> <br />
 
<a href="/wiki/is-content-reuse-important">Content reuse</a> <br />
 
<a href="/wiki/is-single-sourcing-important">Single source</a> <br />
 
<a href="/wiki/is-single-sourcing-important">Single source</a> <br />
Line 69Line 69
 
If you have quantitative estimates of your content (pages x words/page), the fraction of content that can be reused, and the number of localization languages, you might run a simple calculation of your cost savings.
 
If you have quantitative estimates of your content (pages x words/page), the fraction of content that can be reused, and the number of localization languages, you might run a simple calculation of your cost savings.
 
</p>
 
</p>
-
<h3>Your D.Q. (DITA Quotient) </h3>
+
<h3>Your D.Q. (DITA Quotient) </h3>
 
<p>
 
<p>
 
We are developing a ten-question DITA Quotient to help organizations get a quantitative measure of the importance of DITA for their current content.
 
We are developing a ten-question DITA Quotient to help organizations get a quantitative measure of the importance of DITA for their current content.
 
</p>
 
</p>
 
 
Revision of Fri, 2008-04-18 00:50:

Making the Business Case for DITA

Content management
Content structure
Content reuse
Single source
Translation
Metadata markup
Modularity
Conditional processing
Task-oriented and Minimalism
Standardization

To make the business case for DITA, you must align its many powerful features with specific needs in your business or organization.

DITA has many features based on decades of research in methods for technical documentation - like modularity, structured writing, information typing, minimalism, inheritance, specialization, simplified XML, single-source, topic-based, ready-made metadata, conditional processing, component publishing, task-orientation, content reuse, multi-channel, and translation-friendly. See History of DITA.

Few organizations are likely to use all the features of DITA, but you should go through our checklist to determine which features could provide a significant return on investment in your particular business case. Use those features with positive returns in building your arguments for DITA.

ROI Calculations


First, you need your investment and total cost of ownership (TCO). Your investment is likely to be much greater than the direct costs for DITA technology - the basic software licenses and the hardware infrastructure needed in IT to support the component content publishing system.

Your TCO must include the expense to retrain writers to write topics using new editing tools. Change management costs will result from personnel turnover - expect that some senior writers are likely to resign rather than change their writing style (if possible, try to determine who they might be before putting them through expensive training). You will have new costs for specialists who can analyze and organize your content for structured delivery.

If you have quantitative estimates of your content (pages x words/page), the fraction of content that can be reused, and the number of localization languages, you might run a simple calculation of your cost savings.

Your D.Q. (DITA Quotient)

We are developing a ten-question DITA Quotient to help organizations get a quantitative measure of the importance of DITA for their current content.

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I