Hacker News new | comments | show | ask | jobs | submit login

I have found all of my procrastination to stem from lacking a certain degree of knowledge of how to perform the task that I'm procrastinating. When I don't know how to do something or I don't know how long it will take, then I don't know where it fits into my schedule, so I never fit it into my schedule. Most of the time, I grossly over estimate how long something will take, i.e. "all day" when it's probably only a 15 minute issue.

Of course, there is the opposite issue of grossly underestimating the problem. I've had "close old checking account" on my todo list for well over a two months now. I thought it would take 15 minutes to just call them, maybe scan a signature or something, and be done. They actually want me to come into the office, which is over 3 hours away (hence this issue of wanting to close the account). It is experiences like that that help to keep the gross-overestimation/procrastination game in business.

How do I fix it? I choose a day where I decide I will be fine if the only thing I get done is I find out how long it will take to get one thing done. Usually it's not that bad, though. I usually end up getting a whole slew of things done. But being OK with not getting anything officially done for a day helps me to kill the procrastination cycle.

This is exactly right, for me at least.

Sometimes its easy to know what is required, and probably guess at how long it will take (15mins or 1 day), usually because you've seen other people do it this quick. But if you don't know how to do it, and even worse, don't know where to start to learn it (which book to read, which course to take, who to ask) you can end up sitting about doing nothing but getting frustrated.

A great example is Linux. You know a task is easy (like creating an automated backup), but you can't just go and do it. You need to read up on it, you need to learn CRON and how it works, you've then got to read up on the subtle differences of your linux distro vs the one in the tutorial. You then need to read up on chmod or sudo to change the permissions, etc., etc.

Point is, it's an easy task once you know how, but when you don't know how, all you see is a huge mountain of learning you have to do to achieve it. And to make matters worse, sometimes the juice isn't worth the squeeze. Why spend all day reading up on Linux just to copy some files?

End result... I'll do it tomorrow

>You know a task is easy (like creating an automated backup), but you can't just go and do it.

Even worse is when the todo is to also make a decision. I need to automate backups to a new NAS. Do I install Linux? FreeBSD? FreeNAS? RedHat? Good old debian-stable? I should definitely explore all decision branches, in full detail, to make the best choice. open in new tab, open in new tab

But I have no idea how long that would take. I can't even set aside 15 min (or 45) to determine how long it will take. It's incomputable. It's either dive headfirst and hope to come out with a working solution, or put it off another week (and hope some howto pops up on ars).

This is why it's important to have days where I'm okay with not getting anything moved to "complete".

I don't try to find out how long it will take but how to do it. So the first time the item is on the list is 'How can I do this?', and it will transform from there. Each time it counts as a full-blown task. Usually there are some older items as well where no further overhead is needed and which are well-known. And I feel ok if I get 3-5 in total done. (Simple ones are 'Do the laundry', 'write this email where you know exactly what to write'.)

This. I also have trouble breaking large tasks into smaller tasks -- a project planning skill that some people seem to have naturally.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact