<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Does DITA Make You Dumb?</title>
	<atom:link href="http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/feed/" rel="self" type="application/rss+xml" />
	<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/</link>
	<description>A Real World Guide to Managing Technical Documentation</description>
	<lastBuildDate>Sun, 15 Aug 2010 13:41:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: &#160; Weekly links roundup&#160;by&#160;Communications from DMN</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4471</link>
		<dc:creator>&#160; Weekly links roundup&#160;by&#160;Communications from DMN</dc:creator>
		<pubDate>Fri, 16 Oct 2009 10:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4471</guid>
		<description>[...] Does DITA make you dumb? [...]</description>
		<content:encoded><![CDATA[<p>[...] Does DITA make you dumb? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xadmin</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4387</link>
		<dc:creator>xadmin</dc:creator>
		<pubDate>Sat, 10 Oct 2009 17:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4387</guid>
		<description>Milan,

Absolutely true. A lot of this discussion has nothing at all to do with the quality of documentation. It&#039;s all about perception. Do managers &quot;perceive&quot; that DITA makes it possible to hire cheaper writers? Do writers perceive that DITA will narrow their field or put them in a writing straitjacket? 

That doesn&#039;t mean the discussion isn&#039;t relevant, but it does take it away from the core of what technical communicators are supposedly paid to do.</description>
		<content:encoded><![CDATA[<p>Milan,</p>
<p>Absolutely true. A lot of this discussion has nothing at all to do with the quality of documentation. It&#8217;s all about perception. Do managers &#8220;perceive&#8221; that DITA makes it possible to hire cheaper writers? Do writers perceive that DITA will narrow their field or put them in a writing straitjacket? </p>
<p>That doesn&#8217;t mean the discussion isn&#8217;t relevant, but it does take it away from the core of what technical communicators are supposedly paid to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Milan Davidovic</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4383</link>
		<dc:creator>Milan Davidovic</dc:creator>
		<pubDate>Sat, 10 Oct 2009 02:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4383</guid>
		<description>@Richard -- I get &quot;devaluation of the field&quot;, but I don&#039;t think that documentation quality necessarily suffers because of it. It could, but it doesn&#039;t have to.</description>
		<content:encoded><![CDATA[<p>@Richard &#8212; I get &#8220;devaluation of the field&#8221;, but I don&#8217;t think that documentation quality necessarily suffers because of it. It could, but it doesn&#8217;t have to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul K. Sholar</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4380</link>
		<dc:creator>Paul K. Sholar</dc:creator>
		<pubDate>Fri, 09 Oct 2009 17:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4380</guid>
		<description>I don&#039;t agree that DITA does anything to ensure &quot;higher quality&quot; documentation or to produce documentation that &quot;look good&quot;--probably quite the contrary due to the paucity of formatting control provided by XSL-FO, compared with the previous generation of print-oriented desktop publishing tools such as FrameMaker. Rather DITA is a means to enforce a particular three-class structuring scheme for text. The quality of documentation comes from its fitness for its purpose. Regarding &quot;devaluing&quot; of documentation, I would say this is the marketplace&#039;s response to low-quality documentation. Low-quality documentation tends to correlate with poorly designed products. Low-quality documentation also tends to correlate with less skilled technical writers, regardless of product quality. My main concern with DITA, and with the topic-based model for authoring documentation, is that the scope of the tech writer&#039;s required knowledge shrinks. There is no longer the need to know the great sweep of the product&#039;s intended use. That knowledge migrates strongly back into the product development team; the old TWs must now consider moving to product development as a &quot;usability&quot; expert who may or may not have expertise in the product&#039;s functional domain. My understanding today is that &quot;usability&quot; means mostly a person who focuses on web page design and screen layout, not functional workflow; I hope I&#039;m wrong about that. If I&#039;m not wrong, I see a long future ahead of poorly designed computer products with dumbed-down technical writers struggling to write topics that, as a set, don&#039;t come close to meeting the customer&#039;s needs.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t agree that DITA does anything to ensure &#8220;higher quality&#8221; documentation or to produce documentation that &#8220;look good&#8221;&#8211;probably quite the contrary due to the paucity of formatting control provided by XSL-FO, compared with the previous generation of print-oriented desktop publishing tools such as FrameMaker. Rather DITA is a means to enforce a particular three-class structuring scheme for text. The quality of documentation comes from its fitness for its purpose. Regarding &#8220;devaluing&#8221; of documentation, I would say this is the marketplace&#8217;s response to low-quality documentation. Low-quality documentation tends to correlate with poorly designed products. Low-quality documentation also tends to correlate with less skilled technical writers, regardless of product quality. My main concern with DITA, and with the topic-based model for authoring documentation, is that the scope of the tech writer&#8217;s required knowledge shrinks. There is no longer the need to know the great sweep of the product&#8217;s intended use. That knowledge migrates strongly back into the product development team; the old TWs must now consider moving to product development as a &#8220;usability&#8221; expert who may or may not have expertise in the product&#8217;s functional domain. My understanding today is that &#8220;usability&#8221; means mostly a person who focuses on web page design and screen layout, not functional workflow; I hope I&#8217;m wrong about that. If I&#8217;m not wrong, I see a long future ahead of poorly designed computer products with dumbed-down technical writers struggling to write topics that, as a set, don&#8217;t come close to meeting the customer&#8217;s needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Kunz</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4350</link>
		<dc:creator>Larry Kunz</dc:creator>
		<pubDate>Wed, 07 Oct 2009 19:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4350</guid>
		<description>This article, and the comment from Wallis Sholar, has gotten me thinking. More here: http://www.sdiglobalsolutions.com/Default.aspx?tabid=77&amp;articleType=ArticleView&amp;articleId=45</description>
		<content:encoded><![CDATA[<p>This article, and the comment from Wallis Sholar, has gotten me thinking. More here: <a href="http://www.sdiglobalsolutions.com/Default.aspx?tabid=77&amp;articleType=ArticleView&amp;articleId=45" rel="nofollow">http://www.sdiglobalsolutions.com/Default.aspx?tabid=77&amp;articleType=ArticleView&amp;articleId=45</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julio Vazquez</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4330</link>
		<dc:creator>Julio Vazquez</dc:creator>
		<pubDate>Tue, 06 Oct 2009 18:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4330</guid>
		<description>I agree with Wallis. It&#039;s not the technology that will lead to fewer jobs for writers, but what those writers bring to the mix. As a writer becomes less of a &quot;form filler&quot; and more of a asset to product development by making sure that the customers spend less time in the documentation. This can be done many ways: by making sure the interface is more intuitive, by making sure the any messages from the software are clear and concise, and by making sure that any necessary documentation is clear and concise also. The modularity is important to help integrate the information more closely to the product. 

As for &quot;connective tissue&quot;, even without the publishing specialization, you just need to write the connective prose for those outputs that require them. DITA doesn&#039;t prevent you from having untyped topics used for this sort of thing, the philosophy just discourages it. That said, there&#039;s nothing that prevents you from creating those topics for use only in a book format of the information and using a different DITA map for the online. You can repurpose the base set of topics to whatever output format you want and tailor it to a degree.</description>
		<content:encoded><![CDATA[<p>I agree with Wallis. It&#8217;s not the technology that will lead to fewer jobs for writers, but what those writers bring to the mix. As a writer becomes less of a &#8220;form filler&#8221; and more of a asset to product development by making sure that the customers spend less time in the documentation. This can be done many ways: by making sure the interface is more intuitive, by making sure the any messages from the software are clear and concise, and by making sure that any necessary documentation is clear and concise also. The modularity is important to help integrate the information more closely to the product. </p>
<p>As for &#8220;connective tissue&#8221;, even without the publishing specialization, you just need to write the connective prose for those outputs that require them. DITA doesn&#8217;t prevent you from having untyped topics used for this sort of thing, the philosophy just discourages it. That said, there&#8217;s nothing that prevents you from creating those topics for use only in a book format of the information and using a different DITA map for the online. You can repurpose the base set of topics to whatever output format you want and tailor it to a degree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wallis Sholar</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4327</link>
		<dc:creator>Wallis Sholar</dc:creator>
		<pubDate>Tue, 06 Oct 2009 18:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4327</guid>
		<description>Not sure it&#039;s fair to say that DITA is &quot;dumbing down&quot; the craft of technical communication as much as it is &quot;speeding up&quot; the process of publishing better-quality documentation (to multiple endpoints). Good/valuable/expensive writers will continue to be in high demand for orgs whose customers demand well-constructed documentation. DITA doesn&#039;t make &quot;doc design&quot; decisions, it merely prevents writers from breaking style. A bad writer can write a perfectly &quot;legal&quot; document that isn&#039;t complete, concise, or accurate, but it will still &quot;look&quot; good. A good writer leverages the time savers built into a structured authoring environment and churns out documentation that not only looks good, but is complete, concise, and accurate, and the writer has done it in a fraction of the time that it would have taken using non-structured authoring tools.

At the end of the day, the customer will or won&#039;t demand great documentation-- the success of the dev effort will hinge on its ability to address the customer&#039;s demands. If the field is being devalued, it&#039;s being devalued by the customer, not the type of authoring environment. If it&#039;s being devalued by the customer, then that might be a sign that the user experience designed by the developers is rendering &quot;great&quot; documentation obsolete. I&#039;ve always maintained that the best-designed software requires the least documentation, and I think that&#039;s becoming more widely recognized. Better software keeps the user&#039;s nose out of the documentation, and with fewer noses in the documentation, companies can save money on writers and/or tech support staff. 

Something to consider: We might be seeing fewer jobs for mediocre writers because companies can churn out more and better documentation with a small staff of great writers and a structured authoring environment. In this paradigm, salaries remain constant or even improve some for the top 25% of professional writers. I think we&#039;re just seeing the development of a much more competitive job market for technical communicators, even after high tech fully recovers.</description>
		<content:encoded><![CDATA[<p>Not sure it&#8217;s fair to say that DITA is &#8220;dumbing down&#8221; the craft of technical communication as much as it is &#8220;speeding up&#8221; the process of publishing better-quality documentation (to multiple endpoints). Good/valuable/expensive writers will continue to be in high demand for orgs whose customers demand well-constructed documentation. DITA doesn&#8217;t make &#8220;doc design&#8221; decisions, it merely prevents writers from breaking style. A bad writer can write a perfectly &#8220;legal&#8221; document that isn&#8217;t complete, concise, or accurate, but it will still &#8220;look&#8221; good. A good writer leverages the time savers built into a structured authoring environment and churns out documentation that not only looks good, but is complete, concise, and accurate, and the writer has done it in a fraction of the time that it would have taken using non-structured authoring tools.</p>
<p>At the end of the day, the customer will or won&#8217;t demand great documentation&#8211; the success of the dev effort will hinge on its ability to address the customer&#8217;s demands. If the field is being devalued, it&#8217;s being devalued by the customer, not the type of authoring environment. If it&#8217;s being devalued by the customer, then that might be a sign that the user experience designed by the developers is rendering &#8220;great&#8221; documentation obsolete. I&#8217;ve always maintained that the best-designed software requires the least documentation, and I think that&#8217;s becoming more widely recognized. Better software keeps the user&#8217;s nose out of the documentation, and with fewer noses in the documentation, companies can save money on writers and/or tech support staff. </p>
<p>Something to consider: We might be seeing fewer jobs for mediocre writers because companies can churn out more and better documentation with a small staff of great writers and a structured authoring environment. In this paradigm, salaries remain constant or even improve some for the top 25% of professional writers. I think we&#8217;re just seeing the development of a much more competitive job market for technical communicators, even after high tech fully recovers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Kunz</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4326</link>
		<dc:creator>Larry Kunz</dc:creator>
		<pubDate>Tue, 06 Oct 2009 17:58:03 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4326</guid>
		<description>These are great points. I&#039;d like to hear your thoughts on how those of us in the DITA community can craft our messages to avoid the pitfall you mentioned -- namely that managers will misunderstand DITA and modular technology and that they&#039;ll seek less expensive, less skilled writers.</description>
		<content:encoded><![CDATA[<p>These are great points. I&#8217;d like to hear your thoughts on how those of us in the DITA community can craft our messages to avoid the pitfall you mentioned &#8212; namely that managers will misunderstand DITA and modular technology and that they&#8217;ll seek less expensive, less skilled writers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Hamilton</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4325</link>
		<dc:creator>Richard Hamilton</dc:creator>
		<pubDate>Tue, 06 Oct 2009 16:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4325</guid>
		<description>Milan,

I mean devaluation in a literal sense. That is, companies deciding to pay less for the services of people in that occupational field. I won&#039;t claim that society suffers, but I will claim that technical communicators could be faced with a job market where their services are perceived as having less value than before.

Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Milan,</p>
<p>I mean devaluation in a literal sense. That is, companies deciding to pay less for the services of people in that occupational field. I won&#8217;t claim that society suffers, but I will claim that technical communicators could be faced with a job market where their services are perceived as having less value than before.</p>
<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Milan Davidovic</title>
		<link>http://managingwriters.com/2009/10/06/does-dita-make-you-dumb/comment-page-1/#comment-4324</link>
		<dc:creator>Milan Davidovic</dc:creator>
		<pubDate>Tue, 06 Oct 2009 16:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://managingwriters.com/?p=124#comment-4324</guid>
		<description>Re: the &quot;devaluation of the field&quot; -- how does *society* suffer? Occupational fields come and go; what&#039;s the big picture concern here?</description>
		<content:encoded><![CDATA[<p>Re: the &#8220;devaluation of the field&#8221; &#8212; how does *society* suffer? Occupational fields come and go; what&#8217;s the big picture concern here?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
