10 Screenwriting Lessons You Can Learn From The Dark Knight Rises

Dark Knight Rises
Welcome to a new series of articles we're running here at WhatCulture, prior to a new section of the site that will be opening up soon - one which will focus entirely on the subject of screenwriting. As a graduate with a degree in screenwriting, several short films under my belt, and years and years of experience writing online professionally, I'm hoping to delve a bit deeper into the screenwriting process with weekly articles. I want to explore the craft, offer advice in articles that aren't preachy or academically-aligned, but are easily digestible, much akin to the rest of the content we offer on the site. To kick things off, I've picked a movie which is always sure to generate a bit of discussion: The Dark Knight Rises.
I've watched The Dark Knight Rises three times now. With each viewing, I've found that I've become more and more disillusioned with€ well, what is it, exactly? If I had to relay my position on the movie with a single word, I doubt that it would be entirely possible. And yet - and I think many will agree - there is something not quite right about The Dark Knight Rises. As a Nolan film, it feels wrong. As a blockbuster, it feels way off base. Those of you who find yourselves constantly having to defend the movie might offer up some advice of your own: If you don't like it, stop watching it. Leave it alone. But that's more difficult than it appears to be: The Dark Knight Rises has to be one of the most interesting "mis-fires" in the history of Hollywood blockbusters. From a screenwriting/story perspective, anyway, it's a genuine curiosity. Three viewings later, and I still can't quite put my finger on what it is about this particular final chapter that irks me so much. What is true, however, is that The Dark Knight Rises clings to a strange, near-disastrous screenplay. And that, I think, is the biggest reason as to why I can't embrace the movie as a whole: It's constructed with an almost insulting amount of carelessness. From a director renowed for his Kubrick-esque perfectionism, it's bizarre. It wasn't always this way. My first viewing of the movie was a pleasant one. I came out of the movie feeling satisfied - or, at least, telling myself that I felt satisfied - though I knew, deep down, something wasn't quite right. Later, I realised that I had mistaken the movie's confusing nature for one of intelligent complexity. "Oh, a second watch will let me work out the plot points," I might've said out loud. I couldn't have been more wrong. Plainly put, I didn't understand what was happening because it didn't make any sense. Because the movie hadn't left me with anything to think about. To awe over. To ponder. I wasn't blown away in any respect. The visuals were nice, sure, but there had been a lot going on€ and how did it all fit together, exactly? I realised once I'd arrived home that The Dark Knight Rises had disappointed me greatly. Another viewing two days later, and I felt at even more odds with it. Is it a truly bad movie? Probably not. Is it a mess? Absolutely. With this article, I'm not looking to simply point out what Nolan did wrong, though - I want to explore it from a writer's perspective. What did he do wrong from a point of view of the craft, and what cautionary tales can we learn from it all? Best of all, perhaps, what did he do right? These articles are just as much about learning by good examples too - if not more so. Enough talk. Let's dive in and see what we handy screenwriting tips we can learn from The Dark Knight Rises...

10. Write Set Pieces That You've Never Seen Before

