A Struggle Or Clash Between Opposing Characters Or Opposing Forces

What Happens When Two Forces Just Won't Back Down

There's a particular kind of tension that makes a story worth caring about. It's not the pretty kind — not the polite disagreement over dinner where everyone shakes hands afterward. It's the kind where something real is on the line. Where two people, or two ideas, or two entire armies, look at each other and decide, not today, not ever*. Even so, that friction? That's where the best stories live.

We call it a conflict*, but that word gets thrown around so casually it almost loses its meaning. A conflict isn't just "two characters arguing.So naturally, without it, you've got a postcard. " It's the entire engine that drives a story forward. With it, you've got a novel, a film, a play, a political movement, a chess match.

What Is Conflict, Really?

At its core, a conflict is a struggle or clash between opposing characters, opposing forces, or both. But here's the thing most definitions skip past: conflict isn't just about disagreement. It's about resistance*. That's the textbook answer, and it's fine as far as it goes. One side pushes, the other pushes back, and what happens in that space between them is the story.

The Two Flavors of Opposition

There are basically two kinds of conflict working in any given scene, even though most people only talk about one of them.

The first is the obvious one: person versus person. So two characters, two opposing viewpoints, both dug in. The clash is external. On top of that, think of every rivalry you've ever read about — Holmes and Moriarty, Batman and the Joker, your protagonist and the corrupt mayor blocking their goal. You can see it.

The second kind runs deeper, and honestly, it's usually the one that keeps readers turning pages. Which means a mother who told a lie twenty years ago and can't sleep. It's the internal war — the character fighting their own fears, their own desires, their own worst impulses. A kid who knows what they should do and just can't make themselves do it. A cop who took a bribe. That kind of conflict doesn't have a fistfight, but it leaves the reader just as wrecked.

Forces, Not Just People

Here's what gets missed a lot. Now, the opposing force can be a system, a belief, a natural disaster, a ticking clock, a society. A village facing a flood. Conflict doesn't require two fully drawn characters staring each other down. A whistleblower going up against a corporation. A teenager trying to fit into a school that wasn't built for someone like them. The "character" on the other side of the struggle might be invisible, abstract, or distributed across a hundred people — but the resistance is just as real.

This is the part that separates a good story from a forgettable one. When the opposing force feels like it has weight — like it's not going to roll over just because the protagonist wants something — the story breathes.

Why Conflict Matters (And Why Most Beginner Writers Get It Wrong)

Here's a sentence worth tattooing somewhere: a story without conflict is just a description of things that happened. You can have a charming setting, beautiful prose, and deeply likable characters — and if nothing is actually at stake, the reader will quietly close the tab.

Conflict is what creates stakes. Tension is what keeps a reader leaning forward instead of leaning back. Stakes are what create tension. Pull any of those out and the whole thing collapses like a tent with one pole missing.

The Mistake of Mistaking Friction for Conflict

A lot of new writers confuse friction* — small bumps, awkward moments, minor disagreements — with actual conflict. Friction is texture. If your two characters are bickering about who forgot to buy milk, that's friction. Day to day, conflict is pressure. If one of them needs the other to confess something that could end their marriage before the day is over, now you're in conflict.

The difference? In conflict, something has to change. The world on the other side of the scene can't be the same as the world on this side. If nothing is at risk, you've written a slice-of-life moment. Which is fine, as long as you meant to.

Why Conflict Needs to Cost Something

This is the part most people skip. The hero wins the duel but loses their best friend. The reader knows. If the struggle doesn't cost the character something — time, comfort, relationships, safety, a piece of their soul — it doesn't feel earned. Also, the activist wins the campaign but ruins their health. The kid stands up to the bully and eats lunch alone for a week. Every meaningful clash demands a cost. They always know.

How Conflict Actually Works in a Story

If you strip conflict down to its bones, you get four moving parts. Most stories use all of them, even if the writer never names them.

The Protagonist Wants Something Specific

Not "to be happy.The protagonist has to want something concrete — a job, a confession, a door opened, a document signed, a person found. " That's too vague to fight over. Practically speaking, " Not "to find love. The more specific the want, the easier it is to build resistance against it.

The Opposition Pushes Back

And it has to be credible. A villain who's secretly weak, an obstacle that folds at the first sign of effort, a society that secretly agrees with the rebel — none of that produces a real struggle. On the flip side, the opposition has to feel like it could win. Maybe it even should win, by all logic. That's when the reader holds their breath.

The Stakes Are Clear

What happens if the protagonist fails? If the reader can't answer that question in one sentence, the stakes aren't doing their job. Even so, if she doesn't get the money by Friday, her father loses the house. * That's stakes. If she doesn't get the money, things will be hard* — that's a shrug.

The Pressure Builds

