TexasCHLforum.com

Just another way to have people document thier jobs so they can be handed to somebody with half the real knowelege at half the pay.

suthdj wrote:Just another way to have people document their jobs so they can be handed to somebody with half the real knowledge at half the pay.

You show a great deal of wisdom, sir.

suthdj wrote:Just another way to have people document thier jobs so they can be handed to somebody with half the real knowelege at half the pay.

You are one cynical son of a gun.


Notice I didn't disagree with you. Welcome to the club.

It really bugs me when people use the term root cause. Rarely if ever will you find a root cause, it's usually several causes that are all contributing factors to system failures. I much prefer the causal tree process

Sorry, I'll get off my engineering geek soap box now

txcharvel wrote:It really bugs me when people use the term root cause. Rarely if ever will you find a root cause, it's usually several causes that are all contributing factors to system failures. I much prefer the causal tree process

Sorry, I'll get off my engineering geek soap box now

That is also part of the training module.

txcharvel wrote:It really bugs me when people use the term root cause. Rarely if ever will you find a root cause, it's usually several causes that are all contributing factors to system failures. I much prefer the causal tree process

Sorry, I'll get off my engineering geek soap box now

I prefer not having and overly complex methodology when all you have to do is ask why and have the skills to answer that question until there's no longer the need to ask why. That a nutshell its root cause analysis.

suthdj wrote:

txcharvel wrote:It really bugs me when people use the term root cause. Rarely if ever will you find a root cause, it's usually several causes that are all contributing factors to system failures. I much prefer the causal tree process

Sorry, I'll get off my engineering geek soap box now

I prefer not having and overly complex methodology when all you have to do is ask why and have the skills to answer that question until there's no longer the need to ask why. That a nutshell its root cause analysis.

I agree, but most people still have to be taught the basic skills on what questions to ask, how to ask them and how to answer them.

Wow, that reference from ISO9000 brought back some real nightmarish memories One of the reasons "root cause analysis" has such poor results in many companies is they simply don't fully grasp the real simplicity of ISO, and create a big, heavy, cumbersome system that works for no one. I'm so glad I'm retired

ISO9000 and Kaizen meetings - two of my most reoccurring nightmares.

mojo84 wrote:

suthdj wrote:Just another way to have people document thier jobs so they can be handed to somebody with half the real knowelege at half the pay.

You are one cynical son of a gun.


Notice I didn't disagree with you. Welcome to the club.

Yes, yes, thanks I think

jmra wrote:
ISO9000 and Kaizen meetings - two of my most reoccurring nightmares.

We got kaizen also do you work for a Japanese company also?

while i was still working found most of the root causes of problems was the operator screwed up

suthdj wrote:

jmra wrote:
ISO9000 and Kaizen meetings - two of my most reoccurring nightmares.

We got kaizen also do you work for a Japanese company also?

No. I worked for an international communications company that adopted the kaizen philosophy - I left 11 years ago to spend more time with my family.