- UID
- 599620
- 在线时间
- 小时
- 注册时间
- 2011-1-23
- 最后登录
- 1970-1-1
- 主题
- 帖子
- 性别
- 保密
|
板凳

楼主 |
发表于 2011-4-13 15:42:10
|
只看该作者
For some, maintaining a positive time position comes naturally. However, for most of us, the time pressure is too tight, and the stakes too high, to ignore. So, how does one work out of the red zone and into the green? Collect data, reflect, and transition. (1) KEEP A SINGLE-PROBLEM TIME LOG When practicing GMAT problems, ALWAYS keep track of the time. Try to work within the following time constraints for any individual problem: Quantitative: 2 minutes Sentence Correction: 1 minute 15 seconds Critical Reasoning: 2 minutes Reading Comprehension: 6 min / 3 question passage, 8 min / 4 question passage, etc. Keep a time log that reflects the time spent on EVERY problem. A time log might look like a rough version of this:
Question Type | Benchmark | Time Spent | Time Position | Data Sufficiency | 2 min | 2 min 10 sec | Negative by 10 sec | Sentence Correction | 1 min | 15 sec | 1 min Positive by 15 sec | Reading Comp | 6 min | 5 min 30 sec | Positive by 30 sec | More than anything, this will make you aware of your pacing on a single-problem level, and will force you to consider the time as you work through a practice problem. In addition to highlighting those question types that are costing you time (data sufficiency in this case) and those that are buying you time (sentence correction and reading comp in this case), the time log tears the mask off the scary clock. In other words, once you know how much time you’re spending on a problem, you will be less anxious about it. Less time anxiety means more focus on the content of the question at hand. (2) REFLECT ON THE RESULTSAt this point, a common response from students is, “Okay, I’ve been keeping a time log and I’ve discovered that I am consistently behind on Data Sufficiency problems. I know that I’m working too slowly, but how do I fix that?” This is obviously a great question; awareness is one thing, but increasing speed is another. Speed comes when the problem solving process runs like a finely tuned machine. Have you practiced critical reasoning diagrams enough to make them second nature? Can you sketch a reading comprehension passage in your sleep? Do you immediately consider options for rephrasing, and do you automatically draw a grid, for data sufficiency problems? Do you search for splits and re-splits on sentence correction questions? Speed is all about process. If you find you’re losing too much time on any particular question type, reflect on, and rehearse, the process. Be sure to keep a time log as a measure of progress. (3) TRANSITION TO BENCHMARKS While keeping a single-problem time log will help you become aware of your pacing on all question types, it’s certainly not a practical way to monitor the time during the actual exam. First, checking the clock after each problem on the actual exam is too much of a distraction. Second, to be an effective time manager, you must be flexible. You may be able to complete a slightly easier math problem in fewer than 2 minutes, and you may need slightly more than 2 minutes for the more difficult problems. For these two reasons, it’s much easier to monitor time on the actual exam using these 15 minute benchmarks:
Time Left | Math—Near Question… | Verbal—Near Question… | 75 minutes | 1 | 1 | 60 minutes | 7-8 | 8-10 | 45 minutes | 14-15 | 16-18 | 30 minutes | 21-22 | 24-26 | 15 minutes | 28-29 | 32-34 | Keeping track of the timing for question blocks, as opposed to individual questions, allows for flexibility: less time on the slightly easier questions, more time on the difficult questions. Once you feel comfortable with the single-problem time log, begin to transition to the 15 minute benchmarks. To practice, take a block of 7 or 8 math problems and allot yourself 15 minutes. Are you maintaining a positive time position for an 8 question block? Do the same for a block of verbal questions and monitor your progress. |
|