And I thought to myself, "One file for EVERY idea. Separate ideas for separate contexts, too - for example, I'm one of those people who gets only limited time with his boss, so I had a whole list with the filename, I had a half-dozen lists, then a dozen, and eventually the whole thing got too hairy and I had to give it up.īut then I heard Merlin's talk at Macworld, and he mentioned, in passing, while making another point, an "ideas" file. So I started keeping separate files for separate projects. Then I said to myself, "I really ought to group similar ideas together, because they're likely to all end up in the same article or blog." For instance, I'm a Second Life enthusiast, and I'm working up a list-type blog post or article: "N Easy Things Second Life Can Do To Make Itself More Useful And Attractive" So I really ought to group all those ideas into a separate file. Back then, I went by gut feeling, now I think I have some good thumb rules - but either way, this decision should not be made at this stage of the process. The first difficulty I encountered was that it wasn't always clear, up front, what's going to turn out to be a blog, and what will be an article. I also had a file called "inbox" for random thoughts, most of which would get turned into GTD next actions. I am a journalist and a blogger, and so I started out with three files. I started keeping text files of ideas a year or two ago, but the system quickly collapsed due to its own complexity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |