Bad Guys Have Reasons: Writing Villains Who Aren't Cardboard

The worst thing you can do to a villain is make him evil.

Evil is a shortcut. It's the writer telling the reader who to hate so nobody has to do the harder work of understanding why a person ends up doing the thing. A man who's evil because the plot needs a bad guy is a cardboard cutout with a gun, and you can feel the cardboard, and the second you feel it the fear goes out of the book. Nobody's scared of cardboard. People are scared of the guy at the end of the bar who has a reason.

My rule, the one taped over the desk: good guys have flaws, bad guys have reasons. Not excuses. Reasons. There's daylight between those two words and the whole genre lives in it.

Take the three families in these books. Not one of them is run by a monster who wants to watch the world burn. They're run by people solving problems, and the problems are real, and the solutions are what damn them.

There's a widow, seventy-three, who runs a construction empire off relationships — aldermen, union stewards, building inspectors, a couple of priests. She never wanted the chair. She got it because every man ahead of her died in a federal cell and somebody had to keep the machine turning. Her reason is the most human one there is: she's the last person alive who understands how the thing works, and if she lets go, it comes apart and takes the neighborhood with it. That's not villainy. That's duty pointed in a bad direction. She's frightening precisely because you understand her. You'd probably do what she does. That's the point.

There's an enforcer on the West Side, late forties, the most dangerous man in a fractured operation run by three captains who can't stand each other. He should be running the whole thing and he isn't, because the structure won't allow it and his own history of violence keeps him boxed into the one job they'll give a man like him — the breaking of things. Here's his reason, and it's the one that makes him more than muscle: he can see, clearer than anyone above him, that the organization is destroying itself. He's the smartest man in the room and the room only values his hands. Give a reader that — a man trapped inside a role beneath his intelligence, watching fools drive the car off the road — and the reader will follow him into terrible places, because the reader knows what it is to be underestimated.

And there's the quiet one. Mid-forties, patient, runs the trafficking side — narcotics, and people, which is the line in these books I refuse to make glamorous. His reason is that he learned. While the old families spent a decade rebuilding the same structure the feds had just knocked down, he built something new — burners, insulation, layers between himself and the street so nothing touches him. He's the most dangerous man in the city because you forget he's in the room until it's too late.

But this is where the reasons-not-excuses line has to hold, and hold hard. Understanding why a trafficker operates the way he does is craft. Making him cool is a betrayal. The people moving through his corridors are not plot devices — they're human beings with their own names and their own before, and if the writing ever forgets that to make the villain more impressive, the writing has failed at the only thing that actually matters. He gets a reason. He does not get a pass. The camera stays on the cost.

Which brings me to the real answer, the one under all three. The villain in these books isn't a person. It's the system. It's the rot in the institutions — the mayor's office, the parish council, the longshoremen's local, the development authority — all of it compromised, all of it still running, all of it load-bearing. The families are just the parts of that machine you can see. The widow, the enforcer, the quiet man — they're not the disease. They're symptoms with faces, people doing locally reasonable things inside a structure that has stopped making sense, and the tragedy is that every one of them could tell you exactly why they did what they did, and every reason would check out, and the city rots anyway.

That's the villain worth writing. Not a man who wants to be bad. A machine that runs on people who each had a reason, feeding it one good reason at a time until there's nothing left standing but the machine.

So when you build your antagonist, don't ask what makes him evil. Ask what he's protecting. Ask what he's afraid of losing. Ask what reasonable thing he wanted before the wanting turned him into the man your hero has to stop. Then put the reason on the page and take the cardboard off, and let the reader sit with the worst realization the genre has to offer — that they get it. That in his chair, with his reasons, they're not sure they'd have done different.

The guy at the end of the bar isn't scary because he's a monster. He's scary because he makes sense.