Introduction
In our last lesson, we built a diagnostic procedure for identifying scenes that serve no purpose—the narrative equivalent of "dead code." We established that every scene must either advance the plot or develop character to justify its existence.
Today, we move from structural necessity to functional performance. A scene can have a clear purpose but still fail in its execution, creating a negative experience for the reader. Your learning outcome is to distinguish between reader confusion (a clarity issue), boredom (a stakes issue), and disbelief (a logic issue).
Think of this as moving from architectural review to system debugging. The previous lesson asked, "Is this component necessary for the machine?" This lesson asks, "Is this necessary component working correctly, or is it buggy?" When a reader reports that a scene "doesn't work," they are giving you a high-level error message. Your job, as the story's engineer, is to diagnose the specific fault.
1. The Diagnostic Mindset: Symptoms vs. Root Causes
When a beta reader says, "I didn't feel attached to the lead character," or "The ending of that chapter felt flat," they are describing a symptom. This feedback is valid but not actionable. It's like a user telling a programmer, "The app feels slow." It identifies a problem but doesn't locate the cause.
A professional diagnostic process drills down from the symptom to the root cause. This is the core principle behind the Story Grid methodology, which aims to make editing a technical, analytical process.
To understand the difference between vague feedback and a true diagnosis, let's explore the philosophy behind the Story Grid's analytical approach. This reading frames editing not as an art but as a technical process of deconstruction and problem-solving.
Read the sections that start with 'What you’re doing with the spreadsheet is deconstructing the building,' 'Let me take it back to what I did when I was at the major publishing houses,' and 'I also want to go back to as an editor...'. Focus on Shawn Coyne's analogy of opening up the walls of a house to see the wiring and his argument for replacing vague notes like 'I didn’t find that the third act paid off' with specific, mechanical fixes.
The key takeaway is that our goal is to translate subjective reader feelings into objective, fixable problems within the text. The three primary "error codes" we will be looking for are Confusion, Boredom, and Disbelief.
2. Error Code #1: Confusion (A Clarity Issue)
Definition: Confusion occurs when the reader's mental model of the story breaks. They don't understand what is happening, why it's happening, or what its significance is. The narrative signal is lost in noise.
Common Causes:
- Unclear Character Goals: The reader doesn't know what the POV character wants in the scene.
- Information Overload: The scene tries to do too many jobs at once (e.g., world-build, introduce a character, advance the plot, and deliver backstory simultaneously). The reader's cognitive load is exceeded.
- Broken Causal Chains: Event B happens after Event A, but the reader can't see the logical link between them.
- Ambiguous Language: "Clunky" sentences or vague descriptions obscure the action.
- Misdirection: The scene emphasizes details that turn out to be irrelevant, splintering the reader's focus.
The following video provides an excellent example of how trying to do too much in one paragraph can lead directly to confusion and, subsequently, boredom.
I Rewrote 50 Slow Chapters — Here's How to Fix a Boring Scene Without Cutting It
In his video on fixing boring scenes, Patrick Walsh identifies the 'Hidden Load Problem' as a key culprit. This is a primary source of reader confusion.
Watch from 00:48 to 03:10. Notice how the initial example paragraph collapses under the weight of doing five jobs at once. The fix is to give the scene one primary job, which provides clarity and focus.
Diagnostic Test for Confusion: Pause after reading a scene and ask:
- What did the POV character want at the start of this scene?
- What did they do to try and get it?
- What happened as a result?
If you cannot answer these three questions clearly and concisely, you have a clarity problem.
3. Error Code #2: Boredom (A Stakes Issue)
Definition: Boredom occurs when the reader understands what is happening but has no emotional investment in the outcome. The events lack tension, consequence, or emotional charge.
As a writer, your own emotional response during revision can be a powerful diagnostic tool. Acclaimed author Mary Robinette Kowal offers a useful insight.
A Chat W/ Mary Robinette Kowal!
In this interview, Mary Robinette Kowal explains how to interpret your own feelings during the writing process as diagnostic signals for reader experience.
Watch from 00:22:56 to 00:25:24. Pay close attention to her classification of writer's block. She states that if you find yourself getting drowsy while writing, you are probably boring yourself—and therefore, the reader.
Common Causes:
- Neutral or Repetitive Complications: The obstacles the character faces don't actually raise the stakes or they repeat the same challenge without escalation.
- Passive Protagonist: The plot happens to the character, rather than being driven by the character's choices and actions.
- Stakes are Abstract or Missing: The consequences of failure are not clear, tangible, or emotionally resonant.
- Predictable Polarity Shifts: As discussed in the Story Grid resource, if a section begins with a positive charge and ends with a positive charge, the lack of reversal feels unsurprising and flat.
The following resource provides a systematic breakdown of how progressive complications can fail, leading directly to reader boredom.
Where Progressive Complications Go WRONG
Alice Sudlow's article on progressive complications provides a checklist of traps that drain narrative momentum. Several of these are direct causes of boredom.
Read the sections for Trap #1 ('The progressive complications are neutral'), Trap #2 ('The progressive complications repeat the same conflict'), and Trap #5 ('The protagonist lacks agency'). Notice how the 'Reader Impact' for each of these is explicitly identified as boredom.
Diagnostic Test for Boredom: After reading a scene, ask: "What was at risk for the character in this scene, and why does it matter?" If the answer is "nothing," "I'm not sure," or something abstract and distant, you have a stakes problem.
4. Error Code #3: Disbelief (A Logic Issue)
Definition: Disbelief occurs when the reader understands the event and its stakes but finds it implausible within the established rules of the story. It shatters the internal consistency of the narrative world, breaking the "reality" you've created.
Once again, your writer's intuition is a key diagnostic tool.
A Chat W/ Mary Robinette Kowal!
Let's return to Mary Robinette Kowal's diagnostic framework. She has a specific indicator for when you, the writer, don't believe your own scene.
Watch the same clip again from 00:22:56 to 00:25:24, but this time focus on what she says about rewriting the same sentence over and over. She identifies this as an indicator that you don't believe the moment. If the author doesn't believe it, the reader certainly won't.
Common Causes:
- Character Inconsistency: A character acts in a way that contradicts their established values, fears, or capabilities without sufficient motivation. (This links back to our previous lesson on character consistency).
- Contrived Coincidences (Deus Ex Machina): An unsolvable problem is suddenly resolved by a convenient, un-setup event.
- Violated World Rules: The "physics" of your world (e.g., how magic works, technological limitations) are broken for the convenience of the plot.
- Unearned Outcomes: A character achieves a goal without a plausible struggle, or a relationship changes state (e.g., from hate to love) without a convincing process.
The article on progressive complications also directly addresses the most common cause of reader disbelief: coincidence.
Where Progressive Complications Go WRONG
Alice Sudlow's article also contains a precise analysis of how coincidences, when used improperly, can destroy a reader's trust in the story.
Now, read Trap #4 ('The progressive complications are too coincidental'). Pay attention to the distinction between believable coincidences that create problems (like in Pride and Prejudice) and unbelievable ones that conveniently solve them.
Diagnostic Test for Disbelief: After reading a scene, ask: "Given everything I know about this character and this world, is this event a probable or at least possible consequence of the preceding events?" If it feels like an authorial hand reached in to make something happen, you have a logic problem.
Test your understanding!
You are editing a sci-fi thriller. Analyze the following scene summary and diagnose the primary reader experience issue: Confusion, Boredom, or Disbelief? Justify your diagnosis by referencing one of the common causes.
Scene: Captain Eva Rostova, a hardened cynic who trusts no one, is trapped in a sealed maintenance corridor on a failing starship. The door's electronic lock is fried. An unstoppable killer android is punching its way through the far wall. With only seconds to spare, Eva closes her eyes, concentrates, and suddenly manifests a telekinetic blast that rips the door from its hinges, allowing her to escape. This is the first and only time telekinesis has been mentioned or used in the story.
Show answer
The primary issue is Disbelief.
Justification: The root cause is a Contrived Coincidence combined with a Violation of World Rules. The solution to Eva's problem (telekenisis) appears out of nowhere, with no prior setup. It breaks the established "physics" of the story world for the sole purpose of saving the character. It feels like the author needed an escape and just invented one on the spot, rather than having Eva use her established skills (e.g., her cynical intellect or technical knowledge) to find a clever, plausible solution. This shatters the reader's suspension of disbelief.
Conclusion
You now have a diagnostic framework to move beyond the vague feeling that a scene "doesn't work." By categorizing the problem into one of three distinct "error codes," you can perform targeted, effective revisions.
Key Takeaways:
- Negative reader feedback is a symptom, not a diagnosis. Your job is to trace the symptom to its root cause.
- Confusion is a clarity issue. The reader doesn't understand what's happening or why. Fix it by clarifying goals, simplifying information, and strengthening causal links.
- Boredom is a stakes issue. The reader understands but doesn't care. Fix it by increasing stakes, ensuring character agency, and escalating conflict.
- Disbelief is a logic issue. The reader understands and cares but finds the events implausible. Fix it by ensuring character consistency, setting up solutions, and adhering to your world's rules.
Preview of the Next Lesson
We have now examined scene-level diagnostics from both a structural and a psychological perspective. Next, we will zoom in further to one of the most critical components of any scene: dialogue. Weak dialogue can be a source of confusion, boredom, and disbelief.
In our next lesson, we will learn to diagnose weak dialogue by identifying exchanges that lack a clear goal or subtext for each participant. This will equip you with the tools to ensure every line spoken in your story is pulling its weight.