To Think About . . .

Nothing is foolproof because fools are ingenious. Anon

 

 

 

My Latest Book

Product Details

Also available on Amazon.com, Amazon.fr, and other Amazons and bookshops worldwide! 

Search This Site
Log-in
Latest Comments
My Other Books

Product Details

Product Details

Product Details

The Pathway to Awesomeness

Click to order other recommended books.

Find Us on Facebook Badge

FV and FVP Forum > Someday, maybe list

Suppose the root item is something which you do not foresee to do in the next say 6 months. Do you propose to add it to a someday/maybe list or re-enter it at the bottom of list.

The problem with re-entering is that you will have task that is not currently relevant cluttering your system.

Any thoughts about this?
March 14, 2012 at 15:28 | Unregistered CommenterNico
This is indeed an aspect that (for me) was taken care of by the dismissal process of AF/SF. I'm trying to understand/imagine how this works out in FV.

In fact, I've not yet switched to FV because the very first root item in my list is exactly such a beast: an item I don't want to address right now and that under AF will probably soon be dismissed, to be picked up at the appropriate time via a "review dismissed items" action.
March 14, 2012 at 15:48 | Unregistered CommenterMarc (from Brussels)
Marc: I have made the switch, but after two days of testing I have found that the system does have somedrawbacks for me vs SF. I liked the idea of SF that you can easily see what is urgent now on the right hand column as well as the dismissal process. Thinking of switching back.
March 14, 2012 at 16:00 | Unregistered CommenterNico
Yes, you need a place to keep future stuff off-list. I prefer to categorize them and keep those categories on-list so I review them regularly.

Nico: I would think you'd be intimately familiar with urgent items if you stick to doing them. With SF you are obliged, but with FV you are equally able to keep doing them. They are at the end of the list, you will visit them every round, and you can do them first each round. If that's not enough, you can always mark them to stand out.
March 14, 2012 at 16:10 | Registered CommenterAlan Baljeu
I would put items for things months out, like "decide on summer vacation" in my tickler file for that later time. Or you could have a "Someday Maybe" list or file and a recurring item on your FV list to "check Someday/Maybe list" every once in a while.
March 14, 2012 at 16:34 | Unregistered CommenterJim Randolph
If they'll be due around the time the "start of list" reaches that page, you can write them on the current last page, and they'll sit there happily. You'll never want to do them before the current benchmark -- until it's time to start them. However, if you have too many of them, you'll spend a lot of time reading, comparing and rejecting the same items over and over. I'm using a week as the cutoff for now. I'll refine it as I use the system to see what works for me.
March 14, 2012 at 19:12 | Unregistered CommenterCricket
You could keep everything (active & inactive) in one list, highlight someday/maybe items and ignore them during regular passes through your list.

Pre-FV I started adding tickler dates for future items in the left margin. These are ignored until the date comes. At that point, I re-enter at end of list. I do something similar for someday/maybe's (? In margin). It keeps EVERYTHING on one list without interfering with the AF/SF/FV mechanics.

It's easy to see when any item has been completed, tickled or dotted. Future/someday items are easily ignored while current items stand out.
March 14, 2012 at 19:18 | Unregistered CommenterScotthutchins
I think any sort of external reminder would deal well with this issue, just as per the advice in the AF incarnations
March 14, 2012 at 19:32 | Unregistered CommenterLeon
Perhaps in FV/AF systems "someday/maybe" is a project called "dreams" or "future"
March 14, 2012 at 20:04 | Unregistered Commentermichael
<<I would put items for things months out, like "decide on summer vacation" in my tickler file for that later time. Or you could have a "Someday Maybe" list or file and a recurring item on your FV list to "check Someday/Maybe list" every once in a while. >>

Indeed, I think the following could fit into the rules: if the first item is something I don't want to start now, then I still take some action on it. This action consists of adding it to my someday/maybe list. Then I cross it off. And I'd have a recurring action in the list: "check someday/maybe list", which would allow to reactivate the item in due time. This could be seen as a dismissal on item level.
March 14, 2012 at 22:42 | Unregistered CommenterMarc (from Brussels)
These approaches may work fine, but you could also just follow the rules as written, without involving any other lists:

Enter such items on the list like anything else.

At some point, one of those items may percolate to the top of the list -- the very first item.

As the rules indicate, if you CAN'T take any action right now on that item, then cross it off and add it to the end of the list.

But if you CAN take action, but just don't WANT to yet, that's different. If the item is "no longer relevant" you can just delete it. But it sounds like these are items that we probably do WANT to do, at least sometime. FV is forcing us to ask ourselves, "Why not start now?" "What could I do NOW to work towards completing this?"

Perhaps it's enough just to give the item a few minutes of thought -- "Do I really want to do this? Should I offload this item into the tickler for a few months?"

Or maybe we can take five minutes to actually move the task forward.

There are many reasons why I find this approach very appealing:

It keeps these items on the main list, so they are frequently seen and filtered.

Items that I REALLY want to do, will actually see some action, early and often, which means I might actually accomplish the thing sometime. If I bury it on a someday/maybe, where I rarely even see the item, it doesn't get any visibility or filtering.

By keeping the item always in my mind's eye, it allows my subconscious to process the item.

It forces me to stay real, and not offload things to the imaginary future where I have infinite time to do everything I want.

It keeps the system simple and straightforward.

