O
Re: New Service Company - 20 People - Wants ISO 9001 !
CoKo,
ISO 9004 is indeed a great place to start.
I think pursuing compliance is worthwhile for a start up even if you do not go for certification.
One of my clients is a start-up that began with 5 people when I started talking to them and now they are at 150 employees in two years. They would have suffered even more growing pains than they did if they didn't have good process based documentation and a decent training program.
They actually had a very large customer who headed them towards registration in their early days. The company, BP, wanted some assurance that though they were small they had a mature system they could relate to and ISO 9001:2000 fit the bill. They too are a service organization.
Just a couple of bits of advice.
1.) Document your processes and develop your documentation with the resources and facilities you actually have in place. I have seen small companies make the rookie mistake of thinking they need to write documentation as if they had a 50,000 sq foot office and 200 employees.
Write what you actually do and change what you do based on a gap with the standard or as a thought out correction because it isn't giving you the results you want.
2.) Don't get hung up on reengineering the process. A great American philosopher Yogi Berra said "If you don't know where your going any road will take you there." strive for process consistency first. If you can get everyone doing things roughly the same way over and over and even if it is a lousy process it will pop right out at you and you will have the empirical data to make the right changes.
3.) Don't over-write. Less is more. Think of each document as a tool. If it does not have a purpose or use don't do it. The standard doesn't ask you for anything that isn't potentially useful in most businesses. If you write a bunch of stuff just to impress the auditor you are just setting yourself up for misery. Someone else gave you good advice.
This should be enough to get you started. The people here are a great resource and enormously helpful.
Good luck to you. Keep us posted, no pun intended.
CoKo,
ISO 9004 is indeed a great place to start.
I think pursuing compliance is worthwhile for a start up even if you do not go for certification.
One of my clients is a start-up that began with 5 people when I started talking to them and now they are at 150 employees in two years. They would have suffered even more growing pains than they did if they didn't have good process based documentation and a decent training program.
They actually had a very large customer who headed them towards registration in their early days. The company, BP, wanted some assurance that though they were small they had a mature system they could relate to and ISO 9001:2000 fit the bill. They too are a service organization.
Just a couple of bits of advice.
1.) Document your processes and develop your documentation with the resources and facilities you actually have in place. I have seen small companies make the rookie mistake of thinking they need to write documentation as if they had a 50,000 sq foot office and 200 employees.
Write what you actually do and change what you do based on a gap with the standard or as a thought out correction because it isn't giving you the results you want.
2.) Don't get hung up on reengineering the process. A great American philosopher Yogi Berra said "If you don't know where your going any road will take you there." strive for process consistency first. If you can get everyone doing things roughly the same way over and over and even if it is a lousy process it will pop right out at you and you will have the empirical data to make the right changes.
3.) Don't over-write. Less is more. Think of each document as a tool. If it does not have a purpose or use don't do it. The standard doesn't ask you for anything that isn't potentially useful in most businesses. If you write a bunch of stuff just to impress the auditor you are just setting yourself up for misery. Someone else gave you good advice.
- Identify your core business processes. I am a flowchart fan but at least diagram them out in some fashion. Identify where they touch each other. That is where most processes fall apart when the handoff to another process occurs.
- Match them up with resources they will require by responsibility
- What documentation do you need to support the process? If all roads lead to Rome just describe Rome. If you want them to take a particular road then create more detail.
- Train people using the documentation and then set up a couple of measures to track for results. That will lead you to developing some internal CAR process actions.
Good luck to you. Keep us posted, no pun intended.
Good Luck with your choice
:

