We would like to thank those of you who participated in our initial round of testing Bizmanualz On-Line.

Bizmanualz OnPolicy is a software service in which quality professionals, departments heads and managers can review, approve and release controlled documentation as required by ISO and other compliance standards.

Recently Bizmanualz issued free trial and test instances of the Editor module. On Monday, August 16^th, Bizmanualz will release the Bizmanualz OnPolicy Reader module, a companion web site which automatically displays and organizes all documents released by the Editor module.

Starting Monday, log-in will occur through the Reader module. If you are currently testing the software, you will receive an email with your new link. Your old deep-link will still get you into the editor module. After Monday, we recommend that all users log in using the new link and discard their old link.

Within the reader module, editors will be required to click on an “editor module” button to get into the work flow features that they are currently using. JAVA will load as it has been doing when entering the editor module. The reader module on the other hand does not require JAVA.

Additional Release notes:

A. Only released documents appear in the reader module.
To release documents, click on the editor button in the reader module and use the work flow features.
Test software comes loaded with sample procedures and user help files. Only help files are “released” and therefore appear in the reader module. Any documents released through the Editor module will show up in their respective folders.

B. All readers and editors must have a user name and password.
To create or edit user name and password: Go to the Admin > User tab in the editor module. Enter all the required information.  Select reader and/or editor privileges when you add a user.
Current users will not have to reset their user names or passwords.
Right now as we test the software, editors will have to supply their user name and password a second time to move from the reader module to the editor module. Only one-log-in will be required of editors in the next release.

C. Single point of entry
By having editors log in through the reader module, we are providing a single point for all users to log-in. Sending editors through the reader module will give them easy access to the same view that all employees see, providing editors with an easy way to see what has been released and to see exactly what non-editor (readers) see. We will provide short-cuts to help editors move between the modules in the next release.

D. Your account will NOT lose data as a result of this transition.

E. Unlimited number of users
For now, we have removed the cap on the number of users you may create.
Go to Admin > Users and click the ‘add’ button in the editor module. Add as many users as you want.
When we begin charging for the software, a large but not unlimited number of authenticated readers will be able to log on, even at the introductory price point.

F. Two user-help documents are affected. The log-in instructions have been updated to reflect the new log-in procedure via the reader module. Also, a new use-case has been added that shows basic operation of the reader module.

New reader module home screen.

G. System will be unavailable Aug 14-15th. You may not be able to log in during the transition while we make the changes described above. Most of the changes will occur over the weekend (August 14-15). Help files will be updated in all existing instances on Monday August 16, 2010. All service will be restored by Tuesday.

H. Response time has improved. As mentioned in a previous release note, we moved the test server you are using to an off-site SAS 70 Type II compliant location. Response time has been greatly improved. Please let us know how fast the server is working for you.

Thank you again for your assistance and feedback as we move this product to market.

We will contact all existing users after the transition for a walk-through and to gather your impressions of the software and the new reader module. Free accounts are issued so that we can gain your input. We reserve the right to cancel your access if we cannot get your feedback.

Pleaes let us know if you have questions or additional comments.

sales@bizmanualz.com

I wonder how many of our clients, on receiving our policy-and-procedure manuals, have asked themselves what in heck they got themselves into. (“There’s a lot of stuff here…where do I begin?”) Well, like a lot of things, it’s probably not as difficult as it looks initially. First, you took a step in the right direction by using our templates to develop your company policies and procedures. It’s always easier to start with some of the work already done for you, rather than you having to start from scratch.

Now, how do you proceed?

Understand Why You Need Policies and Procedures

You don’t need policies and procedures merely to comply with regulations or industry standards (like ISO 9001). Sure, there’s nothing quite like the threat of fines, legal action, and the scorn of the business community to motivate you, but that’s far from the best reason. Much better reasons for developing policies and procedures include:

• Communicating your business goals and priorities;
• Standardizing processes, behavior, and results;
• Training your employees consistently; and
• Identifying acceptable and unacceptable behaviors (and encouraging or discouraging them).

Prioritize Your Needs and Set Goals and Timelines

Now that you understand “why”, you need to decide “what”.  Of the policies and procedures you could work on, you have to determine which one(s) are going to provide:

• The biggest bang for the buck;
• A quick return on your investment; and/or
• The greatest good for the greatest number.

