Reader Academy — Review 201: Recognizing Craft

Track: Reader Academy | Level: Intermediate | Estimated time: ~20 minutes Prerequisite: Review 101: Constructive Feedback | Badge unlock: Craft-Aware Reader Quiz: 5 questions with example passages — identify craft elements, spot issues, and explain your reasoning.

Introduction: From "I Liked It" to "Here's Why It Works"

In Review 101, you learned how to give feedback that's specific, constructive, and respectful. You learned the "I Felt" method and the sandwich technique. You can write a review that makes a writer feel seen.

Now it's time to level up.

This module teaches you to see the machinery. Every story that grips you, every chapter that makes you lose track of time, every line that stays in your head for days — those aren't accidents. They're craft choices. And once you learn to recognize them, you become a reader who can tell a writer not just what you felt, but why you felt it.

That's the difference between a good reviewer and a great one.

You don't need to be a writer to do this. You don't need to know the technical terms (though we'll teach you a few). You just need to learn where to look.

Pacing: The Story's Heartbeat

Pacing is how fast or slow a story moves — not in word count, but in felt time. A 10,000-word chapter can feel like a sprint. A 2,000-word chapter can feel like it takes forever. Pacing is about the reader's experience of time passing.

How Writers Speed Up

When a writer wants you to feel urgency, chaos, or momentum, they:

Use short sentences. Short sentences are fast. They hit. They move. The reader's eye flies down the page.

The door slammed. Kael ran. Behind him, footsteps — too many, too fast. He turned a corner. Dead end. He turned back. They were already there.

Use short paragraphs. White space on the page creates speed. One-line paragraphs push the reader forward.

Compress time. Instead of showing every moment, they skip:

Three days. That's how long it took for everything to fall apart.

Cut description. In fast scenes, the world shrinks. You don't notice the wallpaper when someone's chasing you.

How Writers Slow Down

When a writer wants you to feel tension, dread, beauty, or weight, they:

Use longer sentences. Sentences that breathe, that wander, that let the reader settle into the moment the way you settle into a chair at the end of a long day — those sentences create a sense of stillness.

Linger on sensory detail:

The candle had burned down to a stub, and the wax had pooled on the table in a shape that looked almost deliberate, like a small, frozen lake. Voss stared at it. He'd been staring at it for a while. He wasn't sure how long. Time had gone soft at the edges.

Expand small moments. A single glance, a pause in conversation, a hand reaching for a doorknob — when a writer gives a small moment a full paragraph, they're telling you: this matters. Pay attention.

Use internal monologue. Entering a character's thoughts naturally slows the scene, because thinking is slower than doing.

How to Spot Pacing in a Review

When you're reading, notice when you:

• Speed up — you're skimming, your heart rate is up, you want to know what happens next
• Slow down — you're savoring, rereading a line, sitting in a moment
• Get impatient — the scene feels slower than it should (pacing problem)
• Feel lost — the scene moved so fast you missed something (pacing problem)

In your review, you can say:

"The pacing in the chase sequence was perfect — I was reading so fast I almost missed the twist, which I think was intentional. It made me go back and reread, which was even better the second time."

"I felt the middle section slow down more than I think was intended. The descriptions of the market were beautiful, but by the third paragraph of stall descriptions, I'd lost the sense of urgency from the fight scene before it."

Point of View: Whose Eyes Are We Behind?

Point of view (POV) is who the reader experiences the story through. It's one of the most fundamental craft choices, and when it's done well, you barely notice it. When it breaks, it's disorienting.

The Common POVs in Fanfiction

First person: "I walked into the room and immediately wished I hadn't."

• You're inside one character's head. You only know what they know.

Third person limited: "Sera walked into the room and immediately wished she hadn't."

• You're behind one character's eyes. You see the world through their filter, but in third person.

Third person omniscient: "Sera walked into the room, unaware that behind the curtain, Kael was holding his breath."

• The narrator knows everything. They can show you anyone's thoughts.

Second person: "You walk into the room. You immediately wish you hadn't."

• Common in reader-insert fic. "You" are the character.

Head-Hopping: The Most Common POV Mistake

Head-hopping is when the POV switches between characters within a single scene without a clear break. It's jarring because the reader suddenly loses their anchor.

Example of head-hopping:

Maren stared across the table, trying to read his expression. She couldn't tell if he was angry or just tired.

Dex wished she'd stop looking at him like that. It made him feel like an insect under glass.

She took a sip of her coffee. It was too hot, but she drank it anyway because it gave her something to do.

He noticed the way her hand shook on the cup and felt a pang of guilt he didn't want to examine.

Did you feel the whiplash? One moment we're in Maren's head (she couldn't tell what he was feeling — that's her limited perspective). Then suddenly we're in Dex's head (he wished she'd stop). Then back to Maren. Then Dex again.

The reader is bouncing between two skulls like a ping-pong ball. Each jump costs a tiny bit of immersion.

How to fix it (as a reviewer, suggest):

Option 1: Pick one POV and stay there for the entire scene.

Option 2: Use a scene break (a blank line or ---) to signal the switch. The reader's brain resets at a break.

In your review:

"I noticed the POV shifts between Maren and Dex in the kitchen scene. We're in Maren's head at the start — she can't read his expression — but then we suddenly know what Dex is thinking. I'd love this scene from just Maren's perspective, because not knowing what Dex feels would actually increase the tension."

Notice: that's not "you did head-hopping." It's a specific observation, with a reason, and a suggestion that shows you understand the writer's intent.

Intentional POV Shifts

Not every POV shift is a mistake. Some writers deliberately use omniscient narration, or shift between characters with clear breaks. The question isn't "did the POV change?" but "did it change on purpose and for a reason?"

If the shift adds something — irony, dramatic tension, a wider view — it's working. If it feels like the writer accidentally slipped into another character's thoughts, that's head-hopping.

Showing vs. Telling: Spotting It in Practice

You learned about showing and telling in the Writer track (or you've absorbed it from reading). Now let's learn to recognize it as a reviewer — because spotting it in other people's work is how you develop the eye for it in your own.

What Showing Looks Like in the Wild

When a writer shows, you feel things without being told to feel them:

Ilara's hands were steady when she poured the tea. Perfectly, deliberately steady — the kind of steady that takes more effort than shaking would.

The writer never says "Ilara was suppressing her emotions" or "Ilara was pretending to be calm." But you know. The detail about her steadiness being effortful tells you everything. That's showing at work.

What Telling Looks Like in the Wild

When a writer tells, they label the experience for you:

Ilara was nervous but trying to hide it. She poured the tea carefully.

You receive the information, but you don't feel it. The writer did the work for you, and in doing so, gave you less.

The Double Dip (Show + Tell)

This is the most common craft issue you'll encounter, and it's worth flagging in reviews:

Dex's jaw clenched. His knuckles went white on the edge of the table. He was furious.

The first two sentences show. The third tells. The telling sentence actually undercuts the showing — it says to the reader, "In case you didn't get it from the vivid physical details, let me spell it out." Trust the reader less, achieve less immersion.

In your review:

"You did such a strong job showing Dex's anger through his body language — the clenched jaw and white knuckles told me everything. The sentence 'He was furious' afterward actually took me out of the moment because I'd already felt it. You could cut that last line and the scene would be stronger."

This is the gold standard of craft feedback: you're not criticizing. You're showing the writer that their instincts are good (the showing was effective) and that they can trust themselves more.

Dialogue Craft Markers

In Review 101, you learned to comment on what worked. Now let's identify specific things to look for in dialogue.

Subtext

Subtext is when characters mean something different from what they say. Great dialogue vibrates with it.

"You look tired," Sera said.

"Thanks."

"I mean — when did you last sleep?"

"Is that what you came here to ask?"

On the surface: a question about sleep. Underneath: I'm worried about you. I still care. Why won't you let me in?

When you spot subtext, name it in your review:

"The exchange about sleep was doing so much more than it seemed — I could feel Sera's worry and Dex's deflection underneath the actual words. That's exactly the kind of dialogue that makes me reread a scene."

Voice Distinction

Can you tell which character is speaking without looking at the tags? If yes, the writer has voice distinction. If every character sounds the same, that's worth noting.

"This is a catastrophically terrible idea." (formal vocabulary, dramatic emphasis — this sounds like one specific character)

"Yep. We doing it?" (casual, short, direct — clearly someone else)

Information Dumps in Dialogue

When characters explain things to each other that they would both already know, that's a craft issue:

"As you know, Kael, we've been partners for seven years, ever since the incident at the Northern Gate."

No one talks like this. Kael already knows. The writer is using dialogue as a shortcut to deliver backstory to the reader.

Tension and Stakes: Recognizing What Keeps You Reading

Tension is the feeling that something is about to happen — or about to go wrong. Stakes are what will be lost if it does. Together, they're the engine that keeps a reader turning pages.

How to Spot Tension

Tension exists whenever there's a gap between what a character wants and what's happening. It shows up as:

• Unanswered questions — the reader knows something the character doesn't (or vice versa)
• Ticking clocks — a deadline, a countdown, a limited window
• Conflicting desires — a character wants two things that can't both happen
• Unspoken truths — the reader can feel what's not being said

The Difference Between "I Didn't Like This" and "This Didn't Work"

This is perhaps the most important distinction in this entire module.

"I didn't like this" is a preference. It's about you.

"This craft choice didn't work because..." is an observation. It's about the text.

The difference matters because writers can't do anything with your preferences, but they can absolutely do something with craft observations.

The left column shuts conversations down. The right column opens them up.

Quiz: Test Your Craft Eye

Read each passage and answer the question. Take your time — this isn't about speed.

Question 1: Pacing

The forest had a weight to it. Not physical — atmospheric. The kind of weight that pressed against Kael's eardrums and made him hyper-aware of each branch that cracked under his boots. Each crack felt intentional, like the forest was keeping track.

He stopped.

Listened.

Nothing.

Which was worse.

What pacing technique is the writer using in the last four lines?

• A) Time compression — summarizing a longer period into a short passage
• B) Deceleration through fragmentation — breaking sentences into single beats to slow the reader and create suspense
• C) Acceleration through short sentences — speeding the reader up to create urgency
• D) Internal monologue — slowing the scene by entering the character's thoughts

Correct answer: B. The fragments ("Stopped." "Listened." "Nothing.") create a near-freeze-frame effect. Each line forces the reader to pause, mimicking Kael's own stillness and alertness. The final line — "Which was worse" — lands like a held breath. This is deceleration, not acceleration. Short sentences can do both; here, the isolation and the white space between them create tension through slowness, not speed.

Question 2: Head-Hopping

Maren sat across from him, trying to figure out the right words. Everything she'd rehearsed in the car felt wrong now.

Voss watched her struggle and felt something complicated — pity, maybe, or the specific ache of watching someone try to repair something that was already broken.

She opened her mouth. Closed it. Tried again.

"I'm sorry," she said.

He'd waited eleven months to hear those words, and now that they were here, they felt like a coat that didn't fit anymore.

Is there head-hopping in this passage? If so, where?

• A) No — this is consistent third-person omniscient narration
• B) Yes — the passage starts in Maren's limited POV (she's figuring out words, her rehearsal) and shifts to Voss's POV (he watched, he felt pity, his internal metaphor about the coat)
• C) No — it's Voss's POV throughout, and he's observing Maren externally
• D) Yes — but only in the final paragraph

Correct answer: B. The passage opens firmly in Maren's head — "trying to figure out the right words" and "everything she'd rehearsed" are her internal experience. Then it shifts to Voss — "felt something complicated" and the coat metaphor are his inner world. This is a head-hop. A reviewer might suggest either committing to one POV for the full scene, or adding a scene break between Maren's section and Voss's.

