Entries Tagged 'Time Management' ↓

Lifehack: The Importance of a Central Project List

Chris over at Lifehack has a brief article on his morning routine. I’ve found a similar technique to be especially helpful for the day. I try to get up two hours (yep, two hours) before I absolutely have to be anywhere. Half of the time is spent on either exercise or stretching, and the other half on writing out the major goals I have at the different levels followed by the three-five things that I want to get done for the day. Writing it down (in paper at this point, though I’m considering electronic options) helps the sub-conscious reiterate what’s important, and when things pop up, I can ask those important questions:

  • Is this something that is consistent with my goals? (if no, think about how to get out of it; if yes move to the next question)
  • Is this something I need to do now? (if no, then schedule for later; if yes, move to the next question)
  • What on the list has to be rescheduled, and how comfortable am I with that? (unfortunately, this one is not a yes or no–it’s more of a “go-with-the-gut-affair)

Starting the day this way has helped me feel much more in control of the day and my projects; on those days in which I’m too lazy to get up, I feel really disoriented and rushed, regardless of whether I actually have all that much going on for that day. If you can’t come up with two hours, then at least give 30 minutes a try. It’s worth it.

R.A.F.T: Managing Email rather than letting Email Manage You

I’m sure I don’t need to cite statistics to assert that email has become the primary method for work communications. Unfortunately, too many of us have yet to really understand how to work with email yet and the management of email correspondence has become a major source of work in and of itself.

As with most serious components of our work, there is tension from both ends: if we don’t spend enough time filtering email, we miss deadlines and important information that is now being distributed solely through email. However, if we spend too much time messing with email, we end up with too little time to actually get any of the work we need to get done completed. As Aristotle keenly observed, the balance is in the middle.

Enter the R.A.F.T. method. R.A.F.T. is a handy acronym for Read, Act, File, or Trash. Here’s how it works:

  • Read
  • This one’s self-explanatory. Briefly skim through the email and determine whether it’s something that actually requires your attention. You’d be surprised how much doesn’t. If it doesn’t require your attention, Trash it immediately. If it does, move on.

  • Act
  • Does the email require you to do something? If it’s a quick reply, do it, and file the message. If it is something that requires you to do something for the future, but not now, place it on your calendar, or whatever system you use to track suspenses, and file it.

  • File
  • If the message does not require action but needs to be referenced or filed, then File it. I still file messages in one of many different folders, but that’s partially because I manage not only academic stuff but other careers as well. Many productivity gurus are advocating dumping all messages in one big archive and relying on the mature search capabilities now available in most mail apps, but I have yet to make that transition. Do some experimentation to see which is right for you, but, above all, get the stuff out of your inbox.

  • Trash
  • Be merciless on unactionable, unimportant messages and get rid of them immediately.

The goal here is to get your Inbox either empty or so that it contains messages that require some response of you. I’ve experimented with having @Action, @Response, and @Waiting mail folders and noticed that either I spent too much time shifting through them or that I forgot to check them regularly enough. I transitioned to letting actionable items sit in my Inbox, but to get the psychological release, all the stuff in there had to be stuff that required some sort of prolonged action. Despite it being somewhat of a task parking lot, the goal is still to get it to zero.

