"slow" thinking requires checking your immediate gut reaction and taking a moment to think through the problem.
"fast" decision making requires taking a moment to think about how much time it is really worth to make a decision.
Arguably making "fast" decisions requires thinking "slow" about the length of time you should spend making the decision.
If you have the impulse to go fast, think about prototyping whatever it is you are trying to do, if you can. You should agree with yourself to dispose of the prototype completely. By the time you've gone through debugging the prototype you'll know much of what is needed to do the real thing.
Obviously, this doesn't always work. In those cases, whiteboards, pen and paper, even a text document can help.
Shouts out to A.E. for riding in that 6-0
Move fast, stick slow, think fast, talk slow
- Lil BSpeed is important. Patience is important. Stepping back and smelling the flowers is important. It's not about fast or slow. It's about right, and you can't be right all the time if you're stuck in the habit of zooming along all the time.
I remember how many _years_ it took Apple to figure out how to do right-click properly while their competitors were speeding along with that silly second button.
I'm sure it's great once you learn it and get used to it, but not exactly intuitive.
Speed as a habit seems like it would ruin the ability to slow-think. Is there a dichotomy here or can we do both?