Rands in Repose has an article called Taking Time to Think. It talks about thinking needs time and rooms. If you are busy, you won’t be able to think. When you are busy or you are resolving problems in the urgent environment, Rands classified this as reacting, not thinking. Rands gives some examples on software engineering project:
…I will respond and my response might look like thinking, but I’m not doing anything creative because I’ve dealt with the showstopper two days before ship scenario IN EVERY PRODUCT I’VE EVER BUILT. Survived it each time, too. Got some great stories. It’s that experience I’m using when you walk into my office and tell me the sky is falling. I’m not actually doing anything new, I’m just telling you the story of how I propped the sky up last time.
Yes, you can argue that one can be exquisitely creative when one’s hair is on fire. It’s the necessity is the mother of invention argument, but, seriously, if you’re hair’s on fire are you going to take the time seriously consider all hair dousing techniques or are you just going to stick your head in the nearest convenient bucket before it really hurts? Panic is the mother of the path of least resistance…
He suggests there should be a block of time scheduled out for thinking – preferably meetings on brainstorming and prototyping. There are some good tips to lead on creative thinking within the meeting. They are good advices.
Taking Time to Think – [Rands in Repose]
163 técnicas de creatividad y más.
En lifehack.org, he encontrado un artículo muy interesante, llamado Essential Resources for Creativity (163 techniques + 30 tips + books!).Y en efecto son 163 técnicas que junto a los tips y libros, no tiene desperdicio:Un adelanto a
Reacting is common in my workplace as we deal with “sky-falling-hair-on-fire” things on a regular basis. Reacting is not so bad especially if you have experience, but I feel that thinking is much better to avoid future episodes of falling sky.
Commonly what happens in software is something breaks right before it ships. Yes, yes, I know that seems outlandish, but most software engineers lack hair because it is oft on fire. Being engineers, we frequently say “ouch! that burns…let’s fix it” when we ought to be saying, “let’s fix is so it never lights our hair on fire ever again” and fixing it properly. It happens quite often in almost every product big or small that you use everyday.
Our team is trying new ways of “fire-proofing” our hair by trying to preempt such kerosene-esque episodes, but it rarely works out since we’re usually blindsided by something. At least we react to fix things quickly.
11 Fail Proof Habits for Producing a Floodgate of Energy
Feel less tired, more alive, and energized by adopting the following energy boosting strategies: