Back to blog

Expert Lists of Cliches for Stronger Fiction Writing

· Novelium Team
lists of cliches writing cliches fiction tropes editing tips novel writing

Clichés aren't a taste problem. They're a data problem.

You don't need another article telling you that "it was all a dream" is lazy, or that love triangles can feel manufactured. You're a professional. You already know the obvious offenders. The useful question is why these defaults keep showing up anyway, especially in ambitious novels with layered timelines, rotating viewpoints, and cast sprawl.

Clichés are rarely proof that a writer lacks imagination. They're usually proof that the manuscript's internal tracking has started to fail. When character knowledge, timeline logic, relationship states, object locations, and power progression stop being reliably legible to the writer, the draft reaches for a prepackaged solution. A cliché is often the place where causal logic got too messy to manage by hand, so the story grabbed a familiar shortcut.

That matters more than most lists of cliches admit. Historically, cliché talk used to live in the realm of style-guide scolding. Then corpus analysis made repetition measurable. One analysis of movie dialogue examined more than 72,000 films released since 1940 and catalogued 138 common clichés, with question-form lines like "What the hell" appearing in just over one-third of the movies studied. That's useful because it shifts cliché detection from taste to pattern tracking. The same shift needs to happen in fiction editing.

Most lists of cliches are still framed as moral instruction. Avoid this. Never use that. Replace stale phrasing with fresh phrasing. Fine. But if your manuscript keeps generating cliché-shaped solutions, the issue isn't wording. It's system failure. You aren't dealing with a sentence problem. You're dealing with broken state management.

1. The Chosen One Hero's Journey

The chosen one plot doesn't become cliché because destiny stories are necessarily dead. It becomes cliché when "chosen" replaces actual causal architecture. The manuscript stops proving why this protagonist, in this sequence of events, in this political and emotional ecosystem, could plausibly occupy the center. So the draft installs cosmic authorization and calls it structure.

That shortcut shows up a lot in large manuscripts because the chosen one frame is a brute-force way to unify too many moving parts. If your secondary cast, prophecy logic, power rules, and institutional stakes aren't staying synchronized, "special by fate" smooths over the gaps. Temporarily.

A young man with messy hair holding an old book while standing on a rural road at sunset.

What it's usually hiding

In practice, this cliché points to weak ability tracking. The protagonist acquires competence whenever the plot needs it, emotional resilience whenever the theme needs it, and narrative importance whenever the cast threatens to become more interesting than the lead. That's not mythic. That's drift.

Harry Potter, Eragon, Percy Jackson, The Maze Runner. Different execution, same pressure point. The story needs a central axis. If the manuscript can't maintain one through earned decisions, it invokes destiny.

Practical rule: If your protagonist is "chosen," track what they're actually chosen for. Not symbolically. Operationally. What can they do, when do they learn it, who knows about it, and what does it cost?

A static character profile won't catch this. "Brave, stubborn, secretly powerful" is fluff. What matters is scene-by-scene progression. When did the character first demonstrate the relevant skill? Which witness saw it? Which prior limitation now needs revision? If you can't answer that cleanly, the cliché isn't the problem. The missing progression map is.

Subversion isn't enough either. Making the chosen one reluctant, sarcastic, traumatized, or unworthy doesn't fix anything if the underlying competence curve still jumps rails. The only useful move is to make power acquisition auditable. If the manuscript can prove the arc, the trope stops feeling prefab.

2. Love Triangle Romantic Conflict

Most love triangles aren't romantic conflict. They're indecision scaffolds.

When this device works, each relationship reveals a different future self for the protagonist. When it fails, one option exists for heat, the other exists for safety, and the protagonist pinballs between them because the draft needs suspense. That's not emotional complexity. That's relationship-state drift.

Bella, Edward, Jacob. Katniss, Peeta, Gale. Plenty of readers will tolerate the structure if the emotional math stays clean. The problem is that in long fiction, the math usually doesn't stay clean. Affection spikes after scenes that don't earn it. Jealousy appears because the chapter needs friction. A supposedly impossible choice becomes obvious the second you chart actual behavior.

The tracking failure underneath

This is usually a knowledge-state problem. One character knows too much, another knows too little, and the protagonist's emotional response updates without the manuscript properly accounting for what happened in between. Writers often call this chemistry. It isn't. It's continuity debt.

You need to track at least three layers at once:

  • Declared feeling: What the character says they want.
  • Demonstrated attachment: Who they move toward under pressure.
  • Knowledge burden: What each person knows about the others, and when they learn it.

If both romantic options don't have independent motion, the triangle collapses into authorial traffic control. The cleanest fix is brutal. Remove any scene where the protagonist's attraction changes but no new information, vulnerability, betrayal, or concrete choice triggered the change.

If the triangle only exists when all three characters are in the same chapter, it isn't a triangle. It's staging.

Lists of cliches are useful here as filters, not commandments. Editorial resources like ProWritingAid's searchable list of clichés are handy because they remind you how often writers default to stock romantic language when relationship logic gets fuzzy. In revision, use that same mindset structurally. Flag stock scenes, stock reversals, stock declarations. Then ask what state change the manuscript is failing to track.

3. Dark and Brooding Love Interest Archetype

The dark romantic lead isn't the issue. The issue is when opacity substitutes for characterization.

A brooding figure with a sealed past can work for a long time if the concealment has rules. The character knows certain things, hides certain things, leaks certain things under pressure, and resists intimacy in ways that match prior scenes. Once those rules vanish, brooding turns into a continuity patch. The character becomes hot because the manuscript won't specify him.

Edward Cullen, Rhysand, Severus Snape, and the old prototype in Rochester all operate near this line. The archetype persists because mystery creates runway. It buys pages. But mystery without tracked disclosure turns every reveal into retroactive damage control.

A thoughtful young person with curly dark hair looking away against a plain grey wall background.

Brooding needs rules

If you're writing a Byronic hero, stop managing him as an aura. Manage him as a disclosure system. What is he withholding? From whom? Since when? What event justifies the next crack in the wall? Without those answers, "mysterious" becomes random access characterization.

Static character bibles demonstrate a significant shortcoming. They capture vibe, not change. "Haunted, sardonic, emotionally guarded" tells you nothing about whether his emotional walls drop too quickly in chapter 18 or whether the protagonist learns a family secret before she had access to it.

Writers also confuse attraction with narrative exemption. A dark love interest still needs stable motives outside desirability. If every contradiction can be waved away because he's wounded, dangerous, or devastatingly attentive in private, the manuscript has stopped tracking cause and effect.

Use a simple test. Remove the physical appeal. Does the character still make coherent decisions from scene to scene? If not, the trope is carrying broken logic on its back.

4. The Convenient Plot Device Coincidence

Coincidence is only offensive when it replaces earned transfer of information.

Characters can absolutely bump into the wrong person at the right time. They can overhear something, find a letter, catch a glance, miss a train, pull the wrong file. Life does that. Fiction can too. What readers object to is not improbability by itself. They object when the draft uses coincidence to bridge a gap it didn't build a causal path for.

The usual signs are obvious. A secret document appears just when the plot needs acceleration. Two enemies meet in the one place where conflict can advance. A character overhears the exact conversation required to rescue a stalled middle. None of this reads as fate. It reads as author intervention.

A single piece of folded paper rests on an empty black wooden park bench in a garden.

Earn the accident

You don't fix this by banning coincidence. You fix it by making the setup legible before the payoff. If a character finds a letter on a park bench, the question isn't whether that's plausible. It's whether the manuscript established why that bench, why that hour, why that character, and why nobody else got there first.

This is adjacent to deus ex machina, but not identical. The core failure is usually information-flow tracking. The writer knows the clue exists, so the writer underestimates how much logistical scaffolding readers need before the clue feels inevitable rather than dumped from above.

Try these checks in revision:

  • Trace access: Who physically could've encountered the information first?
  • Trace motive: Why was the information where it was?
  • Trace visibility: Who else should've noticed it, and why didn't they?

When those answers exist on the page, coincidence starts reading like convergence. When they don't, the plot is outsourcing causality.

5. The Misunderstood Villain Motivation

Nuanced antagonists aren't cliché. Mandatory tragic reframing is.

A villain can have grief, history, ideology, and legitimate critique. Fine. The cliché appears when the story treats sympathetic motive as a substitute for structured antagonism. Suddenly every bad act is backlit by trauma, every reveal arrives in one tidy package, and the manuscript expects moral complexity points for giving the villain a wound.

Magneto, Killmonger, Thanos, Snape. Different genres, same temptation. The draft wants the antagonist to feel deep, so it backfills explanatory pain. Sometimes it works. Often it lands as an apology note attached to a body count.

Where manuscripts lose the thread

This usually comes from reveal compression. The writer knows the villain's backstory from day one, but the manuscript hasn't distributed that knowledge properly across point of view, rumor, artifact, witness memory, and confrontation. So the whole thing arrives late and heavy. Readers don't experience deepening complexity. They experience a briefing.

The fix is distribution, not decoration. Plant motive in fragments that alter interpretation without dissolving responsibility. Let the protagonist learn pieces at different times than the reader does if that sharpens tension. Track exactly when each faction understands the antagonist's rationale and how that knowledge changes strategy.

A tragic backstory can explain present cruelty. It does not automatically complicate it.

This is one place where giant lists of cliches are less useful than decision rules. Some writing guides flatten the issue into "clichés are trite and should be avoided." That's directionally true, and Be a Better Writer also notes they can work for comic effect or characterization. The same principle applies here. The question isn't whether a misunderstood villain is banned. The question is whether your manuscript is using the reveal with purpose, or using it to fake depth after the fact.

6. The Quirky Manic Pixie Dream Girl Trope

This trope is what happens when a character gets tracked as effect instead of person.

The manuscript knows exactly how she changes the brooding male lead. It knows how she sounds, what she wears, how she disrupts rooms, which details make her feel sparkling and off-axis. What it doesn't know is what she wants when he's not present. So she arrives as voltage, not as a human being.

Ramona Flowers, Summer Finn, early Harley Quinn, and every borderline example that gets defended with "but she's memorable" all trigger the same editorial question. Memorable to whom, for what function, and with what independent momentum?

Quirk inflation is a tracking problem

Writers often think this trope comes from bad ideology alone. Sometimes it does. More often in manuscripts, it comes from incomplete state tracking. The writer records surfaces because surfaces are easy to remember. Hair, laugh, boots, strange hobby, chaotic line delivery. Internal objective progression is harder, so it gets neglected.

That creates a weird imbalance. Her quirks stay consistent, but her arc doesn't. She can keep showing up with the same eccentric texture while her agency fades between chapters.

The fix is not "make her less quirky." The fix is to track her like you would track a political antagonist or series detective:

  • Private objective: What is she trying to accomplish unrelated to the lead?
  • Decision pattern: What does she do when nobody's watching?
  • Consequence trail: Which scenes changed because of her choices, not her vibe?

Once you do that, a supposedly cliché character often either deepens fast or falls apart completely. Good. Better to discover she's a lighting effect than spend another draft pretending she has an arc because she says whimsical things on rooftops.

7. The Exposition Dialogue Info-Dump

"As you know" dialogue isn't a dialogue problem. It's a knowledge map failure.

Writers resort to info-dump exchanges when the manuscript has lost track of who knows what, who needs to learn what, and what scene can carry that transfer without turning into a briefing memo. So two characters explain the world to each other in language neither of them would ever use naturally. The reader hears the scaffolding creak.

Fantasy is notorious for this, but every genre does it. The detective restates the case to the partner who worked the same case. The siblings recount family history they've both lived through. The veteran explains the rules of magic, espionage, or court politics to another veteran because the chapter needs onboarding.

A quick example of the problem is the classic as-you-know-Bob exchange. It's clunky because the dialogue's real audience isn't the other character. It's the reader, and readers can hear the cheat.

Fix the transfer path, not the wording

The cleanest fix is to stop treating exposition as speech and start treating it as controlled release. Information can move through action, misinterpretation, ritual, paperwork, failed plans, overheard fragments, argument, or internal narration constrained by the point of view's blind spots.

The other fix is mechanical. Maintain a live knowledge ledger for major characters. If one person already knows the coronation law, the curse mechanics, or the details of the old betrayal, don't let them explain it unless they have a strategic reason to do so. Reminder dialogue, manipulation dialogue, and testing dialogue are all different from exposition.

Before revising a talky scene, watch this breakdown:

Editor's shortcut: If you can replace the speaking characters with two office printers and the scene still conveys the same facts, cut it and redesign the transfer.

8. The It Was All a Dream Ending Cop-Out

Writers don't reach for dream reveals because they forgot readers hate them. They reach for them because the manuscript has painted itself into a continuity corner.

A dream ending, hallucination reversal, or unreliable-account wipeout often appears when the story can't reconcile its own event logic. Stakes escalated too far. The thematic ending wants one thing, the causal chain demands another, and the draft takes the trapdoor. Suddenly preceding events become provisional, symbolic, or unreal. The writer gets interpretive freedom. The reader gets their investment invalidated.

Dallas made this infamous with the Bobby-in-the-shower reset. Countless short stories have done the same thing in miniature. Even borderline cases only survive when the unreal frame was part of the design all along, not emergency drywall over a broken ending.

Surreal isn't the problem

If you're using dream logic, then commit to dream logic early and keep it internally consistent. Readers will follow a reality-bent narrative if the manuscript establishes the governing rules and doesn't weaponize ambiguity only at the finish line.

What breaks trust is retroactive cancellation. If the events mattered while the reader was reading them, they need to matter after the reveal too. Maybe they reshape identity. Maybe they expose desire. Maybe they alter a real-world decision. But they can't evaporate because the plot failed to close.

This is one of the oldest reasons editors keep lists of cliches around. Language and structure can manipulate perception, and writers have always needed filters for that. Even the old saying "Lies, damned lies, and statistics" survives because people recognize how persuasive framing can disguise weak reasoning. A dream ending often does the same thing narratively. It wraps surrender in the language of sophistication.

9. The Instantly Competent Novice Hero

Readers don't need realism in the strict sense. They need progression they can audit.

The novice hero becomes cliché when mastery appears as a convenience layer. The protagonist learns the sword style, magical discipline, criminal tradecraft, political instincts, or combat reflexes at the speed required by the next set piece. Failure becomes cosmetic. Training becomes montage residue. The manuscript wants payoff without maintaining the burden of earned competence.

Neo is the famous edge case because The Matrix literalizes skill upload. That's a built-in rule, so the cheat is at least systematized. In most novels, there is no such rule. The hero just gets good, then better, then elite, because the draft can't afford the slower sequence of mistake, adaptation, and narrowed limitation.

Competence must stay attached to time

Timeline management holds greater importance than writers often admit. Skill isn't just a trait. It's a chronology. What did the protagonist practice, for how long, under whose supervision, with what setbacks, and what can they still not do?

When writers lose that chronology, every victory starts feeling weightless. Worse, side characters who should outperform the protagonist turn into furniture because the lead's growth curve has become author-mandated.

Use a progression check that asks four blunt questions:

  • First attempt: What did failure look like?
  • Intermediate gain: What specific improvement happened next?
  • Current ceiling: What still remains unreliable?
  • Witness record: Which characters have seen enough to trust this competence?

You don't need pages of drills. You need durable evidence of change. If the hero wins because the manuscript forgot where they were on their own curve, readers will feel the fraud even if they can't name it.

10. The Conveniently Absent Reasonable Solution

This is the cliché that enrages experienced readers fastest because it exposes the machinery.

A problem persists. An obvious solution exists. Nobody takes it. Nobody says the key thing, asks the obvious question, calls the person who could clarify the mess, or uses the resource already established on the page. The draft manufactures tension by deleting adult decision-making.

Sometimes this shows up as stubbornness. Sometimes as pride. Sometimes as "if I tell you, you'll only get hurt." Sometimes as simple omission. Whatever the costume, the underlying issue is the same. The manuscript has lost track of what each character knows and what barriers prevent action.

Force the obstacle to exist

If two characters could solve the central misunderstanding with one honest exchange, the solution isn't to make them dumber. It's to build a reason the exchange can't happen cleanly. Power imbalance. Surveillance. Valid fear. Conflicting incentives. Prior betrayal. Public consequences. Those are real obstacles.

Without them, scenes become procedural stalling. Characters stop behaving like themselves and start behaving like withheld variables.

Marketing editors use lists of cliches in a similarly practical way. B Squared Media's breakdown of marketing clichés treats overused phrases as signals of vague thinking and poor differentiation. That's the right frame for fiction too. The obvious non-solution in a plot is usually a signal of vague causal thinking. The sentence may be dramatic, but the manuscript hasn't specified why the straightforward move is off the table.

When you find this cliché, don't rewrite the dialogue first. Write down the information each person has at that exact moment, then write down the actual cost of telling the truth. If the cost is thin, the scene is thin.

Top 10 Story Clichés Comparison

Item Implementation Complexity 🔄 Resource Requirements ⚡ Expected Outcomes 📊 Ideal Use Cases 💡 Key Advantages ⭐
The Chosen One Hero's Journey Moderate, established beats but requires consistent power progression Medium–High, worldbuilding, mentor arcs, power rules High engagement and clear stakes; risk of predictability Epic fantasy, long-form series, coming-of-age sagas Strong emotional resonance; reliable narrative structure
Love Triangle Romantic Conflict Medium, balancing multiple romantic arcs and timing Medium, develop two compelling love interests and chemistry High emotional tension; potential for reader backlash if unearned Romance, YA, serialized drama where relationship stakes matter Instant emotional stakes; explores relationship dynamics
Dark and Brooding Love Interest Archetype Low–Medium, trope easy to use but needs nuance to avoid toxicity Low–Medium, focused backstory and consistent motivations High intrigue and romantic tension; can romanticize unhealthy patterns Gothic romance, paranormal, romantic suspense Compelling mystery; supports redemption arcs
The Convenient Plot Device Coincidence Low, quick to deploy but often lazy storytelling Low, minimal setup; little plotting required Short-term plot acceleration; long-term credibility loss Quick twists, early drafts, throwaway scenes Speeds plot progression; can create surprise moments
The Misunderstood Villain Motivation Medium, requires careful foreshadowing and pacing Medium, layered backstory and timeline control Adds moral complexity and thematic depth; may excuse harm if mishandled Character-driven drama, antihero stories, thematic works Deepens antagonist; prompts ethical questions
The Quirky Manic Pixie Dream Girl Trope Low, simple to implement but risks shallow portrayal Low, personality set pieces; needs expansion to be substantive Memorable quirks but often criticized for lacking agency Light rom‑coms if subverted; satire or character studies Distinctive voice and comic relief when well-rounded
Exposition Dialogue Info-Dump Low, efficient but breaks natural dialogue flow Low, requires scenes where characters relay information Clear background delivery; reduces immersion and realism Dense worldbuilding needs, early drafts, explanatory scenes Efficient info transfer; tight control of timing
The "It Was All a Dream" Ending Cop-Out Low, easy structural reset but often unsatisfying Low, minimal setup unless dream logic is complex Enables psychological exploration or reset; commonly frustrates readers Experimental fiction, surreal narratives, intentional unreliable POVs Allows exploration of subconscious; can reset stakes
Instantly Competent Novice Hero Low, shortcut to capability that undermines growth Low, avoids extended training sequences Immediate action readiness; victories may feel unearned Fast-paced action, wish‑fulfillment, short adventures Maintains momentum; quick gratification for readers
The Conveniently Absent Reasonable Solution Low, contrived omission of obvious choices Low, little plotting; must justify avoidance to be plausible Prolonged tension; risks reader frustration and broken believability Plots needing sustained conflict without external obstacles Sustains conflict and plot length when justified

