Originally posted 06-May-21
Documentation includes user guides, manuals, and help files that allow users to read about what is expected of them, the people, processes, and tools available to them, and how to use all of these to share, innovate, reuse, collaborate, and learn.
Complete and effective documentation supports training, communications, and user assistance. It is a good way to demonstrate knowledge sharing and reuse, and allows users to learn about all elements of a KM program.
The types of documentation to provide include big picture documents, user’s guides, administrator’s guides, policies and procedures, and knowledge sharing documents. Here are details on each type.
1. Big Picture Documents: These are conceptual or overview documents. They help users understand the importance of knowledge management and their role in making it succeed. For those interested in a high-level view of knowledge management, why things work the way they do, and what resources are available.
Examples:
- Strategy and Vision: defines the Top 3 Objectives, the KM Strategy, and a vision for how things should work
- Program Governance: describes how the KM program is governed
- Roles: defines the roles of KM leaders, project leaders, and knowledge assistants
- Priorities: defines the KM team’s priorities for the year
- Expectations: states the importance of KM to the organization and specifies the responsibilities of all professionals and managers
- Getting Started: explains basic KM concepts, what resources are available, and how to learn more
- Initiatives Inventory: lists all KM initiatives in the organization with sponsoring organizations, responsible individuals, and links to web sites
- Overview: provides highlights of the KM program, details on all components, and screen shots of and links to all relevant web sites
- Architecture: explains the structure of the KM environment, the standard taxonomy, how content is contributed, and how it is searched for
- Insights: provides an overview of the topic of knowledge management, including definitions, models, process maps, checklists, and industry examples
2. User’s Guides: These are written to help users understand how to do something. Knowledge assistants can refer users to these when providing support.
Examples:
- FAQ (Frequently Asked Questions): answers to the most typical questions about finding content, sharing, asking questions, tools, external access, communities, collaboration, archiving, expectations, time reporting, contacts, documentation, rewards, training, and support
- How to Collaborate: describes the processes and technologies that are used to encourage employees to collaborate and participate in communities
- Communities: explains how to create, build, sustain, and participate in communities
- Face-to-face Knowledge Sharing: describes why this is important, different types, guidelines, examples, suggestions, and pitfalls to avoid
- People Guides: explains how to use a particular KM people component, e.g., knowledge help desk, measurements, or incentives
- Process Guides: explains how to use a particular KM process, e.g., capture, reuse, or lessons learned
- Tools Guides: explains how to use a particular KM tool, e.g., team space, repository, or threaded discussion
- How to Ask for Help: describes the key elements of a successful request for help for those posting a question to a threaded discussion or sending an email message seeking help to a large distribution list
- How to Record Time: explains how time spent on KM activities should be reported in the organization’s labor tracking system
- How to Track Accomplishments: describes how to track KM accomplishments in order to take credit for them during performance reviews
3. Administrator’s Guides: These are written to help administrators and knowledge managers understand how to do something.
Examples:
- Managing Disk Usage in Team Spaces: helps team space administrators be efficient in the use of disk storage
- Portal Administrator’s Guide: addresses the most common issues faced by portal administrators
- Threaded Discussion Moderator’s Guide: describes the role and duties of moderators
- Threaded Discussion Administrator’s Guide: details every aspect of the software used for threaded discussions
- Metadata Guide: defines the standard metadata used for documents stored in repositories
4. Policies and Procedures: Details on standard processes which are required of users. These may be part of an official document repository, in which case, they are linked to from the KM documentation web page.
Examples:
- Collaboration Policy: defines the policy for how teams are to collaborate
- Knowledge Capture and Reuse Policy: defines the policy for how knowledge is to be captured and reused
- Knowledge Capture and Reuse Procedure: details the steps to follow in support of the policy
- Records Management Policy: defines the policy for how the organization’s business records are to be managed
- Archiving Procedure: details the steps to follow in support of the records management policy’s archiving rules
5. Knowledge Sharing Documents: These are written to capture tacit knowledge and convert it into explicit knowledge.
Examples:
- White Papers: brief publications about trends, insights, and knowledge nuggets
- Methodologies and techniques: brief publications sharing tips, tricks, and how-to advice
- Case Studies: in-depth reviews of actual practices
- Seminars and Conferences: materials received at or presented at industry events, training courses, or symposia
- Customer-Ready Materials: presentations designed for external audiences
See also the extended version of this post.