-
Warning: I haven't yet been entirely successful with this idea. I'm presenting it for the crowd to consider, suggest improvements, or explain why it shouldn't work.
The idea is to examine tasks you feel you should do but aren't. Maybe it's about to be dismissed. Seems to me there are three cases.
1. It's part of something bigger but this part isn't ready yet. Solution: Scale it Up to the bigger task and start figuring how to work on that.
2. It's too big and you aren't grabbed because of its size. Solution: Scale it Down. Pick a part of the task that you are ready to do.
3. You really don't need this. Throw it Out.
26 October 2010 at 14:44 | Alan Baljeu
-
4. It's not your own goal, but someone else's goal. Are you aware that it's not your goal? Do you want to support it? Solution: Be loyal or 'sharpen your sword'.
26 October 2010 at 15:10 | Rainer
-
That particular one never comes up for me. Anyway, I'm hoping to focus more on the idea of solving a stuck task by either going up to a higher or down to a lower level statement of the task at hand.
Another possibility is to go Forward. If you aren't ready for N, think if there's a K that precedes it and rewrite the N into K.
26 October 2010 at 20:38 | Alan Baljeu
-
@Alan
I think you are on to something.
We all know the fact that some things don't move because they are not well defined. Most of the time, I try to define it more granularly. But you raised the interesting point that when it's not something you can move on now, then going up might help!
I will definitely be trying this!!!
26 October 2010 at 23:50 | Erik
-
I think this is also a very valuable way to think about task. I frequently reduce down, but the idea of scaling up and connecting to a bigger goal seems very valuable as well. Thanks for posting this.
29 October 2010 at 15:48 | Gerry