Of course, the R.A.F.T. method isn’t anything special, and the elements of it are covered in GTD’s processing system. However, “R.A.F.T.” is a nice little mantra to help you through your Inbox. Here are some other quick tips:

  • Don’t check email first thing in the morning
  • Doing so starts your day off responding to external projects and actions rather than advancing internal projects. Do your work first and make other people wait their turn.

  • Turn off the auto-checker in your mail application if you use a computer-based email application.

  • The threat of a notification alone is enough of a psychological distraction and the reaction is much like waiting for a punch that you know is coming. Again, rather than letting other people’s issues distract you, check email only when you’re ready and prepared to karate-chop your way through it. This also allows you to reference your email without having to deal with the inclination to check and read new messages when you should be completing your more important projects.

  • Check email twice a day.
  • Tim’s insight on this is dead-on. I check it about 30 minutes before lunch and about 30 minutes before the end of whatever time I determine I’m done working. Generally, this gives me enough time to respond to short messages, schedule a time to do longer messages and actions, and file messages in their appropriate folder with time left-over.

  • (For Mac users) Use Mail Act-On to decrease drag and drop filing time.
  • When a student writes me, I respond or act, and with this nifty program press “~S” (my tag for “this semester’s student email”) and I’m done. Since I have all of my reference folders short-cutted through Mail Act-On, I don’t have to leave my Inbox to get things filed in their assigned folder. This one program alone probably saves me 10-20 minutes a day.

  • If you get one of those nervous-I-need-an-answer-right-now emails that would give you peace of mind to answer, quickly respond with “Hey, I’ve got your message and am working on an answer. I will get back to you on X day with the information/answer you’ve requested.”
  • This response is generally sufficient to get the offender off of you until the time you’ve indicated. Complete the tasks and projects you’ve decided you’d work on while you’re at your peak. Figure out the answer to those types of emails during some less-productive time prior to the time you said you’d respond and respond then and only then.

The goal is to get email back to the way we accomplish our work rather than email being the work that we do.

The Value of Not Accepting Late Work

I had an amazing thing happen this semester: every student turned in every assignment on time. I don’t think that happened due to the caliber of students or the time I was teaching the course, for those things didn’t make that big of a change in other dimensions of the course. The reason why it happened is that I changed my policy on late work: I simply stated that work not received by the deadline would not be graded and given a “0″ for the assignment.

My wife had started the very same policy a couple of semesters before I had and she found that she significantly decreased the amount of late submissions. Keeping up with students turning things in late, trying to figure out how much to dock their projects, remembering to get those late submissions with the batch of others, etc. proved to be a pain in the arse. That alone proved to be enough of a reason to implement such a policy.


But there are at least two other really good reasons to do this. The first of these deals with the individual student. Having loose late policies actually encourages students to disregard the given deadline for the course. Why? Because, given all of the other hard-deadline items that students have to contend with, it’s more practical to study and/or cram for that Calculus exam that must be taken on Wednesday rather than on that Philosophy (in my case) paper due on that same day but that can be put off. Their efforts in cramming and studying will likely have more impact on their Calculus grade than the negative impact that they’d receive on their paper would have on their grade, depending on the policy.

When I was a TA, I had a professor that had us dock something like a third of a letter grade for every two days late the paper was submitted; weekends counted as one day, as well. Their papers were generally due Friday, and it worked out that they could turn something in on the second Monday after the paper was due and still only have one letter grade docked from their paper. That late submission policy caused me loads of headaches. Given that I tried to have papers graded and turned back out two weeks after they turned them in, it was not at all uncommon for me to be turning back (what I thought was) all of their papers only to have a handful or so trickle in, causing me to either batch them with the next slew of papers, or redo my plan for the week to do those papers. If I chose the former, not only would I have to worry about their grades being consistent with their peers’, but it took me considerably longer, because generally I’d have to reread what we’d covered previously to make sure I understood what the students were saying.

Granted, I could have emailed or caught every student in class who didn’t turn in their papers to see who was turning it in and who wasn’t, but we’re not in high school anymore. My stand on that is that it’s the student’s responsibility to make those arrangements. Furthermore, with roughly eighty students, I wasn’t about to go chasing people down who didn’t turn in their papers, even if I could remember off the top of my head who they were. So, if, while recording scores, I noticed a student didn’t turn in a paper, there was always that lingering question of whether they’d turn it in. Simply put, that’s more brainpower than I want to put on such an issue.

It was commonplace for me to hear students discuss with their peers that they’d just turn their stuff in Monday since they’d probably do better by working on it over the weekend rather than during the week. (Students have a hard time understanding how easily sound travels in classrooms–or they understand all too well and love airing out the lurid details of their escapades for their instructor’s amusement.) What really sold the fact that something was wrong with the policy was when students told me to my face that they turn things in late because the penalty is pretty much non-existent.


The second good reason to impose a hard deadline on students is that doing so prepares them for the real world. There is a creeping concern that higher education is no longer preparing students for entry into the non-academic worlds for which they supposedly go to school to prepare for. Not all business institutions have hard deadlines for policies, I’m sure, but if there is a significant effect for the business if Order X does or does not go in a given day, I don’t see many managers being pleased with their employees if they drop the ball. In such stakes, there is no late submission policy. The students we issue forth, degree in hand, have been trained to turn projects in late, and often rewarded for it. We do them no favor by encouraging this.

The beauty of the policy was the ease of its application. Not a single student asked if they could turn anything late. In those cases where they couldn’t turn it in on the day it was due (student-athletes on tournaments), they took the initiative to turn it in ahead of time. I didn’t have to strong-arm, coddle, or remind people to turn their projects in, and yet, every project was turned in on time. (Note: For this to work properly, make sure you’re explicit about the time it has to be turned in, too.) And, in case you’re worried about such things, it didn’t alter my evaluations–they didn’t make me out to be a bad guy out to get them or anything silly like that. Lastly, the gravity of the deadline made it such that I didn’t even have to give anyone a failing grade. Everything worked out smoothly, exactly the way that it should.

Get rid of those loose late submission policies. Students will adapt accordingly, and the semester will go so much easier for everyone involved.

Teaching Students to Write: Dealing with the Perennial Problem of the Pile of Crap

I’m currently designing my next course and I am faced with a problem that gets me every semester: what’s the best way to teach students how to write well while balancing that objective with many others?

Many people in my department subscribe to the “look-Ma-no-hands” pedagogical principle, which asserts that the best way to learn to write papers is to learn from something you’ve already written, rather than going off of somebody else’s templates. So, we assign papers, have the students write them, and grade fairly charitably the first time around; the idea is that the light hand should alleviate the discomfort that some students feel from having to write papers blind. Having myself done this, I’ve got a few problems with this approach:

  1. Students really feel that this is unfair. “How is it fair that we get graded for something that we don’t know how to do?,” is the graceful, clear way of summarizing the question asked by many of my students.
  2. The light grading tends to skew what students actually would get if you graded the papers for real. It’s sometimes hard to explain to a student why they got a C on their second paper when they followed the same formula that got them an B on the first one. Responding that there was higher expectations on the second paper than the first doesn’t help unless they can see what those expectations are.
  3. Some students are encouraged to turn in the Pile of Crap, since (A) they know they can reasonably argue that their poor grade is unfair and (B) they know that they’ll likely get a passing grade regardless of what they turn in.

Sidebar: A Pile of Crap is a project turned in with the absolute minimum work taken to complete it. What separates the Pile of Crap from the Last Minute Project is that the former is banking on some ambiguity in the assignment or on the student’s ability to complain or wheedle about some aspect of the assignment, whereas the Last Minute Project actually represents the student doing the best she can to complete the assignment and get the best grade possible. An example of a Pile of Crap project is a student turning in a paper that is 2.15 pages long, when the assignment calls for a three page paper, with the student asserting that the paper technically makes it to the third page (after they’ve already found the largest type-face at twelve font and have used reference footnotes to bump the page length). Even though the ploy is as obvious as a forehead-mounted prom pimple, if push came to shove, the student would likely win in an academic dispute. And students also know that you don’t have time to bother with such processes and will likely give them a decent grade not to have to deal with it.


But there’s tension from the other direction, too. If you spend too much time teaching students how to write, you do so at the cost of covering material relevant to whatever course they’re taking. An additional complication is that, frankly, many students just don’t care that their writing is par at best. This is especially problematic if your course is an elective or a course that people have to take to graduate. “Give me the grade, and as long as I pass, I don’t care.” The recognition that the hard work put into trying to teach people to write well will fall flat on many purely degree-seeking ears seems to justify not spending that much time developing our teaching agendas around teaching people to write.

And that’s just the front-side planning. Grading papers thoroughly and providing feedback on papers is time-consuming. Generally, if my students hand in a 4-5 page paper, my comments to them, if I want to be thorough about it, tend to be at least one page (single-spaced). There have been some papers where my comments have had a longer word length than the student’s paper. This is not because I am extremely picky or over-demanding or think I’m a much better writer than they are (which you can see by what you’re reading), but rather, giving constructive criticism and discussing (in writing) ways they may approach their topic differently requires a lot of thought and writing. If I plan on giving thorough comments, I estimate 25 minutes for every paper, and that tends to be pretty close. So, for a class of 30 students, that’s 12.5 hours of grading. I’m fortunate not to be carrying a 4/4 load yet, but, if I were, that’d be 50 hours of just grading to do. Assuming I do three papers (somewhat standard), that’s 150 hours of grading papers, and only papers, spread out over 18 weeks. It’d take eight hours and twenty minutes, on average, per week to complete that much grading, but we all know that papers are feast or famine, coming in at key points in the semester. Again, assuming a 4/4, you can plan on blocking off an entire week (and some change) during critical times in the semester just for grading.

So, here’s the spectrum: On one end, you have doing as little writing preparation and grading work as possible. On the other end, you have spending the time to be completely thorough in preparation and grading. I’ve considered some ways of shooting for the middle:

  1. Assign the first paper, but deceptively not inform the students that it won’t be graded. In reality, it’s a draft or test-run. This satisfies the intuition that learning from what you’ve actually done is the best way to learn, but does so at the cost of you spending the time grading something that won’t be reflected in any grade. Both you and the students have done a lot of work that doesn’t count (at least this time). You also sacrifice a bit of your credibility by going this route, as part of the student-teacher relationship is built on trust.
  2. Ask students who care about their writing to indicate whether they want feedback or not. This ensures that your efforts are well-spent on those students who care and not on those who just want the grade. I can attest from personal experience that two things happens with this approach: (a) no student really wants to admit that they don’t care, thinking it’ll effect your perception of them and hence their grade, and (b) students who get a grade they aren’t happy with then want to talk about it, so you end up looking at the same thing twice.
  3. Assign the first paper, but tell people that it won’t be graded. This cures the anxiety of students and often frees up their thinking (meaning that you actually get some really good papers), but it also leaves plenty of room for the Pile of Crap. In my experience, most students respond only to the impact that assignments will have on their grade, not on the impact it’ll have on their scholarly development; generally, the higher the grade impact, the more work they’ll put into the assignment.
  4. Assign the paper, grade it for real, and give students the option of rewriting the paper and averaging the two grades. This encourages maximum development, lets students who are happy with their grade take it and not work anymore, and thwarts some of the perceived unfairness of the turning something in blind. Perhaps more importantly, though, it also gives students an incentive to not turn in the Pile of Crap, as they know that doing so will hurt their average. However, these benefits come at the cost of your time, since you can anticipate grading at least half of the papers over again.

Option 4 seems to offer the best benefits for the least costs. This time around I’m going with it.

What’s your technique for teaching your students how to write well?

To Work or Not To Work…That is the Question

Some days you wake up knowing that you’re not going to get much done (today was one of those days for me). Popular wisdom would tell you to drink your joe, open up your work, and get to it. In this case, I think popular wisdom is wrong.

Let’s suppose that you’ve got a 20-page project that you’ve got to do. On a strikeout day, you’ll work all day and maybe get 2-3 pages done. Why? Because, dammit, there’s interesting news on Yahoo, you forgot to check your bank account online, a few friends wrote you, it was time to do the weekly vacuuming…in short, Procrastination has worked it’s voodoo on you.

Okay, so you’ve worked the full day, feel happy at the end of it, wake up the next day and look at what you’ve done. The words carry with them the malaise of yesterday, and the process of editing, deleting, and, in general, overhauling what you worked on yesterday saps most of the better part of your Flow time. At the end of day two, you’re all of a page or two further along than you would have been had you just not worked the day prior.

