M
Re: Quality implementation
edit: oh even better ^^^^^^^^^
Hi.
I am not an expert, I am not sure if your company already has, is ready to implement, or need ISO. I am guessing that they do not.
My suggestion is to start by talking with the different departments informally about some of the biggest problems they feel they have. Try to make some friends and get some "Buy In".
Then you will want to design a system for capturing simple mistakes, errors, rework, customer complaints/returned product, ect... This can be a simple form that they fill out and turn into you. I am not sure of your company's size, or computer infrastructure. An electronic data collection system can be very powerful, but this does not mean that a paper system has no use. With a good paper system you could collect, compile, and analyze a great deal of useful information yourself on your own computer.
Find the biggest problems, back them up with data (Component A from vendor D has failed X times in the past year). Focus on your biggest problems and do some "Root Cause Analysis." Figure out how much its costing and what it will save the company to prevent the problems. You can also empower others to have a hand in fixing the problems instead of just complaining about them.
I am sure that if you can tackle one problem with the system it will help get support from your associates, and you will be able to expand your programs to encompass more products / departments and justify a electronic data sytem.
edit: oh even better ^^^^^^^^^
Hi.
I am not an expert, I am not sure if your company already has, is ready to implement, or need ISO. I am guessing that they do not.
My suggestion is to start by talking with the different departments informally about some of the biggest problems they feel they have. Try to make some friends and get some "Buy In".
Then you will want to design a system for capturing simple mistakes, errors, rework, customer complaints/returned product, ect... This can be a simple form that they fill out and turn into you. I am not sure of your company's size, or computer infrastructure. An electronic data collection system can be very powerful, but this does not mean that a paper system has no use. With a good paper system you could collect, compile, and analyze a great deal of useful information yourself on your own computer.
Find the biggest problems, back them up with data (Component A from vendor D has failed X times in the past year). Focus on your biggest problems and do some "Root Cause Analysis." Figure out how much its costing and what it will save the company to prevent the problems. You can also empower others to have a hand in fixing the problems instead of just complaining about them.
I am sure that if you can tackle one problem with the system it will help get support from your associates, and you will be able to expand your programs to encompass more products / departments and justify a electronic data sytem.
Last edited by a moderator: