Introduction
Welcome back. In our previous lesson, we established a process for auditing your outline's internal logic, ensuring that every major character action is driven by a clear and established motivation. We confirmed that your protagonist has agency—the power to make decisions that cause the plot to happen.
Today, we address the opposite scenario: when the plot happens to the protagonist without their involvement. This lesson focuses on a critical failure mode in plot construction: coincidence. Specifically, our learning outcome is to identify and flag coincidences where helpful events occur without character agency or prior setup.
From a systematic perspective, a bad coincidence is a bug in your story's causal code. It's an outcome that appears without a preceding, logical if-then condition rooted in character action or established world rules. Your task is to become a debugger for your plot, flagging these unearned events that break narrative logic and violate reader trust.
1. The Coincidence Equation: Problem vs. Solution
Not all coincidences are created equal. Their acceptability depends entirely on their function within the narrative. We can separate them into two main categories: coincidences that create problems and coincidences that solve them.
To understand this distinction, we'll start with a foundational article on the topic.
Coincidences in Fiction: What You're Doing Wrong
The article 'Coincidences in Fiction: What You're Doing Wrong' by K.M. Weiland provides a clear framework for understanding why some coincidences work and others fail. It establishes the core principle we'll be using.
Read the introduction and the first two main sections, ending just before '4 Ways to Sidestep Coincidences in Fiction'. Focus on a) why readers reject coincidences that solve problems, and b) the Pixar rule for what makes a 'good' coincidence.
As the article explains, the key distinction is:
- Problem-Creating Coincidences (Acceptable): These events get characters into trouble. They often happen at the beginning of a story to kickstart the plot. A character happens to be in the wrong place at the wrong time; they happen to overhear something they shouldn't. These are acceptable because the character must then use their own agency to solve the new problem. The coincidence creates conflict, it doesn't resolve it.
- Problem-Solving Coincidences (Unacceptable): These events get characters out of trouble. This is often called Deus ex machina ("god from the machine"). The protagonist is cornered, and a sudden, unearned event saves them—a forgotten ally appears out of nowhere, a villain suddenly has a change of heart, or they find the exact tool they need lying on the ground. This feels like cheating because the protagonist didn't earn the solution through their own actions.
The rule of thumb is simple: Coincidences can start the story, but character agency must finish it.
2. The Coincidence Audit: A 3-Step Diagnostic
To systematically identify unacceptable coincidences in your outline, you can perform a three-step audit. This process is designed to flag events that lack a causal or character-driven foundation.
Step 1: The "Happens To" Filter
This is a simple linguistic test. Read through your outline beat by beat. If you can describe a key plot development using the phrase "it happens to be" or "[X] happens to [the protagonist]," you have found a potential red flag.
The following resource explains this diagnostic tool clearly.
What makes something too big of a coincidence in a story?
The article 'What makes something too big of a coincidence in a story?' from Go Teen Writers offers a very practical heuristic for spotting potential coincidences.
Read the sub-section '3. Make sure your plot progression is based on characters making decisions'. Pay close attention to the paragraph that begins 'Any time I’m working on a synopsis...' The list of examples ('the guard “happens to” be asleep,' etc.) is exactly what you are looking for in your own outline.
Examples:
- The hero needs to escape, and the cell door happens to be unlocked.
- The detective is stumped, and a witness happens to call with the missing piece of information.
- The protagonist is falling, and a conveniently placed awning happens to break their fall.
Any event flagged by this filter must proceed to the next steps for further analysis.
Step 2: The Agency Test
This test directly leverages the concepts from our previous lesson. For every helpful event flagged in Step 1, ask the following question:
Was this event the direct or indirect result of a choice made by a character (preferably the protagonist) acting on their established motivations?
If the answer is no, you have confirmed a high-risk coincidence. The event occurred without character agency.
Step 3: The Setup Check
If an event fails the Agency Test, there is one final check. An event can feel earned, even if not directly caused by the protagonist, if it has been properly set up. Ask:
Was the possibility of this event, or the mechanism behind it, clearly established earlier in the story?
This is the principle of setup and payoff. A setup turns a potential coincidence into a satisfying, logical conclusion.
What makes something too big of a coincidence in a story?
This article provides an excellent example of how setup can legitimize a seemingly convenient plot point.
Read the sub-section '1. Make sure you properly foreshadowed surprises'. Focus on the example of the antique sword. Notice the difference between a subtle setup (mentioning the sword on the wall) and an overly obvious one (the 'neon arrow').
- Fails the Setup Check (Coincidence): The hero, a historian, is cornered by a henchman. He suddenly reveals he's a black belt in karate and defeats him.
- Passes the Setup Check (Payoff): The hero, a historian, is cornered. Earlier in the story, we saw him in a dojo, or saw a duffel bag with a gi in his apartment, or heard him mention his "weekend classes." When he uses karate now, it's not a coincidence; it's a payoff of a previously established fact.
An event that helps the protagonist and fails both the Agency Test and the Setup Check should be flagged as a critical plot weakness.
Test your understanding!
Below is a sequence from a sci-fi outline. Your task is to perform a coincidence audit.
Character Profile: Kaelen is a starship mechanic, not a pilot. His goal is to find a rare crystal to power his sister's life-support system. He is resourceful with machines but distrustful of authority.
Outline Beats:
- Kaelen learns the only known location of the crystal is on the forbidden moon of Xylos, which is guarded by an impenetrable automated defense grid.
- Kaelen steals a small freighter but is immediately trapped by the defense grid, which locks onto his ship. He has no way to bypass it.
- Suddenly, the entire defense grid shuts down for a full two minutes due to a system-wide, random power surge that happens once a decade. This gives him just enough time to slip through to the moon's surface.
Your Task:
- Identify the coincidence in Beat 3 using the audit steps.
- Explain why it's an unacceptable, or "bad," coincidence.
- Suggest a revised version of Beat 3 that fixes the coincidence by passing the Agency Test.
- Suggest a different revised version of Beat 3 that fixes it by passing the Setup Check.
Show answer
1. Identification:
- "Happens To" Filter: A power surge happens to occur at the exact moment Kaelen needs it. This flags Beat 3.
- Agency Test: The power surge was not caused by any action Kaelen took. It was a random external event. It fails the test.
- Setup Check: The "once a decade" random surge was not mentioned before this moment. It fails the test.
Since Beat 3 fails both tests, it is a critical coincidence.
2. Why it's Unacceptable:
It is a Deus ex machina. It solves Kaelen's "insoluble difficulty" without him having to earn it. His success is based on pure luck, not his skills or choices, which cheapens the stakes and his character's resourcefulness.
3. Revision (Passing the Agency Test):
Kaelen, trapped by the grid, remembers that old freighters of this model have a design flaw: they can reroute the main reactor's energy into a massive, focused EMP. It will fry his own systems and leave him adrift for hours, but it might just be enough to overload the defense grid's targeting sensors for a few seconds. He makes the desperate choice, slamming the console and causing the overload, and uses the brief window to get through.
(This works because Kaelen's action, based on his established skills as a mechanic, directly caused the solution.)
4. Revision (Passing the Setup Check):
Earlier in the story, while Kaelen was planning the heist, he hacked into the defense grid's maintenance logs. He discovered that the grid undergoes a mandatory diagnostic reboot every 12 hours, a process that creates a 90-second blind spot. His entire plan was not just to steal the ship, but to time his arrival perfectly to coincide with this reboot cycle. The tension now comes from whether he can make it to the grid in time.
(This works because the "convenient" shutdown is no longer a coincidence; it's a pre-established element that Kaelen built his plan around.)
Conclusion
You are now equipped with a systematic process for debugging your plot for unearned convenience. By rigorously applying this audit, you ensure that your protagonist's successes are the product of their agency and intellect, not authorial intervention. This creates a more logical, engaging, and satisfying narrative where every victory is earned.
Key Takeaways:
- Problem-solving coincidences (Deus ex machina) break reader trust and should be eliminated.
- Problem-creating coincidences are generally acceptable as they generate conflict for the character to solve.
- The three-step audit is a reliable method for identifying unacceptable coincidences:
- Filter for "happens to" phrasing.
- Apply the Agency Test: was the event caused by a character's choice?
- Apply the Setup Check: was the event foreshadowed or previously established?
- An event that helps the protagonist but fails both the Agency and Setup tests is a critical plot hole.
Preview of the Next Lesson:
We've validated your outline's causal chain, motivational logic, and now its resistance to coincidence. The next step is to ensure the plot has sufficient driving force. In the upcoming lesson, we will focus on a crucial element of momentum: verifying stakes escalation in an outline by confirming each major failure makes the next challenge harder.