Subscribe to my Twitter feed

Tags

Page 5 of 512345

Only ask how if you know why


To solve your problem you’ll have to ask “why” or “how”. Which one should you?

Formulate your problem with a “how” only if you already know its root cause(s)

Formulating your problem with a “how” is attractive because it forces you, right from the start, to think about potential solutions: you are dedicating yourself to finding the various ways in which you can solve it. Soon, you’ll decide which one is the best, implement it, and give yourself a pat on the back.
The problem is that much of your effort can be misplaced thinking “how” if you don’t know the root cause of your problem.


Related Posts:

Practice and enlist others


It’s like tennis, you can’t become a good problem-solver just by reading about it. You have to practice it. And just like tennis, you’ll become much better if you practice with others rather than by yourself.

That’s why my graduate-level problem-solving course is not exactly a course. Rather, it’s a practical workshop. Each of the 20 students brings one problem— professional or personal—that causes them significant stress and we all work on it. So let’s talk about what works well there.

Related Posts:

Build logic trees: diagnosis trees and decision trees



 

Logic trees (also called issue trees) are at the heart of analytical problem-solving and, therefore, are a recurrent theme on this site. We’ll use two types of trees: diagnosis trees and decision trees.

A logic trees is a graphical breakdown of your key question. Trees have four basic rules:

  • They consistently answer to “why” or “how” (depending on your key question)
  • They progress from the key question to the analysis as they move to the right

Related Posts:

Page 5 of 512345