If you look past the big-”c” Conclusions of this study, you’ll find a tactical gem buried in the narrative — a piece of study advice I’ve been promoting for years: the best guide for how to study for a class is the first exam.
Think about this for a moment. The first exam reveals the exact relationship between the material presented in class and the type of questions that you’ll be asked to answer about it. After your get your first exam back, you have, in essence, been granted the Rosetta Stone for your class. You now know exactly how to study for the exams that follow.
The details work as follows…
The Post-Exam Post-Mortem
After you get back your first exam, set aside 15 or 20 minutes to soak up its lessons and adjust your habits accordingly. Begin by asking yourself the following questions:
1. What did I do right? What note-taking and study strategies served you well on the exam?
2. What was a waste of time? Which strategies took up time but did not help?
3. What did I miss? Where were you caught off guard? What type of question were you not prepared for? What type of material did you miss in your review?
Next, lay out, in detail, the rules for the study system that you’ll follow for the remainder of the semester. Make sure this system includes the tactics you listed in your answer to (1) and excludes the tactics mentioned in your answer to (2). (This sounds obvious, but many students get so comfortable with certain study rituals that they have a hard time abandoning them, even after they’ve identified them as not helping.)
Most important, think hard about your answer for (3). Then ask yourself what’s the most efficient habit you could add to your study arsenal that would fill in those gaps. Add this to your system.
Case Study: MIT Kicks Me in the Ass…Then I Kick Back
In an old Monday Master Class article, originally posted in July, I walk through the tale of a post-exam post-mortem that saved my ass here at MIT. Here’s the bullet-point summary (see the original post for more detail):
* I studied hard for a course in distributed system design. The course relied on academic papers, several per week, that we reviewed in class. I used quiz-and-recall to make sure I knew the main structure, pros, and cons, of each of the systems studied.
* Then the test came. I froze on the first question. It was asking for nitty-gritty details; i.e., what would happen to this performance plot if 5% of the processors failed? My high-level quiz-and-recall questions had not prepared me for these down in the dirt detailed prompts. The clock was ticking…
* I didn’t know how to answer these questions. So I did poorly. Afterwards, it took me about an hour of pacing to wear off the negative energy of the experience. Later that same day, I sat down and began to tweak my study system. I asked myself what went wrong. And then looked for answers.
* By the end of the day, I had a new strategy. For the remainder of the semester, I would focus on the tables and graphs included in the papers we reviewed. If I could do a quiz-and-recall lecture on each of these figures — explaining what it showed and why — then I should understand the correct level of detail for the subsequent exams. Better yet, this system was efficient. These figures, it turns out, capture all the salient details of the paper. They provided natural, targeted questions for learning the right level of material.
It turned out that I wasn’t the only student to do poorly on that first exam. Most of them, however, did not adjust their study habits for the final, and ended up doing poorly there as well. In comparison, my strong final grade, plus strong problem set performance, earned me an “A.”
Trust Your Conclusions
A good percentage of the e-mails I get from students are instigated by a bad exam. They are worried that they are in danger of taking a turn for the worse academically. I love these e-mails. Having completed one exam makes the polishing of your study system easy. It’s hard to guess how to best study at the beginning of a class. But once you have some feedback you can get specific.
Let your first exam guide you. Learn its lessons, and those that follow will go much more smoothly. And if you can, avoid taking the grad-level distributed system design course at MIT. It’s tough.
Saturday, February 6, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment