On 22 Nov 2008 00:43:08 -0500, Jim Henderson <nos### [at] nospamcom> wrote:

>On Fri, 21 Nov 2008 23:00:59 -0500, Jim Henderson wrote:
>
>> On Fri, 21 Nov 2008 20:48:12 +0000, Orchid XP v8 wrote:
>> 
>>> Jim Henderson wrote:
>>> 
>>>> "Troubleshooting" is a good general term for this, or "problem
>>>> diagnosis and resolution".
>>> 
>>> Troubleshooting is the term I'd go with.
>> 
>> It's a good one; "problem isolation" is another that I've seen.
>
>Another that gets attention is "root cause analysis".
>
Personally, I'd say fault finding ;)

Seriously, on this side of the Pond. The simpler the word or phrase the better.
I'd rather hire someone who could do a good job rather than talk a good job.

"Troubleshooting" is acceptable but it would be more applied to whole system
problems not individual equipment faults.

I think it's interesting that "fault finding" sounds like a "blame game" to
Darren. Here a phrase like "root cause analysis" would get the CV passed around
so everyone could have a good snigger. Again two countries separated by a common
language :)


-- 

Regards
     Stephen

Post a reply to this message