From Diagnosis to Systemic Cure

Every cliché on this list is a diagnostic flag. Not a sin. Not a sign that you've failed some purity test. A flag.

The chosen one points to broken power progression. The love triangle points to relationship-state drift. The brooding love interest points to unmanaged disclosure. Convenient coincidence points to weak information routing. The misunderstood villain points to reveal compression. The manic pixie figure points to character tracking by effect instead of agency. The info-dump points to a bad knowledge map. The dream ending points to unresolved continuity pressure. The instantly competent novice points to an untracked ability timeline. The absent reasonable solution points to missing obstacle logic.

That's why swapping one trope for a fancier trope doesn't solve much. If the data layer underneath the manuscript is unstable, the story will generate another shortcut. Maybe it won't be "it was all a dream." Maybe it'll be "secret sibling," "hidden prophecy," "last-minute betrayal," or "sudden confession." Same disease, different rash.

This is also why most character profiles fail. They're static documents trying to manage dynamic systems. They tell you eye color, trauma history, favorite drink, maybe a handful of voice notes and contradictions. Fine. None of that helps when chapter 23 needs to know whether Mara already learned that Felix forged the letter, whether Tomas still believes the wrong alibi, whether the knife moved from the study to the carriage in scene order, or whether your apprentice mage should be capable of that spell yet. Character development notes are not the same thing as character tracking.

What matters for consistency isn't the fun worldbuilding trivia. It's state. Knowledge state. Emotional state. Relationship state. Location state. Ability state. Obligation state. Those are the variables that mutate across scenes and wreck manuscripts when they aren't maintained. Most cliché failures are just those state changes going untracked until the writer reaches for a stock solution.

And this gets worse at scale. At novella length, you can sometimes hold the book in your head. At novel length, especially with multiple points of view or a series bible accreting over time, you can't. Spreadsheets help until they don't. Character bibles get stale. Revision introduces one elegant fix in chapter 8 and three new contradictions in chapters 14, 19, and 31. The manuscript's internal record falls out of sync with itself.

That's the primary use of lists of cliches for working novelists. Not as schoolroom shame sheets. As forensic tools. If a familiar device keeps appearing in your draft, ask what kind of tracking burden the manuscript is trying to escape. That's where the actual work is.

Novelium was built for exactly that layer of the problem. It doesn't just help you spot a cliché after the fact. It helps you maintain the moving parts that create cliché-shaped failures in the first place. When the system can track character knowledge, contradictions, object continuity, event order, and scene-level progression across the manuscript, you stop relying on memory and instinct to hold everything together. You get a live map of what the book believes to be true.

That changes revision. Instead of sanding down stale scenes one by one, you can fix the broken mechanism producing them. The result is better than "more original." It's more coherent. And coherence is what lets originality survive contact with a long draft.


If you're done babysitting spreadsheets and stale character bibles, try Novelium. It tracks the continuity variables that break manuscripts, including knowledge states, timeline order, character contradictions, relationship shifts, and object movement, so you can fix the root problem before it turns into another familiar workaround.