Question 3: Showing vs. Telling

Which version is stronger, and why?

Version A:

Dex was clearly uncomfortable at the party. He didn't like large groups and wanted to leave.

Version B:

Dex stood near the door — not blocking it, but aware of it. He held his drink with both hands, like a shield he hadn't decided to lower yet. When someone laughed too loud two tables over, his shoulders went up a fraction of an inch and stayed there.

• A) Version A — it's more efficient and gets the point across faster
• B) Version B — the physical details let the reader experience Dex's discomfort rather than being told about it
• C) Both are equally effective, just different styles
• D) Version B — but it's over-showing; a mix of both would be better

Correct answer: B. Version A is telling: "uncomfortable," "didn't like," "wanted to leave" are all labels. Version B never uses any of those words, but the reader feels the discomfort through specific, grounded details — the positioning near the door, the drink held like a shield, the shoulders rising at loud noise. The details are doing the emotional work. This is showing at its most effective.

Question 4: Dialogue Craft

"I brought you soup," Ilara said.

"I'm not hungry."

"I didn't ask if you were hungry."

Silence. Then: "You don't have to do this."

"I know."

She set the bowl on the nightstand. He didn't touch it. She didn't leave.

What craft element is most at work in this passage?

• A) Worldbuilding — the details establish the setting
• B) Subtext — the conversation is about care and resistance, not soup
• C) Pacing — the short lines create a fast rhythm
• D) Voice distinction — each character has a unique speech pattern