“Charlie, that’s total nonsense! If I were to do that everyday, I’d never get anything done.”

Okay, realistically, odds are you’re not going to do that. Also, realistically, you’ve been denying yourself some down time for quite some time. We all have to refresh our batteries, lest we burnout. Let’s talk about Pareto’s principle in our context.

Pareto’s principle, sometimes called the 80/20 rule, advances (among other things) that 80% of our results come from 20% of our efforts. How is this relevant to your slacking for the day? Consider the inverse of the principle: 80% of our efforts advance 20% of our results. We can probably surmise that your days worth of procrastination and funk-fighting would fall within the latter 80% rather than the former 20%. In short, it’s a lot of squeezing for such little juice.

I’ll give two options for how to spend your strike-out days: (1) do something fun or enjoyable (you remember what that feels like, right), or (2) work away at some routine task that doesn’t require so much brainpower. (1) is good because you recharge your batteries and actually may be better able to work when it’s time, or, even better, you may catch some insight from not thinking about whatever you need to be doing (the “finding-the-remote-when-you’re-not-looking-for-it” syndrome). (2) accepts that not a lot will be accomplished on Project A, but Tasks B, C, and D, if completed, will allow you to more clearly focus on Project A, when you come back to it…and, without the psychic RAM being taken up by those inane tasks, you’re more likely to wind up in the Flow.

“Why do today what you can put off ’til tomorrow?”

Because, either way, you won’t be really doing it today. But what you don’t do today may help you do what you need to tomorrow.

Yet another blog on time management?!

Okay, so there’s a plethora of blogs out there about personal productivity (I personally enjoy 43folders and LifeDev). However, their appeal is either based on programmers, as Merlin’s is, or is too general. I’ve often found myself asking, “How the !@#@! do I translate this good stuff into my academic world?” Generally, by the time I figure it out, I’ve already wasted too much time doing so and am now in Crisis Mode, or have gotten distracted into another form of procrastination.

So, this site is as it’s titled: Life Management for Academics. Why not time management or some such? Time management is a small piece of one’s career in academia. Granted, it may touch other components, but there are other components that are specific to academic life that are not covered by the geniuses at the other time management sites. My suggestion is that academics are different from the general PP (personal productivity) population due to our having to manage the holy Triad: teaching, research/writing, and administrivia (committees, reports, and general paperwork).

There’s also this fact: academics are never done. A paper submitted here needs reworking for presentation there. After that presentation, it needs rework for submission to publication there. If it’s accepted there, then the seeds from it may start another presentation there. Even if it doesn’t start another presentation here, maybe, just maybe, the information you’ve presented will be relevant to another project you’re either working on or will start (better file this away there, mentally, physically, or digitally…just in case). We often accept that we’ll spend our life in project polish hell, but often forget that that’s only the fire; the brimstone comes from project residue.

And here’s the final kicker for why it’s Life Management rather than Time Management: calculate the time and psychic energy required to manage the Triad, and then throw more time and psychic energy onto the fire for keeping up with project polishing and residue. How much time and energy is left? Okay, then start thinking about family, hygiene, subsistence, and sleep. Still have time and energy left? Maybe a little. What if you’d like to do anything fun or to just plain relax and do nothing? Good luck with that one.

Clearly, something has got to give. We can (A) get less to do, (B) complete all that we have to do more efficiently, or (C) quit. Granted, any of the options are up to us, but it’s unlikely that people will take the last option. After all, how long did you spend in school to do what you’re doing? This blog will focus instead on the first two options.

Here’s what you can expect to see on this blog:

  • Commentary on books having to do with time management, creativity, and personal productivity
  • Reviews on software and hardware that may help you manage your life (this will be Mac-Centric), especially software and tips that help with project polishing and residue
  • Posts about developing yourself as a teacher and as a learner
  • Tricks and best practices to help you heal the administrative pains that ail you

If you find any of this useful, please consider donating or visiting one of my sponsors.