Only you know what you need.  I can offer you suggestions (like “start with a fairly simple process”) but only you have the intimate, day-to-day knowledge of your organization. It’s your company: you decide.

So, decide which process you’re going to document first.  If you have absolutely no idea (you have no metrics and no historical basis for evaluation), try any Bizmanualz policy or procedure.  Document your initial design and development process and use it as a baseline for further development.

Give the first procedure a fair evaluation.  Don’t look at your first policy-and-procedure development, point out all the flaws you can find, declare the project an abject failure, and pull the plug.

Introduce discipline into the development process by setting clear and meaningful (aka, “SMART“) goals and timelines.

Analyze Your Existing Procedure

If you already have a de facto¹ procedure in place, don’t throw it out in favor of so-called best practices that may or may not work for your firm.

“If it ain’t broke, don’t fix it.” (Anon.)

Now is as good a time as any to document your process.  Diagram it quickly in any manner and medium with which you’re comfortable. Simple is best (“Don’t make a big production out of it!”, Mom used to say).  Next…

Compare Your Process with Bizmanualz Best Practices

Bizmanualz has already looked at many companies’ procedures, blended them together to describe “best practices”, and reasonably modeled these procedures on the Deming, or “Plan-Do-Check-Act”, cycle. You may find that your procedure already looks very much like the PDCA model:

• You develop a set of objectives and a plan (process) for realizing those objectives;
• You implement the plan and immediately start collecting process data (in-process, end-of-process, etc.);
• You routinely analyze the data, to see if the process is performing in line with expectations; and
• You make changes to the process (procedure) in order to improve it and improve your results.

If that’s the case, you don’t have far to go at all. Next…

Make Our Procedure Your Procedure

Make the obvious and necessary changes to the Bizmanualz policy and/or procedure.  We wrote them generally, like ISO standards, so they’d have the widest possible application.  Any resemblance between our procedure and your process is coincidental; that is, you’ll have to customize our procedures – make them your procedures.  For example:

• Change every instance of “Bizmanualz” or “the company” to your company;
• Where you have an existing form (e.g., purchase order, customer order, invoice), use it – and make sure field names, etc., on the form and in the procedure agree;
• Change job titles in the “Responsibilities” section and in the procedure itself to reflect your circumstances;
• Change diagrams² as needed;
• Add visual aids – they add impact and meaning and they complement verbal descriptions very well (especially when they come from your office, your shop floor, your staff, etc.); and
• Leave out what you don’t need.  An entire procedure or just part of one — if it doesn’t apply to your situation, delete it.  Make your policies and procedures simple and direct.

Verify and Validate the Procedure

The people responsible for implementing the procedure have to put it to the test.  Oh, you could write a procedure and thrust it on an unsuspecting workforce but until it’s subjected to “real world” conditions, the results you see may not be the ones you want or expect.

And there’s more to it than procedure verification and validation. Some people call it “getting buy-in”. Whatever you call it, recognize that your employees are stakeholders in the company. They have a vested interest in the company, too – if it does well, they do well. So, keep them in the loop on matters that directly affect them, to ensure their understanding and cooperation.

Even if they’re not directly impacted by the procedure in question, keep all employees informed of this — and most — company matters.

Implement the Procedure

Now, publish the tested-and-verified procedure.  Distribute the procedure to those responsible for executing it, analyzing it, and training employees.  NOTE: A document management system, or DMS, will help you address publication and distribution, as well as improve document control.

Hold a training session on the procedure – make sure trainees are not only capable of doing the work, but that they understand the process and the objectives, as well.  Finally, execute the process.  Collect the data from measuring devices and routinely analyze it.  Look for anomalies and trends in the data, evaluate the process, and aim for continual improvement.

Yes, ladies and gentlemen, it’s just that simple! Any questions?

NOTES

¹Just because you haven’t documented it doesn’t mean you don’t have an effective process in place.  Example: my wife and I came to a quick understanding some time ago that I would clean tubs, showers, and toilets and balance the checkbook. It’s very effective, plus there’s no point in documenting such processes because (a) they’re easy and (b) she won’t ever do them.

²We’ve been using Microsoft Visio to build diagrams. Unfortunately, Visio is not automatically included with any version of MS-Office, so far as we know. There are many alternatives to Visio, though – any search engine will help you find them – so your organization need not be constrained by a lack of Visio³.

³No, that’s not a typo.