Wondering if anyone else has implemented an if-then-else structure for their projects. This is the first time I've thought to do this, and while one could argue it's an unnecessary step, it helps me plan out my course of action for each possible outcome.
In the example below, while sitting in a lecture I was thinking about an episode of the StarTalk radio show, and wondered whether or not the show was available on iTunes. I didn't want to open iTunes and check at that moment, so I added the "research whether or not Startalk podcasts available from iTunes" item to my inbox. Normally I would leave it there and deal with the yes/no structure internally while I was completing the task, but decided to plan out both possible routes while I was thinking about them.
While this additional planning adds a little time to the process phase, I think I like the way it lets me think a project all the way through before I tackle it.
Click for full size - Uploaded with plasq's Skitch
In the example below, while sitting in a lecture I was thinking about an episode of the StarTalk radio show, and wondered whether or not the show was available on iTunes. I didn't want to open iTunes and check at that moment, so I added the "research whether or not Startalk podcasts available from iTunes" item to my inbox. Normally I would leave it there and deal with the yes/no structure internally while I was completing the task, but decided to plan out both possible routes while I was thinking about them.
While this additional planning adds a little time to the process phase, I think I like the way it lets me think a project all the way through before I tackle it.
Click for full size - Uploaded with plasq's Skitch