These books focus on effectively communicating policies and procedures:
- Writing Effective Policies and Procedures: A Step-By-Step Resource for Clear Communication, by Nancy Campbell, AMACOM (1998)
- Establishing a System of Policies and Procedures, by Stephen Page, Bookmasters (1998)
- 7 Steps to Better Written Policies and Procedures, by Stephen Page, Process Improvement Publishing (2001)
- How to Write Policies, Procedures & Task Outlines: Sending Clear Signals in Written Directions, by Larry Peabody, Idyll Arbor; 3rd edition (2001)
- Procedure Writing: Principles and Practices, by Douglas Wieringa, Christopher Moore, and Valerie Barnes; Battelle Pr; 2nd edition (August 1998)
- The New Playscript Procedure – Management Tool for Action, by Leslie H. Matthies, Office Publications, Stamford, CT (1977)
Compiled by Raymond Urgo.
Post a comment to add books.
Proceedings-1999; By Robert Krull; Summary by Maria Christophel (2006)
This article introduces a method for achieving balance between the people’s mental representation of actions and the display plane in which the action is represented. It explains the components of actions as procedures that brain must conform with, and provides detailed information on the performer and the spectator’s point of view as pictured on the display plane.
Proceedings-1996; Judy M. Gibbs; Summary by Maria Christophel (2006)
This article provides information on the implementation of writing techniques used in a technical field to improve the documentation of procedures of another. The author describes the scenario, narrates the status of the current procedures, and names the protocols needed to enhance the document. The article provides clear examples for enhancing the protocols, summarizes the positive results of implementing the recommended protocol enhancements, and provides a sample of the complete template.
Proceedings-2003; By Adrienne Escoe; Summary by Maria Christophel (2006)
This article provides guidelines for estimating the cost of developing policies and procedures for a company. It points some of the misconceptions of scope and responsibilities between the client and the technical writer that eventually surface with financial downturns. It recommends the use of a checklist and a detailed list of items that should be included in it. It guides through the main items of scoping the project, and enumerates the tasks that should be considered, time, level, etc. The author recommends the careful preparation of a list of assumptions and the consequences of the violation of such assumptions.
Intercom-June 2006; By Brenda Huettner; Summary by Maria Christophel (2006)
This article describes the twelve basic areas for managing a documentation project that must be included in the new set of standards dictated by ISO requirements. These areas include: roles and job descriptions, process, plan content, suite design, review and testing, configuration management, audience and task analysis, software and systems engineering life cycle, estimation, work br /eakdown structure, and quality metrics. The article cites several resources available for learning to manage documentation projects.
Proceedings-2000; By Raymond Urgo; Summary by Maria Christophel (2006)
This article discusses the five levels of concern that documentation developers should address when preparing the design of policies and procedures. Level 1: Defines P&P Architecture, and addresses the need to either use/recreate existing architecture or create a new. Level 1: Compares the united or disunited relationship between the P&P documents to be developed. Level 3: presents the extrinsic and the intrinsic approaches for development the content and the effects of combining them. Level 4: describes the Prose-based and the Structured methods for writing and the uses of both. Level 5: refers to individual units and collective units as techniques for communicating the information.
Intercom-November 2005; By Faye Newsham; Summary by Maria Christophel (2006)
This article explains in detail the reasons for increasing productivity and revenue by using Capability Maturity Model Integration (CMMI). It defines Maturity and its five levels of maturity. It indicates how companies can obtain CMMI certification. It elaborates on the benefits of building a Process Assets Libr /ary. It enumerates the various reasons why the implementation of CMMI in a company will need a technical writer. Finally, the article provides suggestions on how to get involved to get started working with CMMI.
Proceedings-2002; By Ann Rockley and Jodee Clore; Summary by Maria Christophel (2006)
This article defines Silo Trap™, Enterprise Content Management (ECM), and promotes the use of a unified content strategy for managing the volumes of information produced by the various areas of a company. It describes the problematic effects of content silos such as poor communication, lack of standardization and consistency, high costs, etc. It expands the definition of content management beyond Single Sourcing into ECM for which it provides description of benefits such as maintenance speed, cost reduction, and customer relation opportunities.
Proceedings-1998; By Raymond Urgo; Summary by Maria Christophel (2006)
This article defines the terminology and the scope of policies and procedures and introduces an Assessment Model for measuring the level of policies and procedures programs developed in a corporate structure. The model measures the grade in consideration to the functions provided by the program. It states that the model plays a synergistic role measuring the contribution of P&P to the organization.
Intercom-November 2005; By Raymond E. Urgo; Summary by Maria Christophel (2006)
This article discusses the various opportunities that await technical communicators in the world. It explains the reasons policies and procedures documentation is awakening interest in the business community. It provides a clear hierarchy of talents and skills required to achieve a career in policies and procedures documentation.