This post's headline is intended as a friendly riposte to Elisa Freschi's recent post, "You are not too busy, just disorganized." In brief, in response to a frustrating situation, Elisa enjoins all of us to either (1) stop overcommitting to projects that we cannot follow through upon in a timely manner, or (2) develop organizational skills so that we can follow through on our commitments.

I think (I hope!) Elisa's basic point is easy to agree with. It's common courtesy not to leave other people on the hook for bad planning, and better courtesy not to make excuses for oneself when one does plan poorly. But, of course, for many people, good planning is easier said than done! We often make commitments with the best of intentions, fully intending to meet our deadlines…and yet, all too often, we find ourselves overcommitted and struggling to meet those deadlines. Which begs the obvious-enough question: how can avoid landing ourselves in these types of situations?

In today's post, I am simply going to make a friendly suggestion to those who find themselves strugging to meet deadlines or get things done in a timely manner. Although I recognize that people work differently, and that the suggestion may not work for everyone, the strategy I'm going to describe has worked splendidly for me–and so, if you're having trouble, maybe give it a try! 

It's natural enough to think–as Elisa's post suggests–that being "well-organized" is conducive to getting things done. I actually don't think this is the case. At least it hasn't been my experience that being "well-organized" in any traditional is conducive to getting things done. I know some people who are incredibly well-organized–people who have daily lists of things to get done, planners detailing their daily schedule, etc.–but who are constrantly struggling to meet deadlines. I think there is a general problem with this entire approach to getting things done. Let me explain.