http://www.youtube.com/watch?v=WomtYMqeAe8 When we go to see blockbusters, the thing we usually remember more than any other is the set pieces. They're also the moments that we're probably looking forward to seeing the most prior to knowing much else about the story - especially these days, where you can analyze a movie's trailer in depth for hours and hours online. What you'll notice now, however, is that set-pieces are becoming bigger and bigger, what with the allowances afforded to filmmakers by way of CGI and massive budgets. This is great news for writers: if you can imagine it, it can probably be filmed. So what exactly is a set piece, you might ask? Well, these are the moments that help to define cinema at its best. They're the best sections, and the ones that you look forward to - can't wait to get to, even - the second time you sit down to watch a flick. It's the chestburster scene from Alien. The shark hunt in Jaws. The skyscraper climb in the last Mission: Impossible. They're explosions of cinematic invention and action spectacle. Going back to "if you can imagine it, it can probably be filmed," Christopher Nolan is a visionary in possession of such a mindset. And to give the man credit, he sure can conjure up a set piece. Whereas it's probably easy to just accidentally re-write a set-piece that you've seen in another movie, writing great set pieces is a serious route towards screenwriting success. Studios want to see original ideas for set pieces because, hey, they're what will eventually sell the movie to audiences. The good thing about set pieces is that they don't necessarily have to advance the story (though if you can conjure up one that does, good on you!), but exist to inject some energy where an Act risks getting flat. The Dark Knight Rises, on the whole, is surprisingly flat when it comes great set pieces. There are a couple that play like bad copies of set pieces from the movie's predecessor. The opening scene, however, is a great lesson in screenwriting, because it happens to be a set piece that a) we've never seen before and b) constantly surprises us. The key to a great set piece, however, isn't in the scale - it's in the originality. The Dark Knight has an even better opening set piece, what with the Joker's bank robbery in downtown Gotham. It's relatively low-scale, but the structure, pacing and suspense makes for a dynamite set-piece. Though Nolan tried to outdo himself with the plane sequence at the beginning of this movie, it's interesting to note that bigger doesn't necessarily mean better - the bank robbery is far more interesting and revealing of the Joker's nature. We learn a ton about him - best of all, we don't even realise it's happening, because we're too caught up in the excitement.

9. Ensure That Each Main Character Has A Clear Motivation

bane Here's a fundamental rule that always seems to get lost in the wake of all kinds of screenplays - produced and unproduced. But just like in real life, human beings are interesting because of their ambitions and motivations. What does that person hope to achieve? Same goes for the movies. And here's where - once again - The Dark Knight Rises remains vaguely thin. Though there are a few characters embedded in the movie's world that are working illogical agendas, the main culprits here are Bane and Talia al Ghul. What, really, is Bane's motivation? There are a number of options scattered throughout the movie, sure, though the execution is messy and unclear. Whether it's because he's in love with Talia or not, his extensive plan is made weak by the fact that he's - up until the end - working an unclear plan. The movie waits 'til the last moments to let us know that Bane is in cahoots with Talia, so for over two hours we're left in a state of confusion. If crime is down in Gotham and has been lowered thanks to the Dent act, why would the League of Shadows even need to destroy Gotham? It's a revenge mission, you say? Okay, but why would Talia be hellbent on carrying out her father's intentions wrongly, as opposed to just murdering Batman? Plot gripes aside, the target here is absolutely the screenwriting itself. Bane is a badly written character because he doesn't stand for anything. Eventually, it's revealed that he's just a puppet of sorts, and the impact of his speeches and rallies are reduced as a result on further viewings. Even if there is an answer of sorts buried within the screenplay, what use is it, really? In The Dark Knight, we knew from the very beginning that the Joker's intention was to "watch the world burn." That's it. Done. Okay, we know he's insane and that he just likes causing mayhem. Not exactly the most original reason, but hey, we know where we stand. All these turns for the sake of a meaningless "twist" isn't worth the strain it puts on the script. When writing your own screenplay, it's seriously important to ensure that each one of your main characters has a clear motivation from the start. How else are we supposed to know what's at stake, and whether or not we agree with the cause?

8. Take Your Time With Romance (Even In A Blockbuster)

