Slashdot Mirror


Arbitrary Deadlines Are the Enemy of Creativity, According to Harvard Research (qz.com)

Time can feel like the enemy to an employee in any role, and in any industry, but it's most acutely threatening to creative types. From a report: We may tease them for their diva-like behaviors when they feel persecuted by a deadline, but we have to admit that "develop an amazing new idea" is not something that slides into your schedule, like pick up lunch or respond to new clients. Nor can systems be tweaked and extra hands hired to help hit a goal that requires innovation, the way they can when mundane busy work is piling up. And yet deadlines are a fact of life for any company that wants to stay competitive. In a recent Harvard Business School podcast, professor Teresa Amabile, whose academic career has focused on individuals, teams, and creativity, offers some guidance for managers who struggle to support or coax their creative talent. She explains that although the creative process itself can't be controlled, certain structures can set up the conditions to move it along. When possible, managers should avoid tight deadlines for creative projects. In her work, Amabile found that creative teams can produce ideas on a deadline, and creative people may feel productive on high-pressured days, but their ideas won't be inspired.

29 of 123 comments (clear)

  1. Not enough time to make an insightful first post by Aero77 · · Score: 5, Funny

    Curse these deadlines!

  2. Rumination by omnichad · · Score: 5, Interesting

    Rumination is free labor. If I'm thinking about a project for several weeks when I'm in the shower, trying to sleep, driving - that's extra overtime for free.

    Doing all of my thinking on a tight deadline while also doing the actual design or coding involves a lot of bad guessing. But there comes a point where I could just think about all the possibilities forever and never start or get anything done.

    1. Re:Rumination by computational+super · · Score: 2

      Arbitrary deadlines = arbitrary results.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    2. Re:Rumination by ranton · · Score: 4, Interesting

      Doing all of my thinking on a tight deadline while also doing the actual design or coding involves a lot of bad guessing. But there comes a point where I could just think about all the possibilities forever and never start or get anything done.

      Like most things, you aren't going to get good results if you don't have implementation teams you can trust to give realistic estimates. And management teams who listen to these estimates, while probably making slight adjustments based on past results (almost always adding time to the estimates).

      I'm in a project right now where we were introduced to the project early October, sat down for a full day requirements gathering session mid-October, and gave estimates by the end of October. We estimated code completion in mid-January. They gave us a mid-December deadline. The product will now be complete at the end of January, after spending weeks in constant status meetings trying to hit that ridiculous deadline.

      In the end the only thing that changed from the results we promised in our first estimates is now the team's two architect-level resources are prepping our resumes just in case this type of shit doesn't happen again and/or this year's bonus isn't a high five figure amount (aka starting with a 3+).

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    3. Re:Rumination by jellomizer · · Score: 5, Interesting

      There is a difference between an Arbitrary deadlines vs no deadlines.

      Often we will get a deadline, based on the Boss trying to impress a partner, or a customer, or just beat competition to the market. These deadlines are not based on what it would take to do the job right and best. However if someone went to me and say we need to solve this problem, I can usually give a fair ballpark figure on when it can be done by, and add some buffer for unforeseen problems, Then you can have a good deadline, where the project keeps moving and gets done, without stressing and taking shortcuts to meet it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    4. Re:Rumination by the_skywise · · Score: 2

      Do you work at my last company?
      We spent over a week hammering out work and time estimates for a large project because management demanded we were going to have a realistic schedule this time. No other work was done. We were in day long meetings knocking out feature requirements and possible work load and time estimates for it. In the end we hammered out a 10 month time estimate (basically the following March) - management turned around and said it had to be out by Christmas and took a "F- it we'll do it live" attitude.
      We sat there afterwards with our jaws on the floor wondering a> Why they didn't stipulate Christmas as a hard deadline to begin with and b> why they made us waste a week on a schedule for an already looming deadline!

    5. Re:Rumination by thomst · · Score: 3, Insightful

      omnichad observed:

      Doing all of my thinking on a tight deadline while also doing the actual design or coding involves a lot of bad guessing. But there comes a point where I could just think about all the possibilities forever and never start or get anything done.

      Yep. Making the perfect the enemy of the good is never a useful strategy. It's a prescription for inaction.

      Having said that, your first point:

      Rumination is free labor. If I'm thinking about a project for several weeks when I'm in the shower, trying to sleep, driving - that's extra overtime for free.

      is absolutely the case, IMnsHO.

      I'm a writer. A key part of my process is thinking about what I'm going to write. In particular, whether it's a chapter in my novel, an opinion piece, or a feature story, the most important product of my rumination is the opening and closing lines. Assuming I've done the necessary research, and I know the points I want to cover, once I have those taped down, the bit in between them almost writes itself.

      If you work in journalism, you write to deadlines all the time. Under that kind of pressure, stuff tends to falls on the floor - and sometimes that stuff is important. For the most part, that's where corrections and retractions originate: the need to get the piece submitted by an arbitrary deadline (trying to "scoop" the competition, as a big, fat for-instance) incentivizes sloppiness. That's why there used to be people called "fact checkers" in the industry - and, believe it or not, they had the power to spike a story, if it contained factual errors (or simply assertions for which there was insufficient evidence).

      Now? Not so much. The really big guys - NYT, WaPo, WSJ, etc. - can still afford to pay those people, but they inevitably are a dying breed, like circus elephant trainers. That's driven by economics, of course. As circulation numbers for print media have plummeted like an Acapulco cliff diver, so have ad revenues - and ad revenues, not subscription fees, are where print media makes its principal income. (That's also true of digital publication, where ad revenues are tiny compared to print, so fact checking in the online world is mostly post hoc, and conducted for "Gotcha!" purposes, rather than to ensure the journalistic ducks are properly aligned before you click "Publish!")

      The thing is, though, that, for businesses in general, deadlines are a necessary and unavoidable evil. Creative teams rarely work in a vacuum - Google's Project X skunkworks notwithstanding - and it's just impractical to budget and responsibly allocate resources for "When you get around to it ... "

      --
      Check out my novel.
    6. Re:Rumination by dgatwood · · Score: 2

      Arbitrary deadlines are fine, too. What's not fine are deadlines that don't match the work required. If you give me a month to get a new release of an app shipped, I can do it. If you give me a week, I can do that, too. The difference is that the one released after a week will less than a quarter of the changes that would have been in the one released after a month.

      Of course, at some point, a too-fast release cadence can slow down development by requiring you to maintain too much redundant code while you do large redesigns of parts of the app that require multiple release cycles to complete, but that's a separate issue.

      There are two approaches that work: A. choose an arbitrary feature set and then figure out how long it will take to implement those features, or B. choose an arbitrary deadline and then figure out which proposed features you can pull off by that deadline. What doesn't work is choosing an arbitrary feature set and an arbitrary deadline independently. :-)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

  3. Two obvious examples by Hognoxious · · Score: 5, Funny

    Systemd and Gnome 3. These would have been much better if the deadline was around 2075.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  4. You needed a scientist to figure that out? by computational+super · · Score: 4, Insightful

    What's next? We'll discover that noisy open office bullpens aren't conducive to any sort of work that requires concentration? Or will we discover that most managers don't much care about productivity as long as they maintain the illusion of control?

    --
    Proud neuron in the Slashdot hivemind since 2002.
    1. Re:You needed a scientist to figure that out? by jellomizer · · Score: 2

      Such studies even if it points out something you know is true, you can actually quantify its affect. Because there are also studies that show evidence of things you though were true, to actually be false, or something that has little overall effect.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:You needed a scientist to figure that out? by gfxguy · · Score: 2

      Ahh.... open office plans... the problem with your post is that we've known the truth for at least half a decade or more, but you are absolutely right - as long as the work still gets done, it doesn't matter that it wasn't as good as it could have been. Quantity over quality. Actually, even that's not true. In my work environment, open concept didn't improve quantity - it simply reduced quality while also reducing expenses (cramming 4x as many people into the space), and I'm sure some accountant living 1000 miles away (the order came from the corporate overlords, after all) is patting him/herself on the back with the gold plated hand bought with the huge bonus they got.... all while sitting in their nice corner office in some nice office building somewhere.

      No, I'm not bitter.

      --
      Stupid sexy Flanders.
    3. Re:You needed a scientist to figure that out? by computational+super · · Score: 2

      Hand in your resignation all you like. The next job will be an all-distractions, all-the-time open office just like the last one. They can do it, so they do.

      --
      Proud neuron in the Slashdot hivemind since 2002.
  5. Re:Amabile found... by computational+super · · Score: 2

    It doesn't matter if the ideas are inspired - it doesn't even matter if they work! As long as they're on time.

    --
    Proud neuron in the Slashdot hivemind since 2002.
  6. Agreed. OTOH by Anonymous Coward · · Score: 2, Insightful

    The second biggest enemy of creativity is probably the lack of any deadlines. With no urgency, the creative project is put aside for more immediately pressing tasks (or distractions).

  7. But often things don't get done... by Anonymous Coward · · Score: 5, Insightful

    if you don't have a deadline. What's the compromise?

    Seriously, I've noticed that after working just over twenty years managing programmers and a few product people that things get done when you schedule a spec review or a demo.

  8. Why even bother with deadlines? by plopez · · Score: 2

    We never achieve them anyway. It normally starts out as, "We need to deliver a high quality product with A,B,C,D,E,F,G,H by the deadline."
    Then it goes:
      But we can't do D due to a defect in the vendors/open source project's libraries.

    The deadline is slipping so we talked the customer into deferring the release of E until the next release.

    Oops C relies on D so we can't ship that.

    Chris and Bob quit so we are even more short handed than before.

    G is experiencing massive scope creep, let's cut capabilities so we can ship it.

    We're more short handed than ever so we can't fix more than critical bugs.

    The QA automation is falling behind due to all the changes so we'll have to test manually.

    So what get's shipped often looks nothing like what was promised. All that happens is the goal post is moved and victory is declared.

    --
    putting the 'B' in LGBTQ+
  9. Re:creativity is overrated in STEM by TheFakeTimCook · · Score: 3, Insightful

    It's good only for brain storming part, which is the very beginning After that you just apply due process.

    Sounds like someone who has never actually done anything that requires actual creativity.

    Keep in mind that, each time a Developer, or Development Team runs into an unforseen challenge, that essentially RESETS the "Brain Storming Part" timer. So, in REALITY, "Brain Storming" actually occurs MANY TIMES during EVERY Development Project more complicated than "10 GOTO 10".

    If you believe anything else; you're delusional, clueless, or both.

  10. Re:Often deadlines are external by HornWumpus · · Score: 3, Interesting

    Until a client has informed you that the marketer asked them to ask for a 'very short timeframe' in order to 'motivate the team' you haven't lived.

    We found that out...it was the half the team (the competent half) or him. He is still working there. Never so glad to leave a place as that one.

    Sometimes it becomes crystal clear what the bastards think. Vote with your feet.

    --
    John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
  11. Re:Define arbitrary by jellomizer · · Score: 2

    How many bosses do you see calculating the time vs reward calculation? Not many. They will normally just use a gut feeling if it is worth it or not.
    At one job I had, the Boss gave us 2 weeks to have a demo proof of concepts in front of the customers. No matter how complex it was we had 2 weeks.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  12. I Disagree by the_skywise · · Score: 3, Insightful

    A looming hard deadline can do quite a bit for creativity - ask any writer. Given enough time, GENERALLY, you can create a better solution or work but this can also be a hindrance.

    For proof I submit - Star Citizen.

  13. Different priorities in different scenarios... by Junta · · Score: 3, Insightful

    When you are dealing with a situation with other folks depending on you, then the timetable may matter moreso than how creative it can be.

    However novel new capabilities are not generally well served by making up a deadline if one does not naturally exist.

    However that later situation drives managers/project managers insane. Why even bother trying if you don't know when you would finish, how can you 'grade' yourself if you don't know when you would deliver, so make up something.

    Having a backlog of ideas without a milestone to make them due is a fine thing, but project management *must* have it on a roadmap or else get pissed.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  14. Deadlines by daveywest · · Score: 2

    Even God has deadlines. If He let his deliverables slip on days 1-5, you wouldn't be here.

  15. They're a necessary evil by jandrese · · Score: 3, Insightful

    The problem with having no deadlines is that too often nothing gets done. Look at Valve for an example of what happens when management is too hands off. Half Life 2 Episode 3 is a full decade behind schedule now. I get that you can't rush greatness, but you gotta keep it motivated.

    --

    I read the internet for the articles.
  16. Is time a special case for constraints? by Anonymous Coward · · Score: 2, Interesting

    Problem A: think of a cool name.

    Problem B: think of a cool name for a starship.

    Which of the above two problems is easier and which is harder? If you solved both problems, which name was cooler?

    My guess is that problem B was the easier one and it's also the one where you came up with the cooler name. Why? Because it had a constraint, and perversely, constraints cause creativity. Or so I've thought.

    Problem C: think of a cool name for a starship, within 30 seconds.

    I added another constraint, so you got even more creative, right? No. Something about time as a constraint is .. odd.

    But wait a minute. Let's say I show you a mid-game chessboard, and it's white's turn. In one scenario, I give you lots of time to try to come up with the best move. In another, I give you only 10 seconds, and then you must make a move.

    Which chess move to do expect to be the most interesting? Note, I didn't say the best, just the most interesting. I think maybe the time-constrained solution might come out on top.

    Is this all bullshit, or is there something interesting about time?

  17. Best Busines Reason Ever! by avandesande · · Score: 4, Interesting

    Once I asked an application owner what was driving the absurdly short timeline and he replied with a straight face that it was when his yearly review was to occur.

    --
    love is just extroverted narcissism
  18. It's project management by ErichTheRed · · Score: 2

    The problem I have with arbitrary deadlines isn't really the date, although those can be unrealistic. It's the never-ending nagging of project managers. Anything that prevents them from checking the box they need to check or moving the date out on their Gantt chart is an immediate emergency that must be addressed by endless status meetings. The endless status meetings make the project later by tying people up discussing strategies to reduce the time something will take.

    I think part of it is that PMs have been taught that, just like MBAs, they can project-manage anything. And I can see their methods when they make $100K+ and their sole job is to check those boxes, or nag nag nag until they are. But creative work on any complex project isn't like drywalling a commercial building. There are some things you can't rigidly schedule, but software development is treated exactly like a construction project.

    I have noticed that the best project managers don't nag -- they're often the ones who've actually done the work before and aren't looking to throw you under the bus. The worst are the PMP clones. I seriously have had a couple PMs who are following the PMBOK line by line, using the PMI-approved terminology, and PMI-approved nagging/threatening techniques. That's the kind of PM you don't want.

  19. Tree Tap by mentil · · Score: 2

    My understanding is that creativity is like tree sap. You can tap into it periodically, draining it, but you can't do anything to speed up its production.

    --
    Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
  20. \o/ by easyTree · · Score: 2

    Q) Why hasn't this project been completed to deadline?
    A) Because you pulled the deadline out of your ass, without considering the amount or complexity of work required to deliver, ignored feedback that the deadline was unreasonable and inserted more tasks after the project started.