Correct answer: B. The soup is a vehicle. Ilara bringing it means: I'm here. I'm not leaving. You matter. His refusal means: I don't deserve care. Don't get close. Her "I didn't ask" means: I don't need your permission to love you. None of this is stated — it's all subtext, carried by what's not said as much as what is. The final two sentences ("He didn't touch it. She didn't leave.") are the emotional resolution: she stays anyway. That's the whole story in six words.

Question 5: Craft Observation vs. Personal Preference

A story you're reviewing features a slow-burn romance that takes 8 chapters to reach the first kiss. You prefer faster-paced romance. Which review comment is a craft observation rather than a personal preference?

• A) "This slow burn is way too slow. Just get them together already."
• B) "I prefer romances where the couple gets together earlier — 8 chapters felt like too many for me."
• C) "The slow burn works well through chapter 5, where each interaction adds a new layer of tension. But chapters 6 and 7 felt like they repeated the same almost-moment without escalating the stakes, which made the eventual first kiss feel slightly less earned than the buildup promised."
• D) "I skipped to the kiss. Life's too short."

Correct answer: C. Option A is a demand. Option B is an honest preference, but doesn't give the writer actionable craft feedback. Option D is funny but useless. Option C does three things right: it acknowledges what's working (chapters 1-5 build effectively), identifies a specific issue (chapters 6-7 repeat rather than escalate), and explains the consequence (the payoff feels less earned). The writer can work with that.

Badge Unlock: Craft-Aware Reader

You've completed Review 201: Recognizing Craft.

You now understand:

• Pacing — how writers control the reader's sense of time through sentence length, paragraph structure, and detail density
• Point of view — how to identify the POV, spot head-hopping, and distinguish mistakes from intentional choices
• Showing vs. telling — how to recognize it in practice, including the double dip
• Dialogue craft — subtext, voice distinction, and information dumps
• Tension and stakes — what keeps readers reading, and how to articulate it
• The crucial difference between "I didn't like this" and "this craft choice didn't work because..."

Your badge: Craft-Aware Reader

This badge unlocks:

• Review 301: Genre-Aware Reviews (next module)
• Access to the "Craft Spotlight" review template — a structured format for craft-focused feedback
• The ability to mark your reviews as "Craft Review" (a signal to writers that your feedback engages with technique)

You're no longer just reading stories. You're reading how stories are built. That's a different skill entirely — and it makes your feedback genuinely valuable to any writer who receives it.

Next up: Review 301 — Genre-Aware Reviews (learn to review romance, angst, dark fic, and explicit content on their own terms)