Suppose you set aside 2 hours to work on a Project A (e.g. a paper for an edited volume that there's a deadline for), 2 hours to work on Project B (e.g. reviewing a paper for a journal), 2 hours for Project C (e.g. lectures), etc. On the surface, this looks like good planning. But there's a perfectly simple way in which it can predictably lead to a failure to meet deadlines. Suppose you spend your 2 hours working on Project A, but you end up mucking-around (we all have those days, right?). In that case, even though you dedicated 2 hours to Project A that day, it was time wasted. You didn't get squat done on the project, and you could have spent those two hours hacking away at other things you need to get done. And herein, I think, lies the horrible garden-path. You muck around on Project A, not getting far; so you fall behind schedule. Then, because you only left yourself 2 hours on Project B, if you're not super-efficient on that project, you fall behind on that one too. All of a sudden, there you are: you "planned fantastically", and yet you're not meeting any of your deadlines!

I think there's a simple, killer way to solve this problem: move back and forth from project to project constantly, on the fly, so that you're always getting a little bit of everything done. In other words, don't do this:

  • 2 hours for grading
  • 2 hours for working on Paper A
  • 2 hours for working on lecture notes
  • Etc.

Instead, try bouncing back-and-forth between projects on the fly whenever you find yourself wasting time or getting tired with what you're doing–as in:

  • Grade 2 term-papers; immediately move on to:
  • Editing a page of paper A…until you hit a roadblock; then immediately move on to:
  • Writing several Powerpoint lecture slides; then move on to:
  • Grading daily assignments for Class #1; then move on to:
  • Editing a page of project B; then move on to:
  • Grading 2 more term papers; then move onto:
  • Writing ten powerpoint-slides;
  • Etc.

This kind of project-hopping might sound like complete mayhem–but I think you may find yourself surprised just how well it works. Because you're always moving from thing to thing, you're almost constantly crossing things off your to-do list (e.g. 2 papers graded here, 5 lecture slides there, a page of a paper written/edited there, etc.), slowly but surely whittling away all of the stuff you need to get gone.

Contrast this to the strategy of laying aside 2 hours for this project, 2 hours for that, etc. The problem with this, again, is that it's really easy to waste time when you're working on a single project (e.g. a single paper, grading, whatever) for a set time-period. For example, suppose you decide to spend 2 hours on a paper you've been writing. We all know how this can go. You run into a roadblock, sit and think for 30 minutes, revise that same paragraph again, etc. All of a sudden you've wasted two hours. You can avoid this by simply moving from project to project. On this model, whenever you start to struggly with something, you don't sit and think about it for 30 minutes; you move onto 2 paper you need to grade, five lecture slides you need to write, etc. In other words, the 2 hours you would have wasted by setting time aside are 2 hours you are grading 2 papers, writing 5 lecture slides, etc. All of which gets more done. 

The other great thing I've found about bouncing back and forth from stuff is that it really goes a long way to preventing fatigue. Grading a stack of 40 papers? Goodness, it's monotonous. Grading 2 papers, editing a page of a paper, editing a job application letter, grading 2 more papers an hour later? Not monotonous at all. Indeed, suprisingly fun!

Or maybe not. Again, like I said, we're all different. Maybe this Mayhem Strategy won't work for you–but if you are one of those people who struggle to get things done, maybe it couldn't hurt to try something new! :) 

Posted in

3 responses to “Maybe you’re not too disorganized. Maybe you’re too organized!”

  1. Hi Marcus and thanks for the exhaustive answer.
    Two thoughts, in increasing level of importance:
    1) You can jump from one task to the other only if you have previously organised yourself (e.g., you know that you have to grade 40 papers by the end of the week, to revise your paper before 10 days, to write an introduction to your edited book before 1 month, to finish your dissertation/your next book within 24 months etc. etc.) If you don’t, you risk just to run from the thing you first remember to the thing which first comes to your memory next and to avoid dreaded tasks all the time! In other words: your method, it seems to me, presupposes a careful scan of what one has to do and of one’s deadlines.
    2) (Connected with the above, let me just share my experience:) I am always involved in many projects, and I enjoy doing small things such as working for some minutes on the organisation of a certain panel, than emailing someone else concerning another conference, etc. This means that I often keep on doing this kind of things INSTEAD OF doing the really important things, such as working on a difficult point I cannot solve. You have suggested to leave an article as soon as you “run into a roadblock”. This might be true most of the times, but sometimes the question I have to deal with is so complex, that I just need to face it and to face the roadblock —until I can solve it. Leaving it will not help me further the next time.
    (At the present time, for instance, I am constantly avoiding to work on an article on deontic logic, which lies beyond my confort zone, but is for the same reason more interesting than many other things I can easily handle.)
    I know you were talking about different blocks, the sort of blocks one experiences when one is bored, so let us just agree that there are blocks which might be useful, since they are indications of real problems… they need to be taken seriously and need time.,

  2. Hi Elisa: Thanks for your reply. Here are my thoughts:
    On (1), I actually don’t think that’s true! I have a rough list in my head about what needs to get done and by what date–but I don’t find that it really affects what I do. I just do a little bit of everything every day and end up meeting deadlines. So basically, I think if you’re always getting a little bit of everything done, you’ll tend to meet deadlines even if you don’t plan ahead.
    This is really the point of the strategy–namely, that getting stuff done is not about planning ahead at all, but rather making sure you’re constantly knocking different things off your to-do list everyday!
    On (2), I’m not advocating avoiding really important things for less important things. So, for instance, when you say that you’re constantly avoiding that article on deontic logic, you’re not following the strategy I’m recommending. The strategy is to spend a little time on it every day, as well as a little bit of time on everything else (ignoring none of your projects!).
    The point of the strategy is to bounce back-and-forth between important and less-important projects–ignoring none of them–so that you’re always making a little headway on everything, and moving on when you get stuck so that you don’t waste precious time.
    Now I agree that sometimes it is absolutely necessary to solve a “roadblock”, but here again I have a few thoughts.
    First, there’s a lot of neuroscience indicating that our brains work out problems in the background, even when we’re focusing on other stuff. I used to have this experience doing logic, for instance. I’d be staring at a problem for hours, come up with no solution, then move onto something else and…voila, the solution occurred to me! This sort of stuff happens all of the time. Oftentimes, the way to solve a “roadblock” is to not focus on it, make progress on other stuff, and come back. This not only helps solve roadblocks, but (obviously) gets a lot more other stuff done!
    Second, I often find that bouncing back-and-forth between projects can give added perspective on “roadblocks.” Sometimes, the right response to a roadblock really is to give up on it! I had a couple of papers my first years out of grad school that I fumbled away on everyday, never solving the roadblocks that arose. This was a colossal waste of time. Now, if I keep going back to a roadblock and continually find that I can’t solve it, I at least am getting all kinds of other stuff done (rather than getting permanently sidetracked by the roadblock), and often enough, new projects come up that lead me to simply set aside the roadblock project in favor of more promising ideas.
    In short, while I’m sympathetic with your point that sometimes roadblocks are so complex that you have to spend a great deal of time on them, my experience has been that (A) one’s brain can solve a lot of those roadblocks in the subconscious when doing other things, (B) bouncing back-and-forth from roadblock projects to other stuff ensures that you’re not wasting time on roadblocks (time that could be spent checking off other things), and (C) bouncing back and forth can lend added perspective to whether a given roadblock is really worth continuing to waste time on!

  3. Hi Marcus,
    I completely agree on the fact that there is no point in wasting one’s time while feeling stuck and that in this sense your proposal can be very useful, especially for young colleagues who may have not developed their own methodology.
    This being said, I am sorry to say that I still think that there is something missing in your approach. If you go back and forth between projects without having a deadline in view you might at best “happen” to meet the deadline, there is no guarantee that you will do it (unless you have deadlines which are far away and little to do to meet them). I see that you insist that this happens to be the case, but this seems to me like the “invisible hand” of Adam Smith which harmonises the market (e.g., a mystical force we all would like to exist, but which risks to be a wishful thinking).
    Anyway, if we will ever end up co-editing something, I might change my mind (or you yours, who knows?):-)

Leave a Reply to Marcus ArvanCancel reply

Discover more from The Philosophers' Cocoon

Subscribe now to keep reading and get access to the full archive.

Continue reading