Interesting Discussion Using a Wiki to implement a Quality Management System (QMS)

Pancho

wikineer
Super Moderator
I suggest you decide whether you want (or need) to keep your data in Excel or make the leap to reproduce the records in wiki format.

The wiki format is simple, which at first makes you feel like you're taking a step backwards, but if you successfully convert your data it is more accessible (from any web browser, even a mobile device) anywhere, without the need for MS Office, and because of its simplicity is not intimidating to new users.

That's excellent advice.

Also, a published file that is not immediately visible (wiki or not) promotes the distribution of uncontrolled copies because every time a user downloads the file to read it he or she is creating another such copy. Not good. :nope:

Hari, you should always try to make wiki content immediately visible.

Pancho
 
Elsmar Forum Sponsor
H

harishankarpv

hi Pancho n Le chiffre...i am impressed with the guidance that you have provided..right now i am preparing a business case on this....and your information is great for my case

:thanks:
 

Stijloor

Leader
Super Moderator
hi Pancho n Le chiffre...i am impressed with the guidance that you have provided..right now i am preparing a business case on this....and your information is great for my case

:thanks:

Will you be able to share it with other Participants here at The Cove Forums?

Stijloor.
 
H

harishankarpv

Sure...the case is bulding up..once done ..i will be happy to share with you guys.

Hari
 

jkuil

Quite Involved in Discussions
Great concept. I am also looking at new web 2.0 tools to use for qualitymanagement. Wiki was the most obvious.

I have a few questions:
  • In your example it shows that the wiki page is growing fast is the amount of text. How do you assure that the QMS remains focussed on the critical to quality elements and is not used as a library?
  • Is there a link to registration of training when training is required?
  • In your experience, is the QMS consistent, do writer assure their pages are consistent with other wiki elements?
  • Has the wiki contributed to the social network within your company?

Thanks,
 

Pancho

wikineer
Super Moderator
Hi, Jan,

Great questions. Here are my comments on each.

In your example it shows that the wiki page is growing fast is the amount of text. How do you assure that the QMS remains focussed on the critical to quality elements and is not used as a library?

Several points on this:

  1. Our wiki-based management system has grown to encompass more than ISO 9001. OH&S, Financial and General Management systems are being implemented.
  2. The optimal amount of documentation in a management system is very much dependent on its accessibility. A wiki provides great accessibility. We use indexes on every page (see Sample QMS Wiki Organization) and encourage contributors to use plenty of contextual links in the docs themselves.
  3. We try stick to the DRY (Don't Repeat Yourself) principle. Links and "includes" allow this. See Using a Wiki for Document Control.
  4. Documentation in wiki grew very fast during initial implementation. It continues to grow, but at a more moderate pace.
  5. Issue tracking software is a now-indispensable companion to our wiki. We use Bugzilla. If redundant or otherwise undesirable documents appear, they are eventually flagged and then merged with others, or corrected or deleted.

Is there a link to registration of training when training is required?

Yes. We keep many of our records right on the wiki, including this.

In your experience, is the QMS consistent, do writer assure their pages are consistent with other wiki elements?

Mostly yes. Our procedure to create and edit documents requires contributors to DRY and Bugzilla helps in catching inadvertent violations. We've found the system to be self-correcting.

Our group is relatively small (about 40), and that may help, but I believe the system can scale up.


Has the wiki contributed to the social network within your company?

Haven't really thought much about this one, but the wiki certainly increased tremendously network connectivity and made it asynchronous.

We haven't measured, but I believe internal email use has decreased. Firefighting has definitely decreased (as you'd expect with any QMS). Contributors to the wiki acquire "network status" as their contributions are visible to all.

We also have separate wiki spaces for uses outside the Management System, and all of them help in strengthening our internal "social network". One of them is a General wiki space, where, among other things, Geometrica employees keep a page on themselves and where we post news and links of general interest. Other applications where we use wiki spaces include Technical Notes, Project Management and Client interaction.


----


Hope the above is useful.

BTW I noticed that the link in the original post is redirecting to the wrong page, and I can't edit it here. Could a kind Cove moderator please change the link in the first comment of this thread to https://articles.geometrica.com/64.html ?

Cheers,
Pancho
 
Top Bottom