Weak vs. Strong Feedback: Examples From Grading McCandless Journal Analysis
Published on September 23rd, 2026 by the GraideMind team
Feedback on essays analyzing McCandless's journal entries often falls into a predictable trap: comments that are technically accurate but too vague to actually guide revision. A comment like "good use of evidence" tells a student nothing about what made the evidence good or how to replicate that success in a future paragraph, while a comment like "needs more analysis" leaves the student guessing at what kind of analysis is missing. Comparing weak and strong versions of the same feedback side by side makes the difference concrete, and it is a useful exercise for teachers refining their own grading habits, not just for training new graders.

Consider a student paragraph that quotes McCandless's journal entry describing his arrival in Alaska as the start of a "great adventure" and then simply moves on to the next point without further comment. A weak version of feedback here might say "nice quote, but explain more," which identifies that something is missing without specifying what. A strong version of the same feedback would name the specific gap: "You've shown us what McCandless wrote, but not what this specific word choice, great adventure, reveals about his mindset before entering the wilderness, or how it contrasts with his later, more desperate entries." This second version gives the student an actual direction for revision.
The difference between these two comments is not length alone, since a long but still vague comment provides no more direction than a short vague one. What matters is specificity tied to the actual text the student wrote, referencing their exact word choice or their exact quote, rather than offering feedback generic enough to apply to almost any essay on almost any topic. Teachers grading a large stack of essays under time pressure often default to the shorter, vaguer version simply because it is faster to write, which is precisely where an efficient grading workflow can free up time for the more valuable, specific comment instead.
More Side-by-Side Examples
Another common scenario involves a student who cites McCandless's journal to argue he was fully confident and prepared throughout his time in Alaska, without acknowledging the entries that reveal growing desperation later on. Weak feedback here might simply say "consider other evidence too," which again fails to specify what evidence or why it matters. Strong feedback would name the specific gap directly: "Your argument only draws on entries from McCandless's first weeks. Looking at entries from later in his stay, where his tone shifts noticeably, would complicate your claim about his confidence and likely make your argument more persuasive, not less."
- Weak: "Good evidence." Strong: names the specific word choice and what it reveals
- Weak: "Needs more analysis." Strong: specifies which claim lacks support and why
- Weak: "Consider other evidence." Strong: names the specific missing entries and their relevance
- Weak: "Unclear thesis." Strong: identifies whether the issue is scope, arguability, or specificity
- Weak: "Good job." Strong: names the specific skill the student demonstrated well
Feedback a student cannot act on is not actually feedback, it is just a grade with extra steps.
Stop spending your evenings grading essays
Let AI generate rubric-based feedback instantly, so you can focus on teaching instead.
Try it free in secondsWhy Specificity Matters More for This Book
Into the Wild presents a particular feedback challenge because McCandless's journal is genuinely ambiguous and fragmentary, which means students often reach for the most dramatic or memorable entries rather than the ones that most precisely support their argument. Vague feedback in this context tends to reinforce the habit of picking evidence for its emotional impact rather than its analytical precision, since a comment like "strong quote" praises the choice without evaluating whether it was actually the most relevant option available. Specific feedback that names why a particular entry does or does not fit the argument being made teaches students to evaluate their own evidence more critically in future essays.
This specificity also matters because McCandless's journal entries are often short and cryptic, sometimes just a few words per day, which means the interpretive work a student does connecting that fragment to a larger claim is where the real analytical skill lives. Feedback that engages with the specific interpretive leap a student made, rather than just the surface-level fact that a quote was included, addresses the actual skill being developed in this kind of assignment and gives students a much clearer sense of how to strengthen similar interpretive leaps in future writing.
Building a Personal Feedback Bank
Teachers who grade this same assignment year after year benefit from keeping a running bank of strong, specific feedback phrases tied to common student patterns, which can then be adapted quickly rather than rewritten from scratch for every essay. This does not mean copying identical comments onto every paper, since that would recreate the same vagueness problem at a larger scale, but rather having a set of well-tested specific feedback templates that can be tailored to each individual student's actual writing with only minor adjustment.
Reviewing this feedback bank periodically, and retiring comments that students consistently seem to misunderstand or ignore in their revisions, keeps the bank genuinely useful rather than becoming a static list that no longer reflects what actually helps students improve. Some teachers find it useful to track, informally, which specific feedback phrasings correlate with meaningful improvement in a student's next draft, refining their approach over time based on what demonstrably works rather than just what feels thorough to write.
Balancing Specificity With Grading Time
The obvious tension in all of this is that specific, individualized feedback takes considerably more time to write than generic comments, which is a real constraint for any teacher grading a large stack of essays on a tight turnaround. One practical compromise is reserving the most detailed, specific feedback for the paragraphs where a student's argument is closest to working but not quite there, since this is where targeted feedback produces the biggest improvement, while spending less time on paragraphs that are either already strong or so fundamentally underdeveloped that a brief redirection matters more than granular detail.
Tools that can handle some of the more mechanical first-pass feedback, flagging where a claim lacks textual support or where organization breaks down, free up a teacher's limited time for exactly this kind of high-value, specific commentary on the paragraphs that need it most. The goal is never to eliminate the human judgment involved in evaluating interpretive sophistication, but rather to ensure that judgment gets applied where it matters most instead of being spread too thin across mechanical issues that could be caught more efficiently.
See how fast your grading workflow can be
Most teachers go from hours per batch to minutes.
Create free account