Slashdot Mirror


Beating Procrastination with Self-Imposed Deadlines

castironwok writes "Procrastination attracts us because of hyperbolic time discounting: the immediate (guilty) rewards are disproportionally more compelling than the greater delayed cost. Procrastination is the reward itself. An MIT professor found that when he allowed his students to give themselves their own homework deadlines, they would artificially restrict themselves to counter procrastination. However, they did not set deadlines for optimal effectiveness. I am personally a huge procrastinator and it's always a pull between rational logic (giving yourself the most time by choosing end dates as the deadline), and your past experience saying you will put it off so force yourself to start early."

27 of 213 comments (clear)

  1. It's inefficient to start early by JackHoffman · · Score: 5, Insightful

    Of course it's also inefficient to start late, but one should not try to start earlier than necessary. The task will occupy your mind longer and especially if you don't like to do the work, it will stress you longer. The task does not become more difficult if you put it off until you need to do it. It just gets longer, because you will allow interruptions (there's still time, so...).

    1. Re:It's inefficient to start early by TapeCutter · · Score: 2, Insightful

      "It's just a fact, if we have six months to do a job, we'll finish in exactly six months. If we're given 12 months to do the same job, we'll finish in exactly 12 months."

      This is why programmers should not be confused with engineers!

      --
      And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
    2. Re:It's inefficient to start early by Heir+Of+The+Mess · · Score: 2, Insightful

      Yeah, give an Engineer 12 months to do a 3 month job and they will deliver something completely brilliant, but unrelated to the task that you gave them. Engineers procrastinate the same, except that they do engineering stuff while whittling away the time.

      --
      Australian running a company that does C# / C++ / Java / SQL / Python / Mathematica
    3. Re:It's inefficient to start early by Anonymous Coward · · Score: 2, Insightful

      It's just a fact, if we have six months to do a job, we'll finish in exactly six months. If we're given 12 months to do the same job, we'll finish in exactly 12 months.

      But does the quality remain constant? Just because you can rush something to finish it a few months earlier, it doesn't mean you are making the most effective use of your time. You could be simply making more work for yourself further down the line.

    4. Re:It's inefficient to start early by wrook · · Score: 5, Insightful

      It's just a fact, if we have six months to do a job, we'll finish in exactly six months. If we're given 12 months to do the same job, we'll finish in exactly 12 months.

      Perhaps this is the case with your team, but I have to say that I have not observed this on the programming teams I work in. In fact, I have *often* heard managers say this. But actually, it seems not to be the case.

      I have observed two things. If the imposed deadline is shorter than the time actually needed to do the job, then the job will appear to be finished (i.e., people will say they are done), but there will be many things missing. Later, people will say "Oh, we were all under a tight deadline, so I guess we must have forgotten to do that".

      More interestingly, if the deadline is longer than the time actually needed to do the job, I have observed that the job is done early. But (and this is an important but), all of the functionality is actually there.

      To perform this experiment for yourself, I suggest that you take several small problems (small bugs are good for this). Try to find problems that will take from 1/2 a day to a day. Assign deadlines ranging from 2 hours to 3 days. Record the amount of time it actually takes to do the work. Then do code reviews of all the work.

      I think you will find the experiment very instructive.

      I have found that when there is always work in the queue, there is no point to setting deadlines. Instead it is better merely to estimate the work (so that you can make predictions). It is also counter productive to measure the amount of time each task takes (otherwise people will cut corners in order to meet some kind of unreasonable expectation, sometimes self imposed). Instead, just keep a rolling average of how close your estimates are to reality (i.e., we've gone 10 days and we've finished 11 days of estimated work, therefore we are going at 1.1x our estimated rate). This gives you predictability without the negative side effects of measuring too closely. IMPORTANT: Don't complain or cheer if the work rate is different than the estimated rate. This is to be expected. The information is only to allow you to communicate progress with management.

      In every case that I have implemented this (and obviously this isn't my idea -- it's standard practice in many shops), productivity, quality and predictability have all improved. It's worth a try (But don't take my word for it -- do the test...)

    5. Re:It's inefficient to start early by TapeCutter · · Score: 3, Insightful

      I did not mean to imply Engineers don't procrastinate, I was talking about the imposition of project end dates from above.

      Engineers do not recieve end dates, they produce them. A lead engineer is required to "sign off" and is legally responsible for the work, incompetence can land them in jail on a manslaughter charge.

      I have ~20yrs in commercial software development, some places include the programmers in the estimation processes, others don't. If my boss fails to ask me for an estimate, I will fail to join him in the "crunch time" panic.

      --
      And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
    6. Re:It's inefficient to start early by MoogMan · · Score: 2, Insightful

      It's said that there are two types of people (and many people inbetween the two extremes): Starters and Finishers. Starts are good at planning, but find it hard to continue a task. Finishers are good at maintaining, but are crap at planning or actually starting stuff. "Intermediate Deadlines" will only help one type of person (The starters - they can be good at starting these smaller projects, and not burn out). For "Finishers", intermediate deadlines may in fact make the problem worse!

      It looks, to me, that the grandparent has a "Finisher" perspective, while you have a "Starter" perspective, thus explaining your difference in opinion. Both are right. Neither are wrong. Just be aware that what works for you, is not necessarily what works for others :-)

    7. Re:It's inefficient to start early by vtcodger · · Score: 2, Insightful
      ***It's just a fact, if we have six months to do a job, we'll finish in exactly six months. If we're given 12 months to do the same job, we'll finish in exactly 12 months.***

      Maybe for (some) individuals.

      For many organizations, it's more like if we have six months to do a job, we'll take nine. If we're given 12 months to do the same job, it'll take 24. If we are given 24 months for the same job, it'll most likely never be finished.

      Observation: scheduling a 10 hour task as one hour on 10 different days may get the job done early -- not because spreading the work out is more effcient. It isn't. But because the obvious way to do the task often is not the optimal way. Stretching the job out may allow time for the realization to filter through to the forebrain that there is a REALLY simple way to do this job. This works better for individuals than organizations.

      Something that is fairly obvious, but not much discussed is that there is a good reason that complex tasks are frequently late or butchered to fit the scheduled time. It has to do with the non-linearity of scheduling. Suppose we have two tasks that we estimate will take one day each. But neither is all that easy to estimate. So we finish task A in half the scheduled time (hurray!). But task B is misestimated by the same RELATIVE amount in the other direction (Boo!). It takes two days. Total time is not 2 days, it is 2.5 days. In a really complex job, the scheduling uncertainties are likely to be huge. The liklihood is that the project will be late. Because of the non-linearity, scheduling using best guesses will almost certainly produce an overoptimistic schedule.

      --
      You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
  2. Real deadlines... by S.+Traaken · · Score: 5, Insightful

    I find that deadlines I set for myself don't help - unless it's a real deadline with definite consequences beyond my own limitations, I tend to ignore it. And even if it is a 'real' deadline, at the last moment I'll weigh the consequences of not having the job done against Yet Another All-Nighter... and sleep generally wins - or another game. Or movie. Or anything else...

    1. Re:Real deadlines... by xTantrum · · Score: 2, Insightful
      I find that deadlines I set for myself don't help - unless it's a real deadline with definite consequences beyond my own limitations
      I couldn't agree more. I currenly own a business that allows me some free time. I've been planning a VOIP application for about a year now and only just now have even started to work on the audio capture module. For the amount of time i have in the day and what i could be doing i just don't find i'm productive enough, i keep putting coding off for something else. Why? because although i'd like to be in the game, i'm not going hungry. There is no fire under me.
      --
      $action = empty(PHP) ? backToC() : unset(PHP) ; "when the concrete cases are understood, the abstractions are readily
  3. But if I don't procrastinate... by Alicat1194 · · Score: 5, Insightful

    ... what else am I going to do at work all day?

    --
    You can learn a lot about a person if you just take the time to inject them with sodium pentathol
    1. Re:But if I don't procrastinate... by p3w-451 · · Score: 2, Insightful

      Read slashdot.

  4. Anxiety by Cr4wford · · Score: 5, Insightful

    I've had a lot of issues with procrastination and anxiety, and recently I realized that procrastination is actually due to anxiety-you feel anxious about a task, so you choose to ignore it for the time being. Thus, doing things that help with anxiety often help with procrastination. I think exercise is the best answer for this, but I imagine things like meditation, yoga, etc. help as well.

    --
    Freelance Web Designer - Portfolio
  5. Re:/. is once again a full day behind reddit and d by thrillseeker · · Score: 4, Insightful

    Please perform a reddit and digg search before posting content

    Who gives a shit what's on digg?

  6. Big problem for me by astrashe · · Score: 4, Insightful

    It's a big problem for me, and one that I've only had limited success in dealing with. So I don't want to claim to have found the answer or anything.

    But I think the key is to formalize the process of deciding what to do *now*. Another way of saying that is that procrastination is a problem with deciding what to do in the moment -- that if you procrastinate, you have to recognize that your ability to do that is broken.

    The easiest way to manage this is with a to-do list -- you just go through the things on your list, and try not to think about what else you could be doing, or what you should be doing. Just work the list.

    The more robust way is to try to embrace the "Getting Things Done" system (it's described in a book of the same name). The book describes a system that's good enough to keep track of pretty much everything you have going on, and an algorithm that will let you pop off tasks and do them effectively. If you do the system, presumably (it's a big jump, and I haven't made it), you won't drop the ball on tasks, and you'll always know what to do right now.

    1. Re:Big problem for me by i_should_be_working · · Score: 2, Insightful

      Another good thing about the to-do list is that you get a sense of satisfaction after every small task is completed. So even though the big project isn't done you still get some mental reward, which encourages you to do more.

      We really are simple creatures, aren't we?

  7. Procrastination makes me more efficient by jridley · · Score: 5, Insightful

    I find that when properly applied, procrastination results in increased efficiency.
    By delaying my work significantly (but not to the point where I'll have to reduce my delivered quality) I find that I do not wind up coding stuff against docs and specs that will be changed.

    I learned this in college. We'd bust our butts trying to code something early, and the next class the prof would alter the spec because the problem contained unexpected (by him) challenges that he had not intended. If you waited a bit, the prof would code up his solution as an answer key to diff ours against, and he'd hit the challenges and recast the problem.

    So by putting off stuff to some extent, I wind up not coding stuff that I'll just wind up throwing out anyway.

  8. reasons for procrastination by falconwolf · · Score: 4, Insightful

    I've had a lot of issues with procrastination and anxiety, and recently I realized that procrastination is actually due to anxiety-you feel anxious about a task, so you choose to ignore it for the time being. Thus, doing things that help with anxiety often help with procrastination. I think exercise is the best answer for this, but I imagine things like meditation, yoga, etc. help as well.

    Another reason people procrastinate is perfectionism. Some put off doing or finishing something because they want it to be perfect but knowing whatever it is won't be perfect they delay doing it. I was kind of disappointed the article didn't mention this at all. If you know why you procrastinate you may be able to work on it easier than if you don't know why.

    Falcon
  9. Divide and conquer by DrCode · · Score: 4, Insightful

    That's what works for me. Need to implement a large piece of code and don't know where to start? Pick the easiest part of the project, and implement that. Repeat. Before you know it, you're all done. This works particularly well with an object-oriented language like C++, since there are usually lots of little methods you can work on.

    Another thing I find that helps: At the end of the day, try to leave something trivial for the start of the next day. That way, if you're not a morning person, you have something to warm up with until the coffee kicks in.

    The above also works for writing. Tell yourself that you're going to write a 200-page novel, and you'll probably never get started. Instead, think of how a story might begin, and just write a couple pages. The next day, you'll think about what might happen next, and you add another page or two.

    1. Re:Divide and conquer by mattwarden · · Score: 2, Insightful

      That's what works for me. Need to implement a large piece of code and don't know where to start? Pick the easiest part of the project, and implement that. Repeat. Before you know it, you're all done.

      Um, I know where you're coming from, but this is exactly the opposite of what you should do. If you have a large project, you want to pick the most difficult, most risky portion and dig into that first. Why? Because if you need to scrap an idea, you need to know ASAP.

      This is one of the toughest things to learn as a manager. And just because you aren't a "manager" doesn't mean it doesn't apply to you (self-management). If your approach is risky and will end up not working out, you need to know that ASAP so you don't waste your time and get weird looks from PHB asking why you just scrapped 3 weeks of work to try another approach.

  10. deadlines by baomike · · Score: 2, Insightful

    one nice thing about deadlines, if you put them off long enough
    you don't have to worry about them any more.

  11. Re:Add more to your agenda... by WCLPeter · · Score: 2, Insightful
    If you are procrastinating - you don't have enough to do.


    I've always hated this argument. It's based on the notion that obscene overwork will somehow make you forget why you're procrastinating in the first place. Most people procrastinate because the task is so mind nubmingly boring that they'd rather take time off work to clean their house (which they'll procrastinate doing once they're home).

    Assign me tasks that are actually interesting. A task I'm interested and excited to be working on I almost never have trouble completing on or even before time.

    Taking on extra tasks doesn't work. Sure you're busy and working like a dog just to keep up, but you're still going to be bored. Only now you won't have the wiggle room to procrastinate and prioritize tasks, making you a bundle of nervous energy on it's way to burning out quickly.
  12. Factoring Genes. by Anonymous Coward · · Score: 1, Insightful

    You know there's one factor left out that could apply to some people who procrastinate. Medical reasons.

  13. Re:/. is once again a full day behind reddit and d by Mard · · Score: 5, Insightful

    Who gives a shit what's on digg? Precisely. Digg. Reddit. Slashdot is all about intense commentary (nay, we have discussion, even!) on topics which interest a wide geek user base, NOT about who got the news out first (although Slashdot is still quick enough to get the big news out in a meaningful time frame). If you care about is hearing things first, stick to Digg with their 1-3 line comment of "I agree with the article." and 40 responses of "Me too." Honestly, what purpose does it serve to find articles one day earlier, if there are no comments as insightful as those here on Slashdot to bring meaning and a wider perspective to it? Same article, sure. They both had it yesterday, sure. Slashdot has 50x as many comments in 1/20th the time. I'll be sticking here, thanks.
    --
    DRM = Digitally Restricted Media. This is a viral sig, pass it on.
  14. not so sure about the conclusions for Study 1... by bnf · · Score: 4, Insightful

    If you look at the "Procedure" section of page 220 of the pdf of the actual paper (because I know all of you of course have now read the paper) it talks about the apparent incentives for the subjects involved in the study by stating "In fact, the external incentives for the students in the free-choice section encouraged submission of all three papers on the last possible day."

    In the paragraph prior the writer states "second, students had to announce the [self-chosen] deadlines for submission prior to the second lecture;"

    and then on the next page "in fact, only 12 student (27%) chose to submit all three papers on the last day of class."

    The study was conducted at MIT. The paper never acknowledges the role peer pressure and the desire to be perceived as a non-procrastinator by the rest of the class might play in an individual's choice of paper submission date, particularly if that "announcement" was public, and instead focuses on how the submission deadlines would best be gamed; Yet peer pressure and performance pressure at MIT is an acknowledged problem very much part of the culture of MIT.

    --

    this space intentionally left blank (oops)

  15. Re:Hey! by O_at_H2-O2 · · Score: 2, Insightful

    It's really ironic that this gets posted on /.

    I mean, who reading this now has done all their dishes, their work for the day, called their grand-parents to thank them for their Christmas gift, paid all their bills, sent that inquiry to the insurance company, called in for that dentist appointment that is 3 months overdue, etc... I mean who?

  16. Biased Sampling by DynaSoar · · Score: 2, Insightful

    > An MIT professor

    Hint #1

    > found that when he allowed his students

    His MIT students. Hint #2.

    > to give themselves their > own homework deadlines, they would
    > artificially restrict themselves to counter procrastination.

    Leaving aside the begged question as to what is normal/natural restriction
    as opposed to "artificial" restriction, the observation is from a situation
    that is not representative of the general college student population, and so
    no generalization can or should be drawn from it.

    I've taught at two different state level colleges which aren't much above
    community college level as far as academic rigor among the students. I didn't
    require attendance and rarely set a deadline other than the required planned
    exams. I rarely got anything until near the end of the semester, and even after.
    I finally had to start giving graded quizzes before the lecture to (a) force
    attendance and (b) force them to read the material before the lecture (a
    requirement of mine because I don't read the book to them, I add to it), or
    (c) accumulate evidence in the form of missed quizzes/homework/classes to drop them.
    Nothing motivates students to show up and to do their work in a timely manner
    like seeing one of their (ex-)classmates being told he doesn't need to be there
    ever again because he was dropped because he missed too much.

    And it's a damn shame I had to do that. Both places had a large proportion of
    "non-traditional", that is, not right out of high school, usually older, have
    families, jobs and all the problems that come with these and other normal adult
    life. I'd set things up so those students could take the course, and never come
    to class at all, if they could learn enough on their own from the book to make the
    grades they needed on the exams. And I didn't want to make those changes -- I was
    ordered to because too many of my students were failing. Yeah, like I made them
    not do their work.

    Online courses were the worst. Most (not some, not just the majority, but most)
    students would do absolutely nothing* until the day before the exam, and then
    spend 1 to 3 hours reading through the material. One third dropped out after
    the second of 4 exams because they couldn't possibly pass. One third were urged
    to do the same for the same reason, but neglected to even do that, and so failed.
    Of the one third that remained, 90% got A's because they had the necessary sense
    of responsibility and motivation to do the necessary work on their own.

    --
    "I may be synthetic, but I'm not stupid." -- Bishop 341-B