The Note-Taking Paradox: More Notes Doesn't Mean Better Learning
You're in a practice session for your Chemistry exam. You've got your notebook ready. The urge is strong: write down everything.
Approach A: Note everything. As you work through a stoichiometry problem, you write down:
- The problem statement (word for word)
- Every intermediate step
- Every single calculation (even ones you immediately recalculate)
- Comments on formulas
- Corrections you made
- Diagrams of what's happening
- Reminders to yourself to check something
You fill 2 pages per problem. By the end, you've written 12 pages of notes for 6 problems. Total time: 45 minutes solving + 30 minutes note-taking = 75 minutes.
Approach B: Strategic note-taking. As you work through the same stoichiometry problems, you write down:
- Only the formula you're using
- The given values (organized in a table)
- The final answer with units
- One sentence about why you chose that approach (if non-obvious)
- One sentence about a mistake you almost made (if applicable)
You fill half a page per problem. By the end, you've written 3 pages of notes for 6 problems. Total time: 45 minutes solving + 5 minutes note-taking = 50 minutes.
Approach A took 75 minutes. Approach B took 50 minutes. Which student learned more?
Research on note-taking effectiveness (Mueller & Oppenheimer, 2014) shows: More notes ≠ more learning. In fact, students who take excessive notes often perform worse because:
- Cognitive load: Writing everything uses mental energy that should go to problem-solving
- False sense of learning: Writing feels like learning (fluency illusion)
- Passive transcription: Writing by rote (copying problem statement) doesn't engage higher-level thinking
- Excess information: Later review is cluttered with irrelevant detail
Students using strategic note-taking—capturing only high-value information—show 20–30% better retention on follow-up assessments compared to "note everything" students.
The key is knowing what to capture and what to ignore.
What to Capture During Practice: The High-Value Notes
Category 1: Given Information (Always Capture)
"Always" information: Any value explicitly given in the problem should be written down.
Why: Externalizing eliminates the need to hold it in working memory.
Example:
Problem: "A 0.50 mol sample of gas expands from 10 L to 25 L at constant temperature. Pressure is 2.0 atm. Calculate work."
Capture:
GIVEN:
n = 0.50 mol
V₁ = 10 L
V₂ = 25 L
P = 2.0 atm
T = constant
Time cost: 30 seconds Benefit: Clear reference for the entire solution; no re-reading the problem
Do not capture: Information you can derive later (e.g., ΔV = 15 L, even though the problem mentions initial/final volumes separately). Deriving it yourself cements the learning.
Category 2: Formulas and Principles (Selective Capture)
Capture if: Using a formula you might forget or confuse with another.
Don't capture if: Using a formula you've internalized (e.g., F = ma for physics students who've used it 100 times).
Example:
Problem type: "Calculate work done by expanding gas"
Capture:
Work formula: W = -P×ΔV (negative for expansion)
(or W = -∫P dV for non-constant pressure)
Time cost: 15 seconds Benefit: Reference during solution; prevents formula confusion
Don't capture: Just copying the formula name. Write the formula itself with the notation.
Category 3: Solution Approach / Why (Capture When Non-Obvious)
Capture if: The approach isn't the obvious one, or you want to remember why you chose this method.
Don't capture if: The approach is standard (e.g., "use dimensional analysis for unit conversions").
Example:
Problem: "Identify the limiting reagent in this reaction."
Capture:
Always convert to moles first (can't compare grams directly).
Then use stoichiometric ratio to see which reagent is limiting.
Time cost: 20 seconds Benefit: Future reference for why this approach works; prevents just copying numbers
Overkill capture (don't do):
I decided to convert to moles. This is because grams of different substances aren't directly comparable. Moles normalize for molar mass differences, allowing true comparison of quantities.
(Too verbose; the principle is already understood)
Category 4: Common Mistakes / Misconceptions (High Priority)
Capture if: You almost made an error, or you've made a similar error before.
Example:
Problem: "Calculate ΔG using ΔG = ΔH - TΔS. T = 25°C."
Capture:
⚠️ MISTAKE CAUGHT: Converted T to Kelvin! (25°C = 298 K)
This is critical—if T in Celsius is used, ΔG will be completely wrong.
Time cost: 15 seconds Benefit: Prevents this error on the real test; builds awareness of the pitfall
Why this is high-value: Capturing mistakes you catch during practice trains you to catch them on the real test. This is worth more than capturing correct solutions.
Category 5: Key Insight or Conceptual Note (Sparingly)
Capture if: You had a realization that changes how you view the topic.
Example:
Problem: Enthalpy, entropy, and free energy problem.
Capture:
KEY INSIGHT: Temperature affects whether a reaction is spontaneous.
- If ΔH < 0 and ΔS > 0, always spontaneous (TΔS term helps)
- If ΔH > 0 and ΔS < 0, never spontaneous (TΔS term hurts)
- If ΔH < 0 and ΔS < 0, spontaneous only at low T (entropy term minimized)
- If ΔH > 0 and ΔS > 0, spontaneous only at high T (entropy term maximized)
Temperature matters when ΔH and ΔS have opposite signs.
Time cost: 45 seconds Benefit: Conceptual anchor for thermodynamics; explains patterns across multiple problems
Don't overdo this: One or two key insights per problem set. Not every problem yields an epiphany.
Category 6: Final Answer (Always Capture)
Capture: The final answer with units clearly labeled.
Example:
ANSWER: W = -3,040 J (or -3.04 kJ)
Time cost: 10 seconds Benefit: Quick reference for verification; easy to track what you've solved
What NOT to Capture (And Why)
❌ Don't Capture: Complete Problem Rewording
Temptation: Writing out the full problem statement word-for-word in your notes.
Reality: The problem statement is already written in your problem set. Rewriting wastes 30 seconds per problem.
Exception: If the problem is given verbally or you won't have access to it later, write a brief paraphrase (not word-for-word).
❌ Don't Capture: Every Intermediate Step
Temptation: Writing down every arithmetic calculation.
50 ÷ 23 = 2.17391...
2.17391 × 1 = 2.17391
2.17391 × 58.5 = 127.17...
127.17 ÷ 2 = 63.59...
Reality: If you're doing arithmetic, you don't need to write down the step. You've already practiced it. Recalculating during review is redundant.
What to write instead:
50 g Na ÷ 23 g/mol = 2.17 mol
(stoichiometry) → 63.5 g NaCl
Time saved: 1–2 minutes per problem
❌ Don't Capture: Corrections You Made During Problem-Solving
Temptation: Writing down mistakes and then the corrections.
Wait, I forgot to balance the equation...no wait, it's 2K + Cl₂ → 2KCl. Hmm, or is it K + Cl₂ → KCl? Let me check. It's 2K + Cl₂ → 2KCl. Yes.
Reality: If you corrected it, you already learned the lesson. Writing it out in full detail doesn't add value; it clutters your notes.
What to write instead:
Balanced equation: 2K + Cl₂ → 2KCl
Time saved: 30 seconds per error caught (and you catch several per practice session)
❌ Don't Capture: Information You're Confident You Know
Temptation: Writing definitions of concepts as a "safety" net.
Stoichiometry: the study of the quantitative relationships between reactants and products in a balanced chemical equation...
Reality: If you already know this, writing it wastes time. If you don't know it well, you should study the textbook definition, not your practice notes.
What to write instead: Just the concept name. The definition lives in your textbook; your job during practice is to apply it.
Time saved: 15 seconds per "safety" definition
❌ Don't Capture: Thinking-Out-Loud Comments
Temptation: Stream-of-consciousness notes about your problem-solving process.
Hmm, this looks like it could be stoichiometry or limiting reagent. Let me think. Actually I bet it's limiting reagent since they give two reactants. Yeah, that makes sense. So I need to find which one is limiting...
Reality: Thinking out loud while practicing is fine. Writing it down clutters your notes with no future value. Your conclusion matters; the thinking process doesn't.
What to write instead:
This is a limiting reagent problem (identify which reactant runs out first).
Time saved: 45 seconds per problem
What Good Notes Look Like: Practical Examples
Example 1: Chemistry Problem (Stoichiometry)
Problem: "Given 50 g of sodium and excess chlorine gas, how many grams of NaCl are produced?"
Good notes:
GIVEN:
- 50 g Na
- Cl₂ in excess
- Reaction: 2Na + Cl₂ → 2NaCl
SOLUTION:
1. Moles Na: 50 g ÷ 23 g/mol = 2.17 mol
2. Stoichiometry: 2 mol Na : 2 mol NaCl (1:1)
→ 2.17 mol NaCl
3. Mass NaCl: 2.17 mol × 58.5 g/mol = 127 g
Hmm, let me double-check this using the other coefficient ratio...
Actually, 2 Na produces 2 NaCl, so 2.17 mol Na → 2.17 mol NaCl. Yes.
ANSWER: 127 g NaCl
⚠️ EASY MISTAKE: Forgetting that Na is 2:2 ratio with NaCl (not 1:1).
Also: Almost used 23 g/mol × 2 = 46 g/mol for Na₂, but problem asks for Na, not Na₂.
Time cost: 10 minutes solving + 3 minutes notes = 13 minutes Key elements: Given values organized, formula shown, answer clear, mistake flagged
Example 2: Biology Problem (Genetics)
Problem: "In a cross between Aa or Bb heterozygotes, what percentage of offspring will have the dominant phenotype for both traits?"
Good notes:
GIVEN:
- Cross: AaBb × AaBb (heterozygous for both)
- Question: P(dominant for both traits)?
APPROACH:
Use independent assortment. Each trait follows separate Mendelian inheritance.
P(dominant A_) = 3/4
P(dominant B_) = 3/4
P(both dominant) = 3/4 × 3/4 = 9/16
ANSWER: 9/16 = 56.25% of offspring
This is the 9:3:3:1 dihybrid ratio. The 9 represents double-dominant.
Time cost: 5 minutes solving + 2 minutes notes = 7 minutes Key elements: Problem restated briefly, approach explained, answer clear, conceptual link (9:3:3:1 ratio) noted
Example 3: Physics Problem (Kinematics)
Problem: "A car accelerates uniformly from rest to 30 m/s in 10 seconds. How far does it travel?"
Good notes:
GIVEN:
v₀ = 0 m/s
v = 30 m/s
t = 10 s
FIND: d
FORMULA:
d = v₀t + ½at² (need to find a first)
OR
d = (v₀ + v)/2 × t (average velocity method)
SOLUTION:
Method 1: Using a
a = (v - v₀) / t = (30 - 0) / 10 = 3 m/s²
d = 0 + ½(3)(10)² = 150 m
Method 2: Using average velocity (verify)
v_avg = (0 + 30)/2 = 15 m/s
d = 15 × 10 = 150 m ✓
ANSWER: 150 m
⚠️ COMMON MISTAKE: Using v² = v₀² + 2ad forREVERSE problem (finding v, not d).
Average velocity method is quickest for this problem type.
Time cost: 8 minutes solving + 4 minutes notes = 12 minutes Key elements: Both methods shown (good for learning flexibility), verification via second method, mistake flagged
The Note-Taking Habit: Building Selectivity
Week 1: Intentional Capture
For one week, consciously think before writing.
Before writing anything, ask:
- "Will I reference this during review?"
- "Is this high-level insight or low-level detail?"
- "Is this already written elsewhere (in my textbook)?"
If the answer to any of these is "no" or unclear, don't write it.
Week 2: Self-Audit
After solving a problem set, review your notes.
Mark each note:
- H (high-value): You'd reference this during review
- M (medium-value): Helpful, but not essential
- L (low-value): Forgotten already, or it's in the textbook anyway
Goal: Achieve 60%+ high-value notes. If less, you're capturing too much. Adjust your selectivity.
Week 3: Speed Test
Time yourself solving with notes vs. without notes.
With strategic notes: 10 problems, 50 minutes (solve + capture) Without notes (just solve): 10 problems, 45 minutes (solve only)
The 5-minute penalty for note-taking is investment in future review. When you review these problems next week, you'll spend 5 minutes grateful your notes were organized. The break-even is immediate.
Week 4+: Automatic Selectivity
By now, you've internalized what's worth notating. Selectivity becomes automatic. You write only what matters, without conscious deliberation.
Strategic Note-Taking for Different Problem Types
Problem Type 1: Calculation-Heavy (Math, Chemistry, Physics)
What to capture:
- Given values (essential for externalizing WM load)
- Formula used (essential to remember which one)
- Final answer with units
What to skip:
- Every arithmetic step (you're solving, not transcribing)
- Explorations that didn't pan out
Time spent note-taking: 15–20% of total problem time
Problem Type 2: Conceptual (Biology, History, Literature)
What to capture:
- Main argument or thesis
- 2–3 supporting points (not all)
- One "why this matters" insight
What to skip:
- Elaboration that reproduces the textbook
- Every detail of complex systems (high-level understanding instead)
Time spent note-taking: 10–15% of total problem time
Problem Type 3: Word Problems (Applied Science, Real-World Contexts)
What to capture:
- Extraction of given numerical values (often hidden in prose)
- The "model" or approach you selected
- Final answer and real-world interpretation
What to skip:
- The full word problem statement (it's in your problem set)
- Every word of your problem-solving dialogue with yourself
Time spent note-taking: 20–25% of total problem time (because problem extraction is time-consuming)
Integration With Scratchpad and Revision Assets
Strategic note-taking during practice feeds into scratchpad organization and later revision asset creation.
Workflow:
-
Practice session: Use strategic note-taking. Capture given values, formula, approach if non-obvious, common mistakes, answer.
-
Scratchpad: Write messily as you solve. These are your working notes. Don't worry about careful handwriting or organization during solving.
-
Post-practice cleanup: Move from scratchpad to organized notes. Use the strategic capture categories to decide what stays and what's archived.
-
Asset creation: Use your organized notes (not the messy scratchpad) to create flashcards, study guides, checklists.
Total time per problem set (10 problems):
- Solving: 40 minutes
- Strategic note-taking during: 8 minutes (integrated)
- Cleanup to organized storage: 5 minutes
- Total: 53 minutes
Payoff: Organized notes ready for asset conversion. Review during exam prep is 40% faster because you're not wading through extraneous detail.
Key Takeaways: Strategic Note-Taking During Practice
-
Taking notes is valuable, but excessive notes backfire — More notes ≠ more learning. Strategic capture is the balance point.
-
High-value notes: given values, key formulas, approach rationale, mistakes caught, final answers.
-
Low-value notes: problem rewording, every arithmetic step, thinking-out-loud, concepts you already know.
-
Notes during practice enable future asset creation — Organized notes become flashcards, guides, and checklists.
-
Strategic note-taking saves time overall — 5 minutes of good notes saves 20+ minutes during review compared to messy notes.
-
The mistake-catching note is highest-value — "I almost made this error" notes prevent those errors on test day.
-
Selectivity becomes automatic within 2–3 weeks — Then note-taking ceases to be a conscious effort.
FAQ: What to Write During Practice
Q: Isn't writing the problem statement helpful for memory?
If you'll see the problem again, no. You've already read it. If instructors verbally give problems, write a brief summary (not word-for-word).
Q: Should I time-box note-taking (e.g., max 2 minutes per problem)?
Not strictly, but if you're spending 5+ minutes on notes per problem, you're over-capturing. Audit what you're writing.
Q: What if I forget something during review because I didn't capture it?
That's the feedback loop. The next time you solve that problem type, you'll know to capture it. Self-correction improves selectivity.
Q: Can I use abbreviations to speed up note-taking?
Yes. Common abbreviations save time. Examples: "⚠️" for mistakes, "✓" for verification, "→" for "therefore." Develop your own shorthand.
Q: Should I review my notes from today within 24 hours?
Yes, but lightly. Quick 5-minute review confirms what you captured was useful. Then leave them alone until you're studying for a test.
The best note-takers aren't the fastest writers. They're the ones asking "Is this worth capturing?" before writing. That question is your filter.