Project Management is the discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives.
Do You Sound Like a CEO Behind a Microphone?
"You have two options when you walk into a room," says public speaking expert Richard Levick about the art of giving speeches. Most entrepreneurs find speech making to be either terrifying or a waste of time. Too many CEOs see dealing with the media or making presentations as an interruption, but it's as essential to doing business as customers. If you can't deliver energetic and commanding speeches, or polished and articulate interviews, then you're short-circuiting your company's future. It's time to do something about it.
Krotz, Joanna L. Communication World Bulletin (2003). Articles>Presentations>Management>Rhetoric
Do-It-Yourself Single-Sourcing 
In recent years, countless articles and conference workshops have touted single sourcing as the Holy Grail of technical writing. Countless articles and conference workshops have also told us that XML is our means to achieving the Grail. However, in the absence of any off-the-shelf products that facilitate XML and single sourcing in our current work environments, I suspect that most people, particularly in smaller companies, believe that implementing XML is too technically daunting, too expensive, or both.
Wersan, Fred. Intercom (2003). Design>Content Management>Single Sourcing
Document (re)Presentation: Object-orientation, Visual Language, and XML

This article demonstrates how the combination of object-orientation and Horn's notions of visual language morphology, syntax, semantics, and pragmatics may be used to analyze and describe the mapping of marked-up XML files onto user documents. The article also raises the question of whether—or to what extent—the coupling of object-orientation and visual language might be exploited more directly for design purposes in a document production paradigm based on XML.
Johnsen, Lars. Technical Communication Online (2001). Design>Content Management>XML>Metadata
A directory of online resources about document management.
You need to anticipate the lifecycle of technical publications in advance so that all areas related to the final delivery are covered. These include issues such as costs, production, dissemination and archiving.
Document your Database Project to Capture Relevant Info 
Documenting a database during its development is a best practice to ensure that the organizational schema, data objects, and other related information are captured for future reference.
Kelly, William T. Builder.com (2003). Articles>Project Management>Databases>Documentation
A Documentation Database for Managing Time and Costs 
Keeping track of a technical writing team’s time can be a tedious task, especially when that time has to be charged to various internal departments. Using Lotus Notes™ (Lotus Development Corporation and Iris Associates, Inc.), we developed a relational database to track this information. This database uses a single form for all documentation status inputs. Then it summarizes the data in a variety of view. Separate forms track SEI statistics and simplify department employee time administration.
Lang, Darice and Debra Ricks. STC Proceedings (1994). Articles>Documentation>Project Management
Documentation Team Leadership in the 1990s 
In the 1990s, product life cycles are short, technology is ever-advancing, work environments are fast-paced, and there is an ongoing agenda to cut costs. This environment requires documentation teams to accomplish more faster with fewer personnel resources These requirements have redefined the roles and responsibilities of technical writers and documentation team leaders. Leadership skills have become critical to the overall success of documentation teams Critical leadership skills include appropriately implementing situational leadership, working effectively with people who have diverse working and social styles, and participating in ongoing role negotiations.
Muench, Barbara S. STC Proceedings (1995). Careers>Documentation>Management
Documentation Without Documents -- The COIL Model
A description of a Canadian content-management system from the early days of the emerging knowledge management industry. COIL is a document management system that manages the information held in documents, rather than the documents themselves. By integrating more than 1,500 hardcopy pages of legacy documentation into one on-line information resource, COIL provides chart producers with an effective way of consulting the standards and procedures for their GIS, and of managing revisions to those standards and procedures.
Documents That No Project Cannot Be Without
Short deadlines force project teams to quickly design, test, and release the product with little or no design documentation. If these documents are written, they generally are not well-written and are not comprehensive. The fact of the matter is that most project teams do not have enough staff to design the product, let alone write and manage documentation. This situation creates an ideal opportunity for technical writers to assist the project team in more ways than writing a user guide.
Dick, David J. Carolina Communique (2008). Articles>Documentation>Project Management>Collaboration
Does Your CEO Have Spokesperson Deficit Disorder (SDD)?
It's an all-too-common ailment, a not-so-silent killer of corporate reputation—often going undiagnosed even when the symptoms are evident. Early symptoms include negative or weak media coverage, "misquotes" and interviews that go off track. Although it can strike at any level within an organization, Spokesperson Deficit Disorder, or SDD, is perhaps most damaging if left untreated at the CEO level. So what can you do if your CEO suffers from this dreadful condition?
Gibson, Barbara. Communication World Bulletin (2007). Articles>Business Communication>Management
Does Your CMS Vendor Have Product Expertise?
Choosing a content management system (CMS) is not just about finding the product with the right functionality. It's also about dealing with a vendor who can support your needs for the lifetime of the solution. This briefing explores the way most CMS vendors have evolved, what this means for the way they work, and what you should be looking for when purchasing a solution.
Robertson, James. Step Two (2007). Articles>Content Management>Assessment
Dokumentenmanagement für den Mittelstand 
Dokumentenmanagement schien immer eine teuere, aufwendige Angelegenheit der Großunternehmen. Die Einführung einer Document-Related-Technologies-Lösung gleich welcher Ausprägung erfordert Anpassungen an Infrastruktur, Abläufe und Arbeitsorganisation. Dies wollten sich bislang viele Mittelständler nicht leisten. Ihr Credo lautete: "Durch so ein elektronisches Dokumentenmanagement-System bekomme ich doch keinen einzigen Kunden mehr". Diese Situation hat sich geändert. Auch der Mittelstand wird zunehmend in elektronische Geschäftsprozesse eingebunden. Die Abhängigkeit von Software in Verwaltung, Logistik, Kundenbetreuung und Produktentwicklung wird immer größer.
Kampffmeyer, Ulrich. Doculine (2002). (German) Articles>Content Management>SMEs
I've seen dozens of companies waste hundreds of thousands of dollars because they chose their management tools before they had a clear understanding of their business needs, information life cycle and content.
Rockley, Ann. Transform (2004). Articles>Content Management>Content Strategy
Drug Information Association: XML Resources for Life Sciences Pro
The Drug Information Association (DIA) has compiled a series of useful articles designed to help you understand XML and related technologies. Don't worry! You don't have to be an IT guru to understand XML. The resources provided are written in laymen's terms and geared towards life sciences professionals, but may prove beneficial to professionals in other industries and vertical markets.
Rockley, Ann. Rockley Group, The (2004). Articles>Content Management>Scientific Communication>Biomedical
Poor Database Design of Drupal Equals Low Performance
Drupal's database design is stupid! it sucks! it is crap! To things clearer I am talking about design errors. Yes, they do exist. Some say that design errors are the basic cause of bugs in a system. They are right. Rather than go through a bunch of queries or rather hundreds of queries, I will just say that the database design has no relational qualities that would optimize and speed up the system what so ever. This a glaring whole in the knowledge of the Development team so if you are a joiner and want to contribute to the project then think about helping them out with the database design first.
Drupal (2007). Articles>Content Management>Software>Drupal
Drupal Has Terrible Access Control
After a week of fighting with it I have come to the conclusion that Drupal access control modules are all inadequate and are based on some weak database design. Taxonomy access and node access are flawed from the start. This type of access control where the assets are assigning their own internal security is not scalable and suffers from very high database overhead.
Hiveminds (2005). Articles>Content Management>Software>Drupal
This presentation reviews the benefits, principles and history of DSDM (Dynamic Systems Development Method).
Tabaka, Jean. Rally Software Development (2006). Presentations>Project Management>Agile
The DuPont Experience: Strategic Planning for Information Design and Development Organizations 
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'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: Breuninger, Charles L. 1997. “The DuPont Experience: Strategic Planning for Information Design and Development Organizations.” Technical communication 44:394–400.
Breuninger, Charles L. ComTech Services (1997). Articles>Knowledge Management>Organizations>Case Studies
Dynamic Content Delivery using DITA 
This whitepaper defines a new publishing paradigm, which we will call dynamic content delivery. Dynamic delivery changes the rules, putting the reader in charge of what content is important and how it should be packaged. It transforms publishing to an audience of many to publishing to an audience of one.
Severson, Eric. Flatirons Solutions (2007). Articles>Content Management>XML>DITA
Until recently, technical communicators created static content--content that is created in a specific way for a specific purpose (e.g., user guides and help) and that remains the same until the technical communicator deliberately changes it. As single sourcing has made it possible to write information once and use it many times, technical communicators have begun to create static customized content, which is designed to meet the specific needs of the user, the materials to be developed (such as user guides, reference guides, and training), and the delivery media (paper or online). The content is customized for a particular requirement at a particular time but cannot be changed without being regenerated by the author. Now, the ability to create dynamic content will change the way technical communicators envision, create, and distribute information.
Rockley, Ann. STC Proceedings (2002). Design>Content Management>Single Sourcing>Web Design
Introduces dynamic content, a method of single sourcing that 'meets individual users' needs by assembling a series of information objects in response to the userís requests or requirements.' She walks readers through a mock project involving the creation and delivery of dynamic content.
Rockley, Ann. Intercom (2001). Articles>Content Management>Single Sourcing
The Dynamic Duo: Motivation and Recognition 
Offers several tips for motivating workers and recognizing their successes.
Laurent, J. Suzanna. Intercom (2003). Careers>Management
There are two main publishing models used by content management systems: dynamic and batch publishing, and each has its strengths and weaknesses.
Robertson, James. Step Two (2003). Articles>Content Management>Methods
Dynamic Websites: What Are They and Do You Need One?
If you're thinking about getting, or updating, a website, chances are that you'll run into a web designer who will try to sell you on the idea of a 'dynamic site.' Here's what you need to know in order to decide if such an approach is for you.
Bennaco (2004). Design>Web Design>Content Management
There are 17 readers currently online: 1 registered user and 16 guests. Register.

![]()
![]()


![]()
![]()
![]()