In his latest book - which is a very good book and you should read it - Mark Forster, an inventor of time management systems, writes about routines and consistency as fundamental to success in productivity.
Routines however lend themselves very well to being scheduled on the calendar.
Mark never criticised that practice as a bad way.
But the whole idea of the Long List and the tm-systems based there off was also about getting rid of static scheduling.
I found the Long List far superior in finding just the right time for commencing a task than more rigid scheduling and specially with those repeating tasks I got much better.
But what a schedule provides and the Long List doesn't, is an inherent agreement on when not to do a task (which means I don't have to think about it) and of frequency of doing the task.
I feel troubled and conflicted with that.
How can I use the Long List in conjunction with a schedule without destroying the usefulness of either?
Think of it this way. There are two broad categories of routine. Routines which relate to a specific time of day, and those which don't.
Routines which relate to a specific time of day might include:
Early morning routine
Travel to work routine
Opening up the office routine
Lunchtime routine
Closing work routine
Evening routine
Bedtime routine
Those may not all be appropriate for your circumstances of course, but I hope you get the point.
The routines which don't relate to a specific time of day might include:
Filing
Emails
Correspondence
Payments
Thinking Time
Writing
And so on. Whatever fits your particular situation.
The routines which relate to a specific time of day don't need to be on your long list because once they are established they should be happening automatically. Those which don't relate to a specific time of day do need to be on your list.
Routines however lend themselves very well to being scheduled on the calendar.
Mark never criticised that practice as a bad way.
But the whole idea of the Long List and the tm-systems based there off was also about getting rid of static scheduling.
I found the Long List far superior in finding just the right time for commencing a task than more rigid scheduling and specially with those repeating tasks I got much better.
But what a schedule provides and the Long List doesn't, is an inherent agreement on when not to do a task (which means I don't have to think about it) and of frequency of doing the task.
I feel troubled and conflicted with that.
How can I use the Long List in conjunction with a schedule without destroying the usefulness of either?