03 Why document procedures?

In many organizations, procedures are known only to the people who use them and are never documented, or are only casually documented.

Managers and peers may be aware of some or all of these procedures, but without a single reference point, no one can really know for sure.

Documenting procedures:
  • Centralizes procedure-related information in a single location and format
  • Captures and preserves information that might otherwise be lost as users change position within your organization or leave
  • May be legally or contractually required (for union agreements, audits, offsite backup, etc.)
  • Allows you to test validity of current procedures and recognize:
    - Better or more efficient ways of doing these procedures
    - Obsolete or out-of-date procedures
    - Gaps in current procedural documentation
  • Helps ensure standardized performance of procedures and reduce procedural errors
  • Provides a checklist for users when they perform unfamiliar activities
  • Creates workarounds for systems that don't work, or no longer work the way they used to (e.g. 'send weekly timesheets to the fourth floor HP printer', or 'submit vacation requests to your supervisor by email, not on paper')
  • Helps users identify and successfully complete new or revised procedures
  • Potentially reduces supervisor intervention for simpler procedural issues if users are encouraged to first review procedural documentation before requesting help
  • May reduce training and retraining time
  • Becomes a starting point or supplement for other documents such as training and reference tools or troubleshooting instructions
DOCUMENTING PROCEDURES: 03 Why document procedures?

No comments:

Post a Comment