Traditional Procedures aren't Working
For ages, procedures have been written using a standard word processor (e.g. MS Word) and managed using some form of document management system (e.g. SharePoint or Documentum). Yet companies continue to struggle with operational performance and compliance.
Touch the colored areas of the charts below to see what industry personnel claim are the most challenging aspects of traditional procedures:
Writers Tell Us:
Workers Tell Us:
Managers Tell Us:
The Problem With MS Word
When managing procedures in the traditional word processor and document management environment, procedure writers can only deliver in one output (What you see is what you get).
Stuck in one format, and stuck in paper...
But workers are diverse, their tasks are diverse, so their procedures shouldn't be one-size-fits-all.
Top 8 Headaches
- Difficult to update multiple documents
- Limited use of media
- Can't deploy smartly to mobile devices
- Time wasted formatting documents
- Difficult to accurately find information
- Table of Contents crashing
- Inefficient to manage boilerplate content
- Difficult to manage reviews
Free the Data - Step Properties
The SmartProcedures editor tool is database driven, meaning that each procedure step is a unique entity in the system. This allows authors to associate more information to the step - enabling a world of procedure functionality not seen in traditional procedures. Some examples of step properties:
- Role (who performs this step)
- Type of step
- Equipment information
- Sign-off requirements
- Pictures and Media
- Competency assessment questions
- User defined properties
“SmartProcedures solves all of the problems - both known and unknown - with managing procedures. ”