The Two Fundamentals of Engineering

tirsdag den 18. februar 2020 kl. 18.26.22 UTC+1 skrev Tom Gardner:
On 18/02/20 15:54, jlarkin@highlandsniptechnology.com wrote:
On Tue, 18 Feb 2020 00:17:40 -0500, "Tom Del Rosso"
fizzbintuesday@that-google-mail-domain.com> wrote:

jlarkin@highlandsniptechnology.com wrote:
Stop

Think

Define the problem.



Presumably that was done at the start of a project, but it is often
done wrong. Especially when designing a new standard product. So an
occasional stop/think break could change the project direction.

Group-think and management discourage such re-assessments.

I've often seen clients say they want X developed to
solve their problem Y.

After talking to them it becomes apparent that Y is
merely a symptom of the underlying problem and that X
isn't the best way of solving their underlying problem.
In bad cases, X won't even solve the underlying problem.

The clients you don't want are those are wedded to
X for reasons that they can't adequately explain.

https://en.wikipedia.org/wiki/XY_problem
 
On Tuesday, February 18, 2020 at 10:20:10 AM UTC-5, dagmarg...@yahoo.com wrote:
On Tuesday, February 18, 2020 at 10:10:25 AM UTC-5, George Herold wrote:
On Tuesday, February 18, 2020 at 9:39:06 AM UTC-5, dagmarg...@yahoo.com wrote:
On Tuesday, February 18, 2020 at 12:17:46 AM UTC-5, Tom Del Rosso wrote:
jlarkin@highlandsniptechnology.com wrote:
Stop

Think

Define the problem.

Any problem comprises two smaller problems.
Ah a reductionist huh? :^)

George H.

Everything is either simple, or impossible.
Chuckle....
I agree. (though sometimes things will switch categories...
"huh, and I thought that was simple." he said.)
GH
Cheers,
James Arthur
 
On Tuesday, February 18, 2020 at 10:54:19 AM UTC-5, jla...@highlandsniptechnology.com wrote:
On Tue, 18 Feb 2020 00:17:40 -0500, "Tom Del Rosso"
fizzbintuesday@that-google-mail-domain.com> wrote:

jlarkin@highlandsniptechnology.com wrote:
Stop

Think

Define the problem.



Presumably that was done at the start of a project, but it is often
done wrong. Especially when designing a new standard product. So an
occasional stop/think break could change the project direction.

Group-think and management discourage such re-assessments.
Reassessments might be as hard (or harder) if there is just one
person involved. The optimal number of people for one project
is probably greater than one. (not to say some geek working alone
in their basement can't get a lot done.)

George H.
--

John Larkin Highland Technology, Inc

The cork popped merrily, and Lord Peter rose to his feet.
"Bunter", he said, "I give you a toast. The triumph of Instinct over Reason"
 
On 2/15/20 7:09 PM, Clive Arthur wrote:
On 15/02/2020 02:35, jlarkin@highlandsniptechnology.com wrote:


Stop

Think


Measure twice, cut once.

As my father often said: I have cut it now two times and it is still too
short.

--
Reinhardt
 
Reinhardt Behm <rbehm@hushmail.com> wrote in
news:r37at5$sbk$1@dont-email.me:

On 2/15/20 7:09 PM, Clive Arthur wrote:
On 15/02/2020 02:35, jlarkin@highlandsniptechnology.com wrote:


Stop

Think


Measure twice, cut once.


As my father often said: I have cut it now two times and it is
still too short.

Time to get the stretcher out.
 

Welcome to EDABoard.com

Sponsor

Back
Top