the dark knight rises Here's something that you don't really notice until it goes wrong. And when it isn't done properly, romance is both awkward and frustrating to sit through. If you, as an audience member, don't believe it, or it's rushed to the point that you know instinctively that it's being crammed in as a future plot device, there's only one person to blame: the screenwriter. And The Dark Knight Rises - with its many, many plot points - decides to ham in not one, but two romantic encounters for its protagonist. One of which, between Bruce Wayne and Selina Kyle, is a standard enough blockbuster romance. Contrived perhaps, lacking complexity, but anywhere else it might feel less than clumsy than it does here - what more can we expect? But consider this: we spent a large part of two movies working through a turbulent and complex romantic relationship concerning Bruce Wayne and Rachel Dawes in Batman Begins and The Dark Knight. Two movies. It's a relationship that works, because it feels real, and comes with problems that are related to the films as a whole. If Bruce is Batman, can his relationship with Rachel really work? That's good writing, because the two characters are linked directly to a major theme within the movie universe. We also know that they were friends as kids, and there's a nice "will they?/won't they?" dynamic running through both movies. Simply put, we feel invested in these characters because we know them. Juggling so many plots meant that Nolan didn't have enough time to develop a relationship of such resounding resonance here. Which is fine, because killing off Rachel gave Bruce a new vein of angst to struggle against. Screenwriting is all about conflict, after all, external and internal. But when Bruce suddenly shacks up with Miranda Tate, a character who has only been introduced in this third movie, we can't really invest in their relationship. We don't know anything about Miranda. Put bluntly, she's an extremely boring character. And though the scene in which Bruce and Miranda sleep together at his mansion is there to make her later reveal more "personal," because the romance is rushed, it lacks any real punch. We've forgotten that they were even romantically involved at this point, anyway, and that's mostly down to the fact that - above all - their relationship felt forced. It's important to remember, then, that just like in real life, love takes time. And though real life romance likely takes years and years of work, it's up to cinema to grant us - at the very least - the illusion of such things. The Bruce Wayne/Miranda Tate romance feels like a plot point at work, because that's exactly what it is. But here's where one useless scene (and there are plenty in Dark Knight Rises) could've been traded for one that would've further grounded their relationship. As it stands, it feels awkward, and that's mainly because it's not earned.

7. There's Such A Thing As Too Much Plot

The-Dark-Knight-Rises3 Not many writers will find themselves stumbling upon this particular problem, because very few will ever be in the position that the Nolan brothers found themselves in with Rises. That's to say, they had to cap off an extremely successful trilogy with already established and overarching plot points, whilst introducing a whole bunch of new ones - they also had the creative freedom to do as they wanted, which might not have worked in their favour. Generally speaking, "too much plot" is something that most screenwriters never worry about - not having nearly enough plot is the universal worry amongst writers of that kind, because it's genuinely difficult to conjure up a story that remains interesting, gripping and absorbing for two hours. The most genuinely bizarre thing about Rises, however, is in just how much plot Nolan tries to incorporate into the movie for the sake of... well, for what reason? There's so much unnecessarily plot fodder, in fact, that the first hour or so of the movie is just there to explain plot points that have been set up for no real reason. New characters explaining things about new plots that extend the running time meaninglessly. And once the movie gets going, the Nolans introduce even more characters, some of whom turn up, say nothing of worth, and end up getting killed. Ask yourself this: "Would the movie have been any worse if they had never been included?" Worst of all, this kind of stuff commits screenwriting sins on two levels: it's confusing on a first watch, and boring as hell on a second watch. Trying to see how everything fits together the first time 'round here isn't particularly entertaining, because it's exposition on top of exposition, but sitting through it again - when you know what's happening - is mind-numbing. Truth is, the movie spends so much time explaining all its plots, we never really seem to escape the feeling that we're in exposition land. Instead of clearly defining the story and having Batman go up against a problem that we can understand and relate to, we just get lost in a labyrinthe of stories that don't directly affect the narrative or change the circumstances of the characters. The lesson to be learned? There's such a thing as too much plot. Define your storyline in its thinest possible terms, and build on that. You need the breathing room, after all, and so does your audience.

6. Need To Up The Tension? Add A Ticking Clock

Dark Knight Rises