A flat conflict is a dead conflict. Here's the thing — things have to escalate. The opposition tightens. The clock ticks. The cost of failure climbs. Still, each scene should leave the character in a slightly worse position than before, or at least in a more complicated one. The reader should feel the walls closing in, even when the character pretends they don't.

If you found this helpful, you might also enjoy what is half of 3 1/3 cups or five times the sum of a number and.

Common Mistakes That Kill Conflict Before It Starts

Mistake One: Picking Sides Too Early

If your reader knows exactly who's right and who's wrong from page one, the conflict has nowhere to go. That said, the most gripping struggles live in moral gray zones — where both sides have a point, where the reader can almost see themselves in either corner. The minute you stack the deck, the tension drains out.

Mistake Two: Making the Opposition a Prop

A villain who exists only to be defeated isn't a character, they're a punching bag. They need their own logic, their own fears, their own version of why they're right. Even the worst person in your story believes, in their own mind, that they're the hero of their own narrative. Forget that, and your conflict becomes a video game cutscene.

Mistake Three: Resolving Too Quickly

A clash that takes one paragraph to resolve was never really a clash. Struggle is built through duration — through the time it takes to wear down, to compromise, to sacrifice, to outlast. The longer the cost is paid, the heavier the resolution feels.

Mistake Four: Ignoring the Internal War

External conflict without internal conflict is just an action sequence. Even so, the best clashes happen both outside and inside the character at the same time. Now, the warrior is fighting the enemy and their own doubt. Think about it: the whistleblower is fighting the system and the part of themselves that wants to stay safe. Skip the inner side and you get a chase scene. Keep it, and you get a story.

Practical Tips for Writing Conflict That Actually Hurts

Start from the want, not the character. It's tempting to build a character first and then find something for them to want. Flip it. Decide what they want, and let the want shape who they are. Want is the engine; character is the chassis.

Give the opposition a real reason. A villain who is evil "because they're evil" reads like cardboard. A villain who is doing this because of something that happened to them* reads like a person. Even if you never spell it out for the reader, you need to know.

Make the cost visible early. Don't save the consequences for the third act. Let the reader see what's at stake from the opening pages. The longer they know what's on the line, the more every scene afterward hums with pressure.

Let the protagonist be wrong sometimes. A character who's always right is exhausting. A character who makes mistakes, who misreads the opposition, who doubles down when they should retreat — that's a character the reader will follow anywhere.

**End the conflict differently

than it began. Here's the thing — a conflict that resolves exactly as the reader predicted was never worth the time it took to read it. The resolution should cost something the character didn't expect to pay, or reveal something that reframes everything that came before. A surprise ending isn't a twist for its own sake — it's the natural consequence of a conflict that was never simple to begin with.

The Architecture of Sustained Tension

Once you understand the principles, you need the practical scaffolding to hold them up. In practice, sustained tension operates on a rhythm — peaks and valleys that keep the reader engaged without exhausting them. In practice, too high, and the reader becomes numb. Too low, and they put the book down.

Build your scenes in escalating waves. On the flip side, the first confrontation should hint at the larger clash to come. Even so, the second should force a sacrifice. The third should break something the character can't repair. By the time you reach the climax, the reader has been trained to expect that every step forward carries a cost.

Between those waves, let the character breathe — but never fully. Even in the quiet moments, the conflict should be present in the background, like a headache that won't quite go away. A conversation about something mundane can carry unbearable weight when the reader knows what the character is trying not to say. The silence between two people who are about to betray each other is louder than any argument.

Pacing is not the same as speed. A slow scene can move the story forward more than a chase. What matters is whether the pressure is increasing or decreasing. As long as the reader feels the walls closing in, the story is moving, even when the characters are sitting still.

A Final Word

Conflict is not decoration. It is not something you add to a plot to make it more interesting. It is the plot. Everything else — the setting, the backstory, the world-building, the clever dialogue — exists only to make the conflict land harder.

Write a character who wants something badly. Give them an opponent who wants it just as badly, for reasons just as valid. That's why make the cost of getting it clear from the start. Let the struggle go on longer than feels comfortable. And when the resolution comes, make sure it changes something — the character, the world, or the reader's understanding of both.

Do that, and you won't have to worry about whether your conflict is strong enough. Here's the thing — they'll stay up too late because they need to know what happens next. The reader will feel it in their chest. They'll close the book and sit in the quiet for a moment, carrying the weight of what they just read.

That weight is the whole point. Conflict that doesn't cost anything wasn't worth the conflict. Plus, stories that don't leave a mark weren't worth the telling. Build the pressure, honor the struggle, and trust the reader to feel the full force of what you've made.

The best conflicts don't end when the fighting stops. Now, they linger because they revealed something true about the people inside them. Write that truth, and your readers will never forget it.