|
 |
On Sat, 22 Nov 2008 08:32:56 +0000, Stephen wrote:
> On 22 Nov 2008 00:43:08 -0500, Jim Henderson <nos### [at] nospam com> 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.
See, over here, we troubleshoot everything from system-wide faults to
individual hardware component failures.
> 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 :)
Ain't that the truth. :-)
"Fault finding" to me does imply "blamestorming" as well - the result of
"fault finding" is that "it's your fault", so has a very negative
connotation in most parts of the US IME.
Jim
Post a reply to this message
|
|