Here's an age old, welcomed screenwriting trick that you can employ into just about any script, given you've got the right set of circumstances. The good thing is, it's simple and effective, and it gives your screenplay an added sense of urgency and tension without you having to do much. In the case of The Dark Knight Rises, the ticking clock is literally a ticking bomb, and one which will detonate at a specific time should Bruce Wayne/Batman not get there in time to stop it. And that's about as simple as this technique gets. Here, though, it's not quite as effective as it should be, granted that the ticking bomb doesn't need to be a ticking bomb. Bane and Talia might as well have detonated the bomb from the straight off. Still, it works in the sense that there's another layer of tension atop an already volatile situation. The ticking clock works for a number of reasons, but it's mainly so effective because - from the moment you set up the idea that there's a "race against time" - you imbue every moment from then on with an extra dose of drama. What else is a screenplay but a drama machine? It also gives you more to work with when it comes to getting your characters to talk to one another, and therefore allows you to build conversations and situations you might not have had reason. The ticking clock are creates conflict, and that's where you really want to have two characters bickering or arguing with one another. Simple, useful, tried and tested, it's an extremely effective way to give your script that added oomph factor. It also, by association, makes a script somewhat easier to write, because you're constantly under the weight on your own frantic plot device.

5. Bring Your Protagonist To His/Her Knees

movie-nerd-the-dark-knight-rises-movie-review-1 Here's something that Rises does well, given that one of the major plot points of the movie concerns Bruce Wayne's journey to transform himself into the Dark Knight after he's mentally and physically destroyed. And bringing your main character to their knees is a screenwriting notion that will always guarantee you good results, because what's more interesting that watching somebody fail and later trying to succeed at the same task? Here, Batman is tricked into facing off against Bane in an underground sewer. Ill prepared, he's beaten within an inch of his life. In any good screenplay, this is a good way to explore your character's motives. Either it happens towards the beginning of the flick, like here, so that the character can "rise" up and aim to defeat whatever it was that defeated them before. Or, as in A Fistful of Dollars, it can happen towards the end, where the character is almost killed, but manages to re-stabilize, gather and come back with a vengeance... However you employ this trope, bringing your character to the brink of destruction is a great way to ensure they have at least one goal going at a given time.

4. Make Sure All Your Main Characters Have An Arc (However Small)

http://www.youtube.com/watch?v=Mf1GD_587sA Believe it or not, all good movies hinge on one crucial factor: how do people change? You'll often find, in fact, that "bad movies" are slated as such because there has been no opportunity offered to its characters regarding an arc. In the case of Rises, Batman's arc remains muddled, though it's probably still one of the clearest arcs in the entire movie. Having protected Gotham for much of his adult life, Bruce Wayne realises that he must lay down his life for the city, and passes on Batman as a symbol and as a legacy. It's a loose arc, but it still works (though fans of the comic book incarnation might question whether a true Batman would ever "give up"). Selina Kyle, too, has an arc - she changes one very obvious respect: she becomes less selfish, comes back to help Bruce in his mission, and even allows herself to fall in love. That's an arc, plain and simple. As a result of these arcs, these characters are the movie's most effective. They go from A to B in a way we can track. That's screenwriting 101, right there. But there are characters in Rises that don't go from A to B in quite so clear a fashion. In fact, it's difficult to work out whether or not Bane had an arc - maybe he doesn't need one quite so much as the other main characters, as he's a villain, but his character layout is extremely confusing and ill-fitting, considering his purpose. As for Alfred and Lucius - two staple characters from the series - well... these unfortunate two are reduced to that of exposition dispensers. If you can avoid that sort of lackluster handling, it will greatly improve your screenplay. An arc doesn't have to be huge, after all: it can be tiny, in fact, just as long as it's there. And audiences will appreciate that you've gone to those lengths, no matter how small and insignificant they seem to you during the writing process. We're all drawn to change because, ultimately, we all want to change.

3. Give Your Audience Something To Chew Over

