To Think About . . .

It’s not whether you win or lose, it’s how you place the blame. Oscar Wilde

 

 

 

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

Discussion Forum > Can anyone explain Dismissal for full page rule in SFv3?

<<When you visit a page which is full (i.e. both Column 1 and Column 2 are full), all Column 1 tasks on that page must be either actioned or dismissed.>>

Dose it only because I cannot enter more task on this page?

When I move to the *next* page, dose it mean all tasks in C2 are useless?(Then I can erase them for saving space)

<<Enter urgent tasks in Column 2 of the page you are currently working on. If there is no more room in Column 2, then enter it on the first page on which there is room.>>

If I can erase all tasks in C2 of this page, then I can enter new task on this page. Am I right?

I think 25-35 lines per page make C1 a close list. But C2 should not be another close list at all, it's just the complement for C1. If I can erase it or make it with unlimited lines, thing gonna be easier.

My first post.
IL
June 2, 2011 at 14:12 | Registered CommenterIL
SFV3 was designed for use with pen and paper. There is no such thing as erasing tasks. Beyond that, if you use an electronic device it's technically possible to erase tasks, but doing so may destroy the balance in the system. C2 should be of limited size such that if over time you are doing too many C2 tasks, the remaining C1 tasks are dismissed (highlighted and put away for later review). C2 tasks are never dismissed, but all must be worked on.

"If I can erase it or make it with unlimited lines, thing gonna be easier." I completely agree that it would be mechanically easier in most digital programs. I can't vouch for whether you will have success either way.
June 2, 2011 at 14:22 | Registered CommenterAlan Baljeu
Pencil! When I need to cross one C2 task, just erase it :-P
I don't need to highlight it and review it later.

30 lines are enough for C2 tasks at most of the time. Except when the current page is the last page (or I've returned to an old active page). All unfinished tasks re-enter on the 1st active page, but C2 is not empty on that page.

So if I erase all processed C2 tasks just before moving to the *next* page (but not erase it asap), it just like it's a new page for C2. And won't destroy the balance.

If it technical possible, I wish when I go back to the old page (1st active page), all finished and highlighted tasks are achieved, so only unworked C1 tasks and unfinished or new entered C2 tasks are on that page (or every next page).
Just like when I move to the next page, I cross and re-enter all unworked C1 tasks to the end.

I gonna try it myself :-) Fun.
June 2, 2011 at 17:02 | Registered CommenterIL
Why dismiss when C2 is full? Here are some reasons. It depends partly on WHY C2 got filled.

(1) C2 got filled because you have lots of ongoing unfinished work and/or urgent work. This means you really don't have time for those C1 tasks right now. Dismiss them. You can re-enter them when (if) you have more bandwidth in the future. Right now, you already have too much on your plate, so take care of that first. Dismissal allows you to do that.

(2) C2 got filled because you cycled through your list many times but only a very small number of C1 items stood out on each pass. This means you've had repeated exposure to those C1 tasks and they STILL did not feel ready to be done. Dismiss them. This will allow you to focus on what's really important to you right now. You can re-enter them when (if) they call out to you in the future, during a review of dismissed items. But for now, you need to get them out of the way.

(3) Combination of (1) and (2). Dismiss them. You've got enough to do already.


"Dismiss" does not mean "delete" or "kill" -- it means "put them in the drawer, for later consideration".

Dismissal frees you to focus on the things that are really important right now. Don't be afraid of dismissal.
June 2, 2011 at 21:54 | Registered CommenterSeraphim
Seraphim:

Thank you so much. now I'm more clear now.

Reason 2 sounds like it accelerates tasks being dismissed.
It's for a better balance to let me (auto) focus on the really import tasks.

How often the (2) happens in your experience?
When it happened, about how many times had you visited those C1 tasks?
June 3, 2011 at 7:51 | Registered CommenterIL
Now can someone explain their thinking pattern for successfully clearing the dismissed pages?
June 3, 2011 at 13:33 | Registered CommenterAlan Baljeu
Most of the time, you viewed it more than twice (3-5 times?) before you dismiss it.

