<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>ComTech Services</title>	<link>http://tc.eserver.org/publisher/ComTech_Services</link>
	<description>A listing of works published by ComTech Services in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>ComTech Services</title>
		<link>http://tc.eserver.org/dir/ComTech_Services</link>
	</image>
	<item>
		<title>Developing DITA Maps</title>
		<link>http://tc.eserver.org/34722.html</link>
		<guid>http://tc.eserver.org/34722.html</guid>
		<description>DITA maps provide a mechanism for ordering topics and creating a topic hierarchy. Because DITA maps consist of lists of references to topics, you can reorganize the content in a deliverable simply by changing the order of the topic references. You can create different maps referencing the same source topics to create two deliverables to meet different users&apos; needs.</description>
	</item>
	<item>
		<title>Information Design: The Key to Reuse</title>
		<link>http://tc.eserver.org/22166.html</link>
		<guid>http://tc.eserver.org/22166.html</guid>
		<description>Discusses the problems with poor information design: no consistent suite of information, no consistent structure, or idea how customers use their information.</description>
	</item>
	<item>
		<title>One Source, Five Deliverables: A Case Study of Return on Investment</title>
		<link>http://tc.eserver.org/22174.html</link>
		<guid>http://tc.eserver.org/22174.html</guid>
		<description>A case study of the implementation of a single-sourse content management system.</description>
	</item>
	<item>
		<title>Single-Source Content Management: If, Why and How</title>
		<link>http://tc.eserver.org/22165.html</link>
		<guid>http://tc.eserver.org/22165.html</guid>
		<description>Introduces the five levels of single-sourcing.</description>
	</item>
	<item>
		<title>An Application of the Principles of Minimalism to the Design of Human-Computer Interfaces</title>
		<link>http://tc.eserver.org/22147.html</link>
		<guid>http://tc.eserver.org/22147.html</guid>
		<description>Minimalism in information design, specifically as applied to user tutorials and manuals, was introduced in the early 1980s through the work of Dr. John M. Carroll, then a cognitive psychologist at the IBM Watson Research Center. Since that time, theorists and practitioners have further elucidated the principles of minimalism and have attempted to apply it to a variety of situations in which people attempt to learn how to use a software application. Most recently, a new exposition of minimalist principles and practices was published by MIT Press. This work, &lt;i&gt;Minimalism Beyond the Nurnberg Funnel,&lt;/i&gt; represents the work of leading theorists and practitioners in the field.</description>
	</item>
	<item>
		<title>Demystifying Information Modeling</title>
		<link>http://tc.eserver.org/22152.html</link>
		<guid>http://tc.eserver.org/22152.html</guid>
		<description>The information model is a framework for organizing all the information people need.</description>
	</item>
	<item>
		<title>Developing a Content-Management Strategy: Implications in a Multi-Language Environment</title>
		<link>http://tc.eserver.org/22156.html</link>
		<guid>http://tc.eserver.org/22156.html</guid>
		<description>Why we went to a single-source CMS and how we went about it.</description>
	</item>
	<item>
		<title>De Information Process Maturity Model (IPMM)</title>
		<link>http://tc.eserver.org/22159.html</link>
		<guid>http://tc.eserver.org/22159.html</guid>
		<description>There are several reasons for the Information Process Maturity Model: moving beyond chaos; moving beyond the heroism of talented and dedicated individuals; moving toward a repeatable, reliable process.&#xD;It is the reality of the 21th Century: People from the Western countries don&apos;t understand the real imagination of the post-soviet people in The Eastern European countries. &#xD;The matter is: we have not been living in a private property society &amp; and in a national liberal country till 1991. So, my personal and my colleagues&apos; experince had been summarised there in the publicity book &quot;BUSINESS in Ukraine&quot;. The main problem to solve is the countrywide system of a liberal market tersonality training. Everybody has to learn to be a master of its own personality and lot. &#xD;Oleksandr Nahornyy, author, editor, producer</description>
	</item>
	<item>
		<title>Let&apos;s Stop Writing Documentation and Start Working for the Users</title>
		<link>http://tc.eserver.org/22160.html</link>
		<guid>http://tc.eserver.org/22160.html</guid>
		<description>Nearly 20 years ago, the profession of technical communication began to focus on  developing task-oriented documentation. Although task-oriented documentation has  always been produced, particularly for consumer products, it was not the standard in  the computer industry. More often, people writing about computer systems focused  on the system rather than on the tasks people needed to perform. Systems-oriented documentation was the norm.</description>
	</item>
	<item>
		<title>Leveraging Complex Content for the Support Chain</title>
		<link>http://tc.eserver.org/22157.html</link>
		<guid>http://tc.eserver.org/22157.html</guid>
		<description>The support chain is becoming increasingly important as we begin to understand the deep underlying economic trends of the last half-century.</description>
	</item>
	<item>
		<title>New Manager&apos;s To-Do List</title>
		<link>http://tc.eserver.org/22151.html</link>
		<guid>http://tc.eserver.org/22151.html</guid>
		<description>The transition to technical publications management can be difficult.</description>
	</item>
	<item>
		<title>Selecting a Content-Management System</title>
		<link>http://tc.eserver.org/22155.html</link>
		<guid>http://tc.eserver.org/22155.html</guid>
		<description>It&apos;s not about buying a tool; it&apos;s about understanding your requirements.</description>
	</item>
	<item>
		<title>Selecting a Content-Management System</title>
		<link>http://tc.eserver.org/22154.html</link>
		<guid>http://tc.eserver.org/22154.html</guid>
		<description>A discussion of the features and functions of content management software packages.</description>
	</item>
	<item>
		<title>Seven Things New Managers Must Do in the First 90 Days</title>
		<link>http://tc.eserver.org/22149.html</link>
		<guid>http://tc.eserver.org/22149.html</guid>
		<description>Discusses the creation of managed and sustainable workflow.</description>
	</item>
	<item>
		<title>Stop Writing Documentation!</title>
		<link>http://tc.eserver.org/22161.html</link>
		<guid>http://tc.eserver.org/22161.html</guid>
		<description>Redesign your information; write topics, not books.</description>
	</item>
	<item>
		<title>Strategic Planning</title>
		<link>http://tc.eserver.org/22158.html</link>
		<guid>http://tc.eserver.org/22158.html</guid>
		<description>What is strategic planning? A process for determining: where you are; where you intend to be; how you’re going to get there.</description>
	</item>
	<item>
		<title>Twelve Weeks in the Life of New Manager</title>
		<link>http://tc.eserver.org/22150.html</link>
		<guid>http://tc.eserver.org/22150.html</guid>
		<description>A timeline for things to do when beginning a management position.</description>
	</item>
	<item>
		<title>Using the Information Process-Maturity Model for Strategic Planning</title>
		<link>http://tc.eserver.org/22148.html</link>
		<guid>http://tc.eserver.org/22148.html</guid>
		<description>Why should we be interested in strategic planning for our information-development organizations? We might simply apply specific tactics for getting our everyday jobs done. We might focus our concerns on producing a manual or getting the online help finished. We might even plan far enough in advance to send staff members to workshops on the latest online help development tools. These tactics would get us through the day, or the week, or even through the end of the year, and we would be busy doing useful things (or at least things that we hope others find useful). But as we keep busy doing our everyday jobs, we may find ourselves surprised by the decisions of those who decide to eliminate our function, outsource our tasks, or disperse our staff throughout the organization. Only then we will recognize that we lacked an overall goal, a vision of what we should be doing, of how we want to be perceived in the future.</description>
	</item>
	<item>
		<title>A Writer&apos;s Guide to XML Content Management</title>
		<link>http://tc.eserver.org/22153.html</link>
		<guid>http://tc.eserver.org/22153.html</guid>
		<description>A discussion of how XML changes what you do as a writer.</description>
	</item>
	<item>
		<title>Best Practices: A Case Study at Kohler</title>
		<link>http://tc.eserver.org/22141.html</link>
		<guid>http://tc.eserver.org/22141.html</guid>
		<description>The plumbing division of Kohler Co. is no stranger to managing their content. They had been using BroadVision&apos;s document-management system, Relation Document Manager  (RDM), for three years and authoring in Interleaf since 1989.  But when BroadVision stopped supporting RDM, Mark Peterson, the technical publications manager at Kohler, was desperate to find a replacement. BroadVision offered BladeRunner,  but that tool didn&apos;t sufficiently support the heavy and stringent  print requirements of Mark&apos;s department. Plumbers don&apos;t  always have adequate or readily available access  to the Internet.</description>
	</item>
	<item>
		<title>Customer Partnering: Data Gathering for Complex Online Documentation</title>
		<link>http://tc.eserver.org/22144.html</link>
		<guid>http://tc.eserver.org/22144.html</guid>
		<description>Technical communicators today must document complex  applications used in complex environments. Information about users and use models is important under these conditions, especially if documentation will be presented online.  Customer partnering, a method of information gathering that  supplements surveys, contextual inquiries, usability testing,  and interviews, provides a way of involving the users of complex applications in the design of information delivery systems. We used this method to help a client gather important information about user and use models and design a new information library for complex server computer systems.</description>
	</item>
	<item>
		<title>The DuPont Experience: Strategic Planning for Information Design and Development Organizations</title>
		<link>http://tc.eserver.org/22145.html</link>
		<guid>http://tc.eserver.org/22145.html</guid>
		<description>This is a reprint of an article first published in Technical Communication. It explains the strategic planning experience of the Information Design and Development organization in DuPont&apos;s External Affairs division. The author describes why they undertook a strategic planning initiative, the process used, the logistics involved in preparing for and carrying out the process, and the results of their work. Their experience can be applied by technical communication work groups seeking to define and communicate their mission and value proposition within their organization. Original publication:&#xD;Breuninger, Charles L. 1997. “The DuPont Experience:&#xD;Strategic Planning for Information Design and Development&#xD;Organizations.” Technical communication 44:394–400.</description>
	</item>
	<item>
		<title>Enabling Language Translation with XML Tools and  Standards</title>
		<link>http://tc.eserver.org/22143.html</link>
		<guid>http://tc.eserver.org/22143.html</guid>
		<description>Maintaining consistency between a source document and its translated counterparts can be complex and troublesome. Innumerable challenges can arise with character sets, version control, text in graphics, tables, expansion of text, updates, and so on. Using XML for translation can help overcome some of these challenges. In this article, I explain how XML tools and standards can help remedy tricky issues related to translation.</description>
	</item>
	<item>
		<title>Integrating Training and Documentation</title>
		<link>http://tc.eserver.org/22146.html</link>
		<guid>http://tc.eserver.org/22146.html</guid>
		<description>The potential problems I detailed in working to integrate training and documentation functions do indeed occur in many organizations. They have also found that working out the problems is worth the effort.</description>
	</item>
	<item>
		<title>Making the Business Case for Single Sourcing</title>
		<link>http://tc.eserver.org/22138.html</link>
		<guid>http://tc.eserver.org/22138.html</guid>
		<description>Discusses ways to communicate the financial benefits, customer value, learning and growth opportunities, and internal process improvements made possible by single sourcing.</description>
	</item>
	<item>
		<title>Oblivious Organizations and Content Management: Not Yet Ready for Prime Time</title>
		<link>http://tc.eserver.org/22142.html</link>
		<guid>http://tc.eserver.org/22142.html</guid>
		<description>In brief, documents are created everywhere by everyone.  They each develop the documents any way they like, with no common look and feel. Company officials have vehemently  opposed hiring technical communicators for the R&amp;D teams.  They feel that the engineers know the products best and should be able to write about them. Marketing materials are created  independently by many different marketing staff and even by executives who regularly post announcements to the company intranet and Internet sites.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/ComTech_Services.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>