http://www.youtube.com/watch?v=nvtJ_XC2bz8 Christopher Nolan is pretty good at this generally, though it's kind of a no brainer that you should leave your audience with something to ponder and think about once a movie has finished - you should set out to do that anyway, regardless of the ending. In the case of Inception, another film directed by Christopher Nolan, I'd say that the director's ending of choice is ambiguous for the sake of being ambiguous, but that's not necessarily a bad thing - it's a blockbuster, after all, not some serious psychological examination, and it provokes a fun debate. Nolan employs a similar trick in The Dark Knight Rises, which might've been more effective had the movie that proceeded it been a bit more satisfying. Still, Nolan was probably wise to leave the movie on a cliffhanger, with Bruce Wayne - having faked his own death - living in Florence with Selina Kyle. Whether or not you think that's an effective ending for this trilogy is down to a matter of opinion, but the point is that - at least - the movie gives audiences something to ponder. In my humble opinion, it's actually an extremely unsatisfying ending and somewhat of a cop out. After three movies, do we really want to leave the fate of an iconic character to unnecessary speculation? When writing your own screenplay, though, it's important to consider an ending that you feel would leave you feeling intrigued, but not short changed. If you can get the person reading your script to feel both satisfied and wanting more on the last page in equal measure, you're certainly on the right track.

2. Stay True To Your Characters

A-AlfredPR180712 There's nothing more frustrating than watching a movie and suddenly being wrenched right out of it. This can happen for all sorts of reasons, though often it occurs when you find yourself thinking "hey, that character would never do that." And generally speaking, if an incident like this occurs whilst you're watching a movie, you're probably in the right. After all, you're not consciously trying to pick out moments where characters are doing things that don't seem like them - you just feel it, because you're only going on what has been established so far, and you can't help if it doesn't feel logical, right? If you're pulled out as a result of one of these moments, it's probably because the screenwriter has done a bad job in setting up the motivation for a character to act in such a fashion. Either that, or they've been lazy and decided to utilise a character to do something they usually wouldn't because it's easier that way. A lot of people had this complaint when it came to the relationship between Bruce Wayne and Alfred in Rises. After a lifetime of friendship, would Alfred really have abandoned Bruce? Not likely, given what we've learned of him over the course of two and a half movies. It didn't feel justified. It's important to keep your characters consistent. Stay true to their motivations and how you've set them up in your screenplay thus far. If they start acting differently on page 50, your audience will notice. And in case you're unsure whether you've compromised a character's integrity, have a trusted friend read your screenplay and ask them what they think. As an outsider, they'll likely hit on it straight away, should anything be going array.

1. Ensure That There's Logic Working Behind Every Action

Dark Knight Rises There's a part towards the last third of the movie where Bruce Wayne returns to Gotham from a Middle Eastern prison. In the case of his return, audiences might've had to suspend their disbelief somewhat to conjure up a solution as to how Wayne got back into a city under such a tight security regime. Still, he might've managed it - the fact that it stays ambiguous is frustrating and lazy from a writing point of view, but it's passable because, hey, we don't always know everything, and the exposition levels at this point are in overdrive anyway. But before Bruce sets about saving Gotham, he spends time painting a huge fiery mural on the side of bridge. Okay, it looks cool, there's the iconic symbol of the Batman - he's back! Woo! Except€ well, why? Why did Bruce Wayne take a couple of hours out of his schedule to do that? From a story perspective, it makes zero sense. The clock is ticking. People are getting shoved out onto the ice fields and murdered. There's not much time. Things are seriously grim. These are the sorts of moments that - during a first viewing, at least - you don't really think about. You're too absorbed in in spectacle of it all. In retrospect, these moments kill a movie dead. And in this case, logic has been traded in for a brief moment of visual wonder. Was it worth it? Absolutely not. Firstly, it doesn't make sense. Secondly, it has us questioning Bruce's motives. Would a genius waste his time with something like that? And why alert the bad guys to his presence, anyway? The lesson to be learnt here, then, is to think through moments like this and ask yourself: is this essential to the story, does it work on a logical perspective, and is there another place that this might work better? If you're lacking logical motive, though, the audience are bound to pick up on it. If not right away, they most definitely will in retrospect. Like this article? Which screenwriting lessons did you take from The Dark Knight Rises? Are there any other movies you'd like to see in this series? Let us know in the comments section below.

Contributor

All-round pop culture obsessive.