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 > Prioritising baclogs

One of the nice things about DIT is that, since one gets a day's work done in a day, one doesn't need to prioritise. It doesn't matter what order things are done as long as they are done.

But if one has a backlog, by definition it's going to take more than a day to shift. Doesn't this suck one in to choosing what's urgent/important/all the not so nice things DIT seeks to defend us from?
April 4, 2008 at 16:39 | Unregistered CommenterDavid C
My view with my backlog is that often the tasks have been waiting for a long time to be completed so a bit longer isn't going to cause many problems.

I am working through it as my current initiative at the moment and generally pick one that appeals to be on that morning. I know it may not be the most urgent or most important task on the list, but I am making headway to clear the backlog.
April 6, 2008 at 10:28 | Unregistered CommenterKate Davis
David:

Yes, it does. Which is why one should never regard having a backlog as the "norm". Apart from the initial backlog when you start the DIT system for the first time, backlogs should be regarded with horror. Sometimes they are the best choice out of two evils, but they are almost always a symptom that something is wrong.
April 10, 2008 at 11:49 | Registered CommenterMark Forster