Content-Transfer-Encoding: |
7bit |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Fri, 7 Jan 2000 09:45:23 -0500 |
Content-Type: |
text/plain; charset="iso-8859-1" |
MIME-Version: |
1.0 |
Reply-To: |
|
Parts/Attachments: |
|
|
I agree with Bryan, the why's far outway the what's.
Wassat?
Leland
----- Original Message -----
From: J. Bryan Blundell <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, January 07, 2000 8:42 AM
Subject: Re: Poor Application of Product at Biltmore Estate
> Ralph:
>
> The problem is, being able to properly link cause and effect. Knowing what
the
> product is, that did not work, may be misleading. Knowing why it did not
work is
> important. Often my company gets called in to correct a what with another
what
> that has been spec'ed and no one has tried to determine why. The why is
why there
> was failure not the what.
>
> Bryan
> -------------
>
> Ralph Walter wrote:
>
> > In a message dated 1/6/2000 2:37:14 PM Eastern Standard Time,
[log in to unmask]
> > writes:
> >
> > << It does not pay well to go out of our way to make enemies in a short
life.
> > >>
> >
> > Ken,
> >
> > I wasn't looking to make enemies, got enough already, including some of
our
> > mutual acquaintances, but don'cha think it would be good to know what
this
> > stuff was that didn't work?
> >
> > Ralph
>
|
|
|