Some are not worth to do, some will not work on it in the near future (5 days or more).

Highlight it and forget it.

If you really wanna give it a chance, re-enter it, and highlight the rest. (Trust me, you won't do it next time you see it)

So I just killed this page, and go on.
June 3, 2011 at 14:11 | Registered CommenterIL
That's not how I perceive the process, IL. I see it as
1) Hightlight everything and forget everything
2) Periodically review the highlighted items.
a) Some you may reconsider, and put back in.
b) some you may delete.
c) Some you may leave for a future review.

But (2) doesn't seem adequate. When there's a lot of items to review, you tend to skim, and (c) is most often chosen. This is bad because the dismissed-but-not-dead pages keep growing out of control.

I have my own answer, but it doesn't fit the SF rule set, so I ask.
June 3, 2011 at 14:19 | Registered CommenterAlan Baljeu
Me too.
I don't review dismissed items often.
And few of these items will be re-entered to the list, (some will be closed).
Most I just left it there. (e.g. read XXX book)

May copy them to another dismissed-only notebook?
June 3, 2011 at 15:38 | Registered CommenterIL
IL wrote:
<<< How often the (2) happens in your experience? >>>

It has happened several times, but usually for me it's (3).

Of my pages that get dismissed, I'd say about 90% get dismissed simply because nothing stands out. Only 10% get dismissed because C2 is filled up.

When I first started with SF it was the reverse.


<<< When it happened, about how many times had you visited those C1 tasks? >>>

If a page gets dismissed because of C2 being filled up, it's usually because of a circumstance like this:

- I have too many meetings and not enough discretionary time

- As a result, I don’t cycle quickly enough through the pages

- As a result, new items go into C2 more often, because I want to make sure they get attention in a timely manner

- C2 gets filled up after 2 or 3 visits in these cases
June 3, 2011 at 19:03 | Registered CommenterSeraphim
Alan Baljeu wrote:
<<< Now can someone explain their thinking pattern for successfully clearing the dismissed pages? >>>

When I have a small number of dismissed pages, I can easily review them all in just a few minutes. Having a recurring task "Review dismissed" works fine.

When there are too many dismissed pages and I can't cycle through all of them in one review, then I start entering "Review dismissed on page XXX" instead of just "Review dismissed". Those smaller review items work well for filler time, such as waiting at the doctor office or multi-tasking during part of a meeting where my attention isn't required.

If the items for review are in a previous SF book, then I put a limit on how many times I should review it. I'll enter "Review dismissed, old book, 1 of 3" or something like that. After the first review, I'll enter "Review dismissed, old book, 2 of 3". After 3 of 3, I am done with that old book and cross everything out, or toss the book, or file it.

Once, I just cut all the dismissed pages out of my book, stapled them together, and put them into my Paper In Box. I then handled them as any other project -- "Clear the stapled stack of dismissed pages" -- which got entered into C2 repeatedly until it was cleared. That worked pretty well - I liked how SF drove me to finish up with that stack. It helped force me to be more decisive about whether I really wanted to keep those tasks hanging around or not.



<<< I have my own answer, but it doesn't fit the SF rule set, so I ask. >>>

What is your answer?
June 3, 2011 at 19:13 | Registered CommenterSeraphim
My answer: Change the SF rules drastically, so that it's not really SF anymore. With these rules, the question of dismissing comes up less often. More often things are deleted from a page long before they get dismissed. When an occasional page is dismissed, I immediately consider the handful of items, and either delete them or merge into a project plan and add "plan this project" back into SF.
June 3, 2011 at 20:22 | Registered CommenterAlan Baljeu
I still feel strange about the dismiss full page rule. And thanks God, it does not occur too often.
I wish this rule's disappeared, if there's final perfect version.

About the dismissed tasks.
I think we need another simple system to manage them.

I'll show you on another thread.
June 4, 2011 at 9:08 | Registered CommenterIL