Introduction
In our last session, we developed a diagnostic process to audit your outline for unacceptable coincidences, ensuring that every helpful plot event is earned through character agency or prior setup. We treated your outline like a system and debugged it for logical fallacies that break reader trust.
Today, we shift from validating the logic of your plot to validating its momentum. A logically sound story can still fail if it's boring. The engine of narrative engagement is escalating pressure. Therefore, this lesson addresses the learning outcome: Verify stakes escalation in an outline by confirming each major failure makes the next challenge harder.
We will construct a systematic method to audit your outline's "try-fail" cycles. You will learn to identify points where a character's failure leads to a demonstrably more difficult subsequent problem, ensuring the story's tension continuously rises rather than stagnates.
1. The Core Mechanic: Escalating Complications
The middle of a story, often called the "rising action," is where many plots lose momentum. The key to maintaining it is to ensure that the protagonist's journey isn't just a series of events, but a series of escalating challenges. A useful, mechanical way to think about this is the Try-Fail Cycle.
A character tries to achieve a goal, fails, and that very failure creates a new, more difficult situation. The process then repeats.
To begin, let's establish the core concepts of escalation and the try-fail cycle.
Brandon Sanderson's 2025 Overview of Story Structure ...
The article 'Brandon Sanderson's 2025 Overview of Story Structure' introduces two key mechanical concepts for us: the 'Try-Fail Cycle' and the 'Yes, But / No, And' framework. These are practical tools for ensuring a story's conflict progresses.
Please read the section titled 'The Try-Fail Cycle: Mastering Discovery Writing.' Focus on the core loop: a character encounters multiple failures, each more challenging than the last, before achieving their goal. Note how failures force adaptation and reveal new information.
As the resource explains, the cycle is not just about repeated failure. It's about consequential failure. A failed attempt must not return the protagonist to their starting position. Instead, it should put them in a worse position, making their next attempt inherently harder.
This brings us to a simple but powerful logical operator for building plots: "No, and...".
When a character attempts to achieve a goal, the outcome can be framed as:
- "No": The character fails.
- "No, and...": The character fails, and a new complication is added, making the situation worse.
For example:
- Goal: Sneak past the guard.
- Outcome ("No"): The guard spots you and you run away. (You are back where you started).
- Outcome ("No, and..."): The guard spots you, and now he's sounded a general alarm.
Your outline should primarily consist of "No, and..." or "Yes, but..." (success with a complication) outcomes to ensure continuous escalation. A simple "No" leads to stagnation.
2. The Anatomy of Escalation: Defining "Harder"
To audit your outline, we need to move beyond the abstract idea of "harder" and define it with specific, verifiable parameters. What makes a new challenge mechanically more difficult than the last?
The following resource provides an excellent case study.
The article 'Escalating Complications' from Storm Writing School provides a brilliant, granular analysis of what escalation looks like in practice. We will use its breakdown as a model for our audit.
Read the sections titled 'Parts' and 'Now, note how things ramp up'. The text analyzes a video of an iguana being chased by snakes. Pay extremely close attention to the specific, concrete reasons given for why Part 3 is 'even worse' than Part 2. This is our checklist for defining escalation.
From this analysis, we can extract a set of measurable variables for escalation. When a protagonist fails and faces a new challenge, we can test if it's "harder" by asking these questions:
- Scale of Opposition: Has the number of antagonists increased? (e.g., from one snake to a group of snakes).
- Capability of Opposition: Has the antagonist become more skilled, more desperate, or revealed a new, more dangerous ability? (e.g., snakes lunging with open mouths).
- Environmental Hostility: Has the setting itself become an obstacle or more dangerous? (e.g., the iguana must now cross treacherous crevasses).
- Resource Depletion: Has the protagonist lost a tool, an ally, time, or another resource as a result of the failure?
- Stakes Proximity: Is the protagonist closer to their ultimate goal, making this new failure potentially more catastrophic? (Failing 3 meters from the finish line is more dramatic than failing at the start).
A strong escalation will typically modify one or more of these variables in a negative direction for the protagonist.
3. The Escalation Audit: A Step-by-Step Process
You can now use these concepts to perform a systematic audit on your outline.
Step 1: Isolate the Try-Fail Cycles
Go through your beat sheet and identify each major sequence where the protagonist attempts to achieve a significant goal and fails or only partially succeeds.
Step 2: Analyze the Consequence of Failure
For each failure point, examine the very next beat where the protagonist formulates their new plan or faces the next challenge.
Step 3: Apply the Escalation Litmus Test
Using the variables from Section 2, compare the challenge before the failure to the challenge after the failure.
- Does the scale of opposition increase?
- Does the capability of opposition increase?
- Does the environmental hostility increase?
- Does the protagonist have fewer resources?
- Is the protagonist closer to the goal, making the stakes proximity higher?
If the answer to one or more of these is "yes," your outline passes the escalation test for that beat. If the new situation is not demonstrably harder across any of these variables, you have found a point of stagnation. The "No" was not followed by an "and..."
Example Audit:
- Outline Beat 5: The hacker, Anya, tries to breach the corporation's firewall from a remote cafe. She fails when her intrusion is detected.
- Outline Beat 6: Anya goes home and tries to breach the same firewall again using a different program.
Audit Result: FAILURE.
- Scale of Opposition: Same (the firewall).
- Capability of Opposition: Unchanged, possibly higher now that it's "aware" of her, but the beat doesn't specify this. Let's assume it's the same.
- Environmental Hostility: Lower (safer at home than in a public cafe).
- Resources: Same.
- Stakes Proximity: Same.
This is a stagnant loop. The failure had no meaningful consequence.
Revised and Escalated Version:
- Outline Beat 5: The hacker, Anya, tries to breach the corporation's firewall from a remote cafe. She fails when her intrusion is detected.
- Outline Beat 6 (Revised): The corporation's security traces her attempt back to the cafe. She barely escapes as security agents arrive. Now a fugitive with her face on internal memos, she can no longer operate in public. She must now attempt the hack by physically infiltrating the corporate building, a much more dangerous plan.
Audit Result: PASS.
- Scale of Opposition: Increased (from a piece of software to active security agents).
- Environmental Hostility: Increased (she is now a fugitive, the world is less safe).
- Resources: Decreased (lost anonymity, lost safe working locations).
- The "No, you can't hack the firewall" became "No, and now they are physically hunting you." The challenge fundamentally changed and became harder.
Test your understanding!
Below is a three-beat sequence from a fantasy outline. Your task is to perform an escalation audit.
Character Profile: Elara is a young mage trying to retrieve a Sunstone from the Shadowfang Crypt to heal her blighted village.
Outline Beats:
- Try: Elara reaches the crypt's entrance, which is sealed by a riddle-lock. She attempts to answer the riddle.
- Fail: She gives the wrong answer. As a penalty, the lock magically teleports the Sunstone from the crypt's main chamber to a random, unknown location outside the crypt, somewhere in the surrounding forest.
- New Try: Elara now begins searching the vast, ordinary forest for the Sunstone.
Your Task:
- Does this sequence pass or fail the escalation audit?
- Justify your answer using the five escalation variables (Scale/Capability of Opposition, Environment, Resources, Stakes Proximity).
- Propose a revised version of Beat 2 (the consequence of failure) that creates a stronger escalation.
Show answer
1. Audit Result:
This sequence fails the escalation audit. It's a de-escalation of stakes and tension.
2. Justification:
- Scale/Capability of Opposition: Decreased significantly. The opposition has changed from a specific, magical obstacle (a sentient riddle-lock) to a non-sentient, non-active problem (finding a needle in a haystack).
- Environmental Hostility: Decreased. She has moved from a dangerous, named location (Shadowfang Crypt) to a generic, less threatening one (the surrounding forest).
- Resources: Unchanged.
- Stakes Proximity: Decreased. She was at the entrance, on the threshold of her goal. Now she is further away from it than before, with no clear path forward.
The failure made the problem more tedious, but less dangerous and dramatic. It didn't make the next challenge harder in a way that increases tension; it just made it more aimless.
3. Revised Version for Stronger Escalation:
- Revised Beat 2: She gives the wrong answer. As a penalty, the riddle-lock remains sealed, but her failure awakens the crypt's spectral guardians. Ghostly sentinels now patrol the perimeter, and a countdown begins—etched in glowing runes on the door—after which the Sunstone will be consumed by shadow forever.
Why this is a better escalation:
- Scale/Capability of Opposition: Increased. The opposition is now active and dangerous (spectral guardians) where before it was passive (a lock).
- Resources: Decreased. She has lost time, a critical resource, due to the new countdown (a "ticking clock" scenario).
- Stakes Proximity: Unchanged, but the stakes are now higher. She is still at the entrance, but failure is now permanent, and the cost of trying again involves facing new, active threats.
Conclusion
You now have a robust, mechanical process to ensure your plot maintains forward momentum. By auditing for stakes escalation, you confirm that every failure is consequential and serves to increase the pressure on your protagonist, making their eventual success more earned and satisfying.
Key Takeaways:
- A plot escalates through "Try-Fail Cycles" where the failure makes the situation demonstrably worse.
- The "No, and..." framework is a simple logical test for consequential failure.
- Escalation can be measured against concrete variables:
- Scale and Capability of Opposition
- Environmental Hostility
- Resource Depletion
- Stakes Proximity
- A failure that does not negatively impact at least one of these variables is a point of narrative stagnation and needs to be revised.
Preview of the Next Lesson:
We have now audited our outline for causality, motivation, coincidence, and escalation. The internal machinery is sound. The next logical step is to consider the overall size and scope of the project. In our next lesson, we will focus on the learning outcome: Determine the appropriate story scope by aligning the number of major plot events with target word count. This will connect our abstract outline to the practical realities of producing a finished story of a specific length.