This is the approach I am trying right now, and will try to follow for the first couple weeks at least.
March 15, 2012 at 5:21 | Unregistered CommenterSeraphim
Good answer, Seraphim. I've found folliowing this principle has got me moving on some things which have been hanging around for ages.
March 15, 2012 at 7:36 | Registered CommenterMark Forster
<<As the rules indicate, if you CAN'T take any action right now on that item, then cross it off and add it to the end of the list.>>

I reconsidered what I wrote in the light of this. My original interpretation of this rule was that it applies when I can't do something because of wrong location, missing input, unavailability of contributors etc.

In my case, I don't want to do the first item because I'm required to spend most of my time on other priorities and don't have any time to spare for this (for now). But thinking again, this could also be seen as a valid reason why I "can't" do it.

Is this an acceptable/intended interpretation of this rule?
March 15, 2012 at 8:44 | Unregistered CommenterMarc (from Brussels)
Marc,

From Seraphim's response, I would say that if you have other, more urgent, priorities, the "pure" way to play this would be to select the task and, when you get to it, simply move it to a tickler to remind you when you have more time.

That's how I'm playing these, and it seems to work well.
March 15, 2012 at 9:17 | Unregistered Commenterwill
Marc:

I have to admit that I've sometimes moved the first item to the end of the list in similar circumstances to those you describe. I think the key is that the system is there to help you get your work done, not to get in the way. So the question is whether doing this helps you do the work that needs to be done, or is just feeding your procrastination.
March 15, 2012 at 10:42 | Registered CommenterMark Forster
Seraphim: What is the difference between a tickler file and a someday/maybe list? For me a tickler file/list is the same as a someday/maybe list except that it has a specific date/time when you need to review this?
March 15, 2012 at 12:47 | Unregistered CommenterNico
To a certain extent you are right Nico.

Someday / Maybe: here you do record just thoughts and ideas that you might do in the (near) future, whenever you are in the mood or ready for them, if they do make sense. Even if you did attach a date of action to it - which I would not suggest to do. Otherwise you are putting yourself even more under pressure ;)

Tickler: is more hard facts, things that you have scheduled to do and at the end of the day you can not avoid.
March 15, 2012 at 14:47 | Unregistered CommenterStefano F. Rausch
+JMJ+

Actually in my opinion "Someday/Maybe" items are very simple to manage, and this is an advantage I found of FV over all the other systems of Mark Forster:

1. Cross out the item you want to dismiss but add something to distinguish it from a deleted item. In my practice I place a "D" at the end.

2. Add "Review dismissed" item in FV list.

Now what have I done? I made sure that the "Someday/Maybe" items in my FV list are almost invisible to me during my usual use of FV, since they superficially look like deleted items. However, I am now forced to regularly review my "Someday/Maybe" (dismissed) items imbedded in the list because the item "Review dismissed" will, without fail, be included, sooner or later, in the FV algorithm.

Neat, eh?
March 15, 2012 at 15:48 | Registered Commenternuntym
I don't use a tickler for hard dates when things have to be done. That's my calendar.

A tickler is a reminder to start something. It can include a note of the deadline, but it isn't the deadline.

Having said that, I combine tickler and calendar on the same page. I look ahead on the calendar often enough that I see "Birthday" in time to put it on my task list and start getting a present. That process is routine. Reminders that don't need much preparation are included with the event. ("Bring scissors.")

However, some tasks aren't as routine. For them, I'll pick an early date and write "Plan 50th birthday party" well in advance of the party.
March 15, 2012 at 15:54 | Registered CommenterCricket
Nico wrote:

<< Seraphim: What is the difference between a tickler file and a someday/maybe list? For me a tickler file/list is the same as a someday/maybe list except that it has a specific date/time when you need to review this? >>

I don't use someday/maybe lists because I have found I never look at them later.

For me, a tickler is for holding things I don't want to see until the right time arrives. Maybe it's because I can't start that item till the right time arrives. Maybe it's a once-per-month recurring item. Etc.

The way I use a tickler is very simple. It's easiest to explain with an example. I have a "Monday" list with all the things I don't want to see until Monday. When Monday does arrive, I move all those items to the end of my FV list. (Or, in the past, to the end of my AF list.) They are then processed like any other item on the FV list.

I have a list like that for every day of the week, and every week of the year.

When the time arrives, I just move all those items to the end of the FV list.
March 15, 2012 at 18:20 | Registered CommenterSeraphim
After I have been following my own tweak of AF (PING-PONG-Af, described elsewhere in the forum), I hesitated to switch to FV. But I did today, and right the first item on my list was one that would belong on a "someday/maybe" list. I couldn't bring me to simply strike it out; I've put a cross (x) before it instead of a dot. My thought was: "As soon as the page is finished, I'll mark the page finished anyway (which I do with a big cross over it), and then I will mark the x-ed items with yellow text marker just as I usually did."

In doing so, a "someday/maybe list" is building itself. Being a lazy person, I always prefer processes that accomplish things by themselves.

Besides that, I follow FV to the letter, so far with the impression that it is, in fact, a great improvement and the best system ever.
March 17, 2012 at 10:17 | Unregistered CommenterAndreasE
Seraphim:

<< I don't use someday/maybe lists because I have found I never look at them later. >>

I thought that was the point of them.
March 17, 2012 at 11:19 | Registered CommenterMark Forster