How could I have been so wrong about a screenplay?
Genre: Biopic
Premise: We follow Apple co-founder Steve Jobs through three of the most important presentations of his life.
About: This film’s history is almost as storied as Steve Jobs himself. The infamous Sony hack revealed that David Fincher never really connected to the script. When he declined, so did leading Steve Jobs candidate Christian Bale. Sony head Amy Pascal didn’t really like the script either, waffling every time she was encouraged by producer Scott Rudin to put it into production. Eventually, the project had to move to Universal, where B-team Danny Boyle and Michael Fassbender came to the rescue (give me that B-team any day of the week!). But would it be enough to make the film a must-see? It’s looking promising. The film opened in only four theaters this weekend, but grossed a staggering 500k per screen. For comparison, American Sniper, released via the same strategy, grossed 600k per screen.
Writer: Aaron Sorkin
Details: 2 hours and 2 minutes long (off of a 177 page screenplay)
I gave the Steve Jobs screenplay a “wasn’t for me.”
Can I have a redo?
Hello. (Again).
Steve Jobs: The Film, knocked me on my ass, held me down, and tickle-tortured me until I couldn’t breathe anymore. And yet I couldn’t shake that “love-hate” relationship a proper tickle-torture leaves you with.
This movie works. And it shouldn’t have. It’s too different. Too repetitive. Led by too big of an asshole.
But somehow, “Steve Jobs” avoids the spinning pinwheel of death and replaces it with a Spotlight engine that always finds the exact PDF script you’re looking for. And that’s thanks to two people. Danny Boyle and Michael Fassbender.
I’m always the first to say that no director or actor can overcome a bad script. But every once in awhile, this proclamation bites me in the ass. If you find a chunk of ass on Sunset Boulevard, please return it to me.
“Steve Jobs” follows Apple co-founder, Jobs, through three of the most important Apple announcements in history – when Jobs announces the original Mac, when he announces the NEXT system, and when he announces the original iMac. Each mini-story centers on the half-an-hour leading up to his presentation, leaving Jobs to spar with all his nemeses in the meantime. These include: his boss John Sculley, his programmer, Steve Wozniak, his marketing director, Joanna, his other head programmer, Andy Hertzfeld, and his daughter, Lisa.
If you remember, my problem with the script was two-fold. First, the 3-act structure was too repetitive, with every act taking place right before a big presentation.
This got tiring when it was just words on a page (in a 177 page tome, mind you), but Danny Boyle did an EXCELLENT job translating those pages to images. He constantly moved us through the buildings so that most conversations took place in new environments. And most of the time, he’d make sure those environments added something extra to the scene.
For example, in the script, it felt like every Jobs-Wozniak conversation was the same. But in, for example, Jobs and Wozniak’s third act confrontation, Boyle has the two barking at each other in the auditorium with Jobs on stage and Wozniak 20 seats deep. By forcing the two to hash things out in front of numerous Apple employees, it gave the conversation an energy you just couldn’t feel on the page.
The second problem with the script was our unlikable main character, Steve Jobs himself. The man was a total prick on the page. But Michael Fassbender gave the character life. And you know what? He didn’t exaggerate Steve’s positive traits in some desperate bid to make him likable. He played him like a real guy who understood his flaws and did his best to manage them.
His scenes with Joanna (Kate Winslet) were particularly persuasive for a couple of reasons. First, he respected her. And second, he had a LOT of scenes with her. So a lot of the movie is Steve talking to a woman that he respects the hell out of. This evened things out when Steve belittled other characters. We knew there was a good side to this man. He merely had a hard time finding him.
Also, he was so sweet to his daughter. In the script, it felt like he was merely tolerant of her. But here, he clearly connected with and loved this girl. That one-two punch (his connection with Joanna and also with his daughter) made me see that Steve Jobs could be good, and even wanted to be good.
Now let’s get to what the script did REALLY right. When you read an Aaron Sorkin script, the first thing you want to talk about is DIALOGUE. It’s what he’s known for. It’s what he does best. So you’re always seeing what you can learn from the master. I learned a lot.
First, almost every single conversation was laced with a ton of conflict. Jobs battling with Lisa’s mom over whether she deserves his money. Jobs battling with John Sculley about the reason he was fired from Apple. Jobs battling Andy Hertzfeld about making sure the Mac said “Hello” during the inagural presentation. Jobs battling with Joanna about whether he should pay for his daughter’s Harvard tuition. Jobs battling with Woz over acknowledging Woz’s Apple II team.
Remember, heavy conflict dialogue is some of the easiest dialogue to write because it’s clear what needs to happen in the scene (each character must try and “win” the argument). When your dialogue is conflict-less — when there’s nothing to “win” – that’s when you’ll find characters struggling to say interesting or meaningful things.
I’d say 75% of the scenes here involved heavy-conflict. That’s not by accident. Sorkin knows that’s where dialogue thrives.
Sorkin is also known for his obsession with the walk-and-talk. He uses it so frequently that it’s become a walking joke. And we see a lot of it here, where Jobs is moving throughout the buildings, taking on character battles every time he’s on the move.
Well, the walk and talk is not just a way to keep the scene moving. It’s also great for dialogue. When you have characters walking, you create a journey, and a journey isn’t over until the characters reach their destination. Until that happens, you have your audience on a line, which means you have their attention. Simply put, your audience is more focused on dialogue when your characters are moving since their attention will be heightened until the destination is reached.
That’s not to say you can’t make a conversation interesting when characters stand in one place. There’s plenty of that going on here as well. But the next time you watch a film, all else being equal, keep tabs on how attentive you are when characters are walking and talking as opposed to when they’re stationary. You’ll find that you’re a little more tuned in when they’re on the move.
It’s similar to putting time-constraints on dialogue, which, not surprisingly, Sorkin does as well. This whole movie is a time constraint. There isn’t a single conversation that takes place where Jobs isn’t in a hurry – where his presentation isn’t a few minutes away. And Sorkin always saves the most important conversations for right before the presentation.
THIS IS NOT BY ACCIDENT.
We naturally feel more anxious the closer we get to a deadline (in this case, Jobs’s presentation). So if you place a big conversation right before a deadline, we’re LOCKED IN. We’re worried about our character making the impending time constraint, so we’re secretly pushing for him to hurry his conversation up. The problem is, the conversation is important, so we’re tuned into that as well. This means we’re tuned in on all frequencies, creating a sense of extreme focus.
It’s no coincidence then that the biggest conversation of all (between Jobs and his daughter before the final presentation) occurs AFTER Jobs’s presentation is supposed to start. That’s right, for the first time in the film, Sorkin pushes us PAST his start deadline, heightening our awareness beyond any and all previous levels so we’re super-tuned in. The dialogue sizzles in part because there is so much weight placed on every word. I mean, Jesus, the whole world is impatiently waiting for our hero downstairs! Does it get any more intense than that?
For contrast, imagine Jobs trying to have the same conversation with his daughter on a lazy Sunday afternoon, at his house, with all the time in the world, each character perfectly relaxed. Sound like a conversation that’s going to knock your socks off? My guess is probably not.
These are all things I’ve talked about before, though. You’re probably looking for more in-depth tips this Sorkin go-around. What does Sorkin do that makes his dialogue crackle where so many others fizzle? I noticed a few things. Once Sorkin sets up the basics (heavy conflict, a time constraint, characters on the move), he weaves in a variety of conversational variables. Here are some of the big ones I noticed.
1) Asides – A character will all of a sudden take us on a tangent. They’ll say something like, “When I was eight, do you know what the most important thing in the world to me was?’
2) Jokes – Characters crack jokes, sometimes self-deprecating, sometimes at the other character’s expense. A good joke relieves tension, preventing the dialogue from getting too melodramatic.
3) Zingers – Sorkin loves Zingers. Have a character say something derogatory to another character, then have the other character come back with a clever burn.
4) Teachable moments – This is one of Sorkin’s favorite things to do. Have your characters teach the audience something. So a character will say something to the effect of, “Did you know the Romans refused to feed their soldiers after a battle?” The character will go on to explain why this is, before eventually bringing it back to how this relates to their problem.
5) Analogies – Characters will constantly say things like, “It’s like putting together a stereo. You want to choose the parts on your own.” Lots of analogies in a Sorkin script.
6) Set-ups and payoffs – Whereas a lot of writers like to set plot points up and pay them off later (Marty McFly plays guitar in high school. This pays off later when he’s asked to play guitar at his parents’ Fish Under the Sea Dance), Sorkin likes to set up DIALOGUE and pay it off later. So Jobs might call Woz a dickwad. Then 15 minutes later, Jobs will need Woz’s help for an unexpected problem, and Woz will say something like, “I didn’t know dickwads were capable of that.”
On their own, each of these things might seem obvious. But from a person who reads a lot of screenplays with a lot of bad dialogue, I can assure you that the biggest problem with amateur dialogue is how plain and uninspired it is. Characters say exactly what they’re thinking in a monotone matter. By mixing in all of these tools, Sorkin’s able to write a lot of vibrant dialogue. Of course, on top of these tools, you still need imagination, creativity, and talent. Just because you know to use analogies doesn’t mean you can think up an analogy as clever as Aaron Sorkin. But just knowing that you should bring that into the mix in the first place puts you well ahead of the majority of your competition.
Steve Jobs shocked me. I thought this was going to be just like the script. But Danny Boyle elevated it to something more. And he NAILED the Jobs-daughter relationship, which was the heart of the screenplay. Jesus, man. The ending? On that rooftop? These eyes don’t lie. I was tearing up. I want to go find my old iMac and give it a big fat iHug.
[ ] what the hell did I just watch?
[ ] wasn’t for me
[ ] worth the price of admission
[x] impressive
[ ] genius
What I learned: What I learned had nothing to do with the actual screenwriting side of this movie. What struck me is how much Steve Jobs failed in his career. The Mac was a failure, the Lisa (the computer before) was a failure, the NEXT was a failure, Jobs was fired from Apple. It wasn’t until the iMac hit that Jobs truly succeeded. The next time you’re worried about a bad writing day or a script that didn’t get received as well as you’d hoped, remember that a man who many consider to be a genius failed repeatedly in his first 12 years in the business. Failures didn’t stop Jobs. So they shouldn’t stop you.
A Mars Western in the vein of Chinatown? Watch out!
Get Your Script Reviewed On Scriptshadow!: To submit your script for an Amateur Review, send in a PDF of your script, along with the title, genre, logline, and finally, something interesting about yourself and/or your script that you’d like us to post along with the script if reviewed. Use my submission address please: Carsonreeves3@gmail.com. Remember that your script will be posted. If you’re nervous about the effects of a bad review, feel free to use an alias name and/or title. It’s a good idea to resubmit every couple of weeks so your submission stays near the top.
Genre: Sci-Fi
Premise (from writer): When recent, inter-global events threaten to disrupt the idyllic life on the first Mars Colony, a woman with a secret to hide must do all that she can to prevent neighbors in her small town from taking up arms against each other.
Why You Should Read (from writer): I believe that audiences want to be challenged. Why? Because I go to the movies a lot and I like to be challenged. So, it stands to reason that when writing I choose topics that are challenging with characters who are flawed but relatable. This is what led me to write “The Only Lemon Tree on Mars.” Like all good sci-fi there’s an allegory about today buried in there; specifically the modern political process. And although there are a few action beats, it’s really a drama about a woman struggling to make the world better despite the machinations of men. Most importantly, she does this by being a woman, and not acting like a man. In this day and age, that’s an important distinction.
Writer: Chad Rouch
Details: 108 pages
I’m really glad this one got in. Despite some readers believing I’m only in it for the straightforward “follow the rules” type screenplay (someone told me in my Steve Jobs review that I didn’t like the script because it didn’t adhere to traditional structure), I’m here to tell you that I embrace originality! I’m always looking for stuff that’s different. Different is where the genius lies.
What I’m NOT looking for, though, is BAD DIFFERENT. Or confused different. Or “film school experimental” different. In other words, I don’t like “different” that has to do with the writer’s lack of knowledge about storytelling. I like carefully cultivated different – the kind of different with a clear plan behind it. Unfortunately, I don’t see that much.
Hopefully we can get some “carefully cultivated different” today.
9 year-old James trudges down an old country road before meandering into a small town. For those who haven’t read the logline, you might assume you’re at the beginning of a Western. And in some ways, you are. But this Western doesn’t take place on Earth. It turns out James lives on Mars.
James’s mom, Ellie, is a NASA scientist who’s responsible for finding the best place on Mars to farm. And that’s where this American colony, the colony of Elzee, has settled. And it’s hard up here for a chimp. Crop-growth isn’t exactly breaking records. And Earth stopped communicating with Mars months ago.
We get the sense that Elzee is slowly dying. And if Earth doesn’t come to their rescue, everyone’s going to be in a lot of trouble. Luckily, Earth does call. Apparently, the reason they weren’t instagramming was because America was in a Civil War. Now that the war is over, American’s sending a ship up to say hi.
The Mars farmers (or, as I like to call them, the “Marmers”) aren’t so sure Earth’s visit is kosher. It’s quite the coincidence that a ship is showing up just days before the rare Mars rain season. Could Earth be coming to steal Mars’s crops? Might they grab the food, slaughter the colony, then hop on their ship all before The Voice starts?
Rabble-rousing farmer, Tom Dubray, doesn’t want any Earthlings threatening his livelihood. So he grabs a bunch of farmers and readies an army. It’ll be up to Ellie to keep the peace. But with her marriage falling apart and everybody seemingly strapped into their crazy cribs, the Martians very well might kill each other before the Earthlings ever show up.
The Only Lemon Tree on Mars is the best Amateur Friday script I’ve read in awhile. Not only does Chad engage us with one of the simplest easy-to-read writing styles you’ve read all year, he gives us a story unlike any we’ve seen before. As we’ve discussed – if you can offer the reader an experience they haven’t had before? You’re a hundred Mars miles ahead of your competition.
My big problem with Wednesday’s “Boy Scouts vs. Zombies” was that I didn’t know the characters. Even worse, I didn’t feel like the writers wanted to know their characters. Chad proves he’s not playing that game with Lemon Tree.
At the heart of his story is a complex love triangle between Ellie, her husband Reiner, and her lover Ansel. Reiner, a brilliant scientist, works for weeks at a time hundreds of miles away on Mars’s atmosphere machine. This has left Ellie to raise her family on her own. And quite frankly, she’s lonely! It’s only natural that she would fall in love with Ansel, who lives in town.
One of the most compelling character-storylines that plays out is Ellie trying to decide whether to divorce Reiner for Ansel, Reiner eventually realizing Ansel is his wife’s lover, and then later, when Reiner is forced to protect the very man who’s stolen his wife from him (from the militarized Martians).
With both those things said, there’s something missing from this script and I’m not sure what it is. As good as the writing is, the story feels a bit dry in places. And when Chad does try to inject drama, there’s something vague and misguided about it that leaves you wanting more.
How you infuse drama (the major plot points in your story) is the key to keeping your reader’s interest. Give them something small when they want something big, and that might be the moment when they decide to mentally check out.
Take Teddy for instance. Teddy is a Martian farmer who kills another farmer in a bar fight. But it was accident. Yet the event is turned into a major plot point where Reiner is asked to represent Teddy in a trial regarding the murder. Why a scientist is playing lawyer doesn’t make any immediate sense. And since this accidental murder’s not the main point of the story, we’re left to ask why we’d want to watch a trial about it.
The rain stuff is also confusing. The impending rain season is discussed dozens of times throughout the script. Yet it’s not clear why it’s so important. While farming seems to be slow on Mars, we’re never told HOW slow.
Farmers are also suspicious that the Earthlings are coming to steal their crops. But it’s not clear if Earth needs crops. It’s not clear if they’re short on food at all. Nor is it clear why Earth would send a ship to Mars to steal a bunch of subpar Mars vegetables. I mean what’s the crop yield in this small town? 30 acres? Is it really cost effective to fly 34 million miles for 30 acres of food?
Chad needed a scene to make clear what these rains meant. Tell us, for instance, that if this rain doesn’t happen, all of their crops will die before the next rain season comes. Which means everyone here on Mars will starve to death. Just because you’re writing an indie movie doesn’t mean you can’t add some good old fashioned STAKES. High stakes work in any story.
And you have a classic case of confused-protagonist here. Who’s your protagonist? Is it Ellie? If so, why are so many other people driving the story?
Remember, your main character should make the majority of the choices that drive the story. I hated that Ellie just did whatever the Mayor told her to do. I hated how when Reiner showed up (a guy we didn’t even like) he became the temporary protag.
Let’s stay with Ellie and MAKE HER MORE ACTIVE. That alone should infuse this script with some energy. Have her making a lot more decisions. Have her running around trying to get things right. The love triangle story is fine but Ellie trying to snag Ansel shouldn’t be the only thing that gets her out of bed.
Finally, I think you’re a draft or two away from your final plot.
You should simplify the story. In the first act, Mars learns Earth is coming and assumes it’s for good reasons. At the midpoint, they discover secret information (plot twist) that implies Earth is coming to steal their crops. From the midpoint (page 50-55) to the end of Act 2 (page 80-85) then, they prepare for war. And then Earth lands with a small marine-based crew of 200 soldiers, and the third act is the battle for the colony.
And I don’t mean trenches are dug and a traditional shoot-out occurs. You could stay true to the story’s low-budget roots and focus on skirmishes that occur in nooks and crannies of the town. Maybe a group of Marines comes to take down Ellie’s home. She and Reiner must defend themselves and that defense of their home sequence is the climax.
As for the inter-town conflict, I still think you can have that. I like the idea of nobody agreeing how to handle the approaching Earthlings. That’s perfect 2nd act stuff there. But instead of falling apart when the Earthlings arrive, what if they learn to come together? That might provide you with a nicer arc. That we are capable as a species of communicating and compromising and coming together for a common cause.
Or hell, if you wanted to make this super-indie, you could have the Earthlings land and the marines slaughter the entire town. The End. It wouldn’t be my choice but you’d get mad indie cred, that’s for sure.
The Only Lemon Tree on Mars is a messy script that’s not quite there yet. But boy does it show potential for both its screenplay and its writer. Chad Rouch can write. And if he hasn’t gotten attention from the industry yet, it’s about time that changes.
Script link: The Only Lemon Tree On Mars
[ ] what the hell did I just read?
[ ] wasn’t for me
[x] worth the read
[ ] impressive
[ ] genius
What I learned: Important characters, even if they’re not who they appear to be at first, need to be introduced WITH PRESENCE so we know that they’re going to be important later on. The reason for this is, if someone isn’t introduced with PRESENCE, we forget about them. So when you try to bring them back, we’re like, “Who’s that?”
There’s this character in “Lemon Tree” named Tom Dubray who becomes a really important part of the farmer’s resistance. But the guy is given the most forgettable entrance ever. Here’s his intro line, which occurs during a town meeting: “Once inside, Ellie spots TOM and ANGIE DUBRAY, both 40s with a worn look of people who have spent their lives on a farm, who wave her over to sit near them.”
The guy doesn’t even get his own introduction line! He’s doubled up with his wife. That right there tells the reader: UNIMPORTANT. Then, as the meeting goes on, Tom offers a couple of forgettable lines and that’s it. His scene is over. With this character becoming so important later on, give us an intro line to remember. “TOM DUBRAY doesn’t look like much at first glance. But there’s something deadly about this man’s stare. He doesn’t see you. He sees through you.” That’s kinda cheesy but you get the point. You want to point out that there’s something important about this guy.
I ain’t going to lie folks. I’m buried in Scriptshadow 250 reads. The good news is, I’ve already sent TWO scripts into the Top 25. And no, I’m not going to tell you which ones. Because I’m evil. Because I’m an evil evil man.
Unfortunately, this means I need you to do the heavy lifting today. Normally, Thursday is about me offering screenwriting tips to you. But today, you’re going to offer screenwriting tips to me, and by extension to each other.
You see, a couple of weeks ago when I was going through the Scriptshadow 250 e-mail submissions, one of you mentioned that screenplays were about characters doing bad things for good reasons. I’d never thought of it that way before but I realized that’s exactly when screenplays are at their best. Someone has to do the wrong thing for the right reason.
Think about it. If your hero has to kill a child molester to save the day, there isn’t a whole lot of drama in that. I mean, of course he does. But what if your hero had to kill an innocent man to save his son from a child molester? Now we’ve got some drama, right? He’s doing a bad thing for the “right” reason.
I get so wrapped up in my GSU universe, I forget how many other lessons and tips and theories are out there. And maybe I oughtta do more listening and less preaching.
So here’s my question. What are the best screenwriting tips you’ve learned that haven’t come from this site? What is that amazing tip that I don’t talk about here on Scriptshadow? It’s time for you to teach me something. And make sure to curate the comments by UP-VOTING your favorite tip so the best tips rise to the top.
I’m hungry for knowledge.
Feed me, Seymour! FEED ME!
Genre: Biopic
Logline: We follow Apple co-founder Steve Jobs through three of the most important presentations of his life.
About: Wait a minute, you’re saying. Didn’t they already make a movie about Steve Jobs starring Ashton Kutcher? Yeah, well, that was pretty much determined to be the B-movie version of the genius’s story. This was always going to be the “real” Jobs movie, as it was looking like a sure thing that Fincher would direct and Bale would star. In the leaked Sony e-mails, however, we learned many things about the tumultuous development of the movie, as then Sony head, Amy Pascal, was never 100% committed to the idea of making the film, especially after the other Jobs movie failed so spectacularly. But super producer Scott Rudin always believed in the project and eventually flew the coop to Universal, where the project now stars Michael Fassbender, and will be directed by Danny Boyle. Seth Rogen plays Apple co-founder, Steve Wozniak.
Writer: Aaron Sorkin
Details: 177 pages – February 2014 draft
Well buckle my shoe and call me Jerimiah.
I have seen writers take chances before in my life. But this has gotta be one of the biggest ever taken on this level. Sorkin has thrown ALL THE RULES OUT in writing this script and really put himself on the line in the process.
I mean… I’m not going to lie. I’m kinda shocked. Like, “Did that really just happen?” I’ll say this. I am NOT a fan of the traditional biopic. So I’m all for shaking the format up. But this? This is ballsy. I’m going to go as far as saying that this script is why this project caused so much consternation at Sony. Fincher on, Fincher off. Bale in, Bale out. Amy Pascal never really committing to the idea. I think people were scared of this script. And I don’t blame them. Just like the original Macintosh: It’s different.
I’ll try my best to break it down for you. The script starts in 1984 with Steve Jobs about to announce the Macintosh computer to the world. A few days back, Jobs debuted the now famous Mac Superbowl commercial and boy did it pay off. It’s gotten every major news outlet on the planet here at this auditorium eagerly anticipating the unveiling of the new revolutionary computer.
Sorkin uses a problem and a time constraint to build tension into the scene. The Mac is supposed to turn on and say “Hello” but the “Hello” part isn’t working and Jobs is screaming at the computer’s head tech, Andy Hertzfeld, to fix it before the demonstration begins in 30 minutes. In the meantime, Jobs tussles with a few people including Apple co-creator, teddy bear Steve Wozniak, over giving credit to Woz’s team during the speech, and Chrisann, his former girlfriend, who insists that he’s the father of her six year old daughter, Lisa.
Oh yeah, the court has declared Jobs the father as well, but Jobs refuses to accept the ruling and treats Lisa, a beautiful smart little girl, accordingly. He acts like she’s an alien and would rather take a bath in a tub of tarantulas than converse with her.
Cut to four years later where we learn, through TV news snippets, that the Mac launch failed big time and that Steve Jobs was pushed out of the company. Jobs has moved onto his next project, called the “NEXT Cube,” geared towards the educational market. And, once again, we’re meeting him at the launch presentation, a half hour before he’s to give his speech.
Once again, all the usual suspects come by, including Woz, Chrisann, and Lisa, and once again he tussles with them, this time with a little more humility because of some of the failures he’s been through. He’s also a little more accepting that Lisa is his daughter, but not all the way there.
Once again we get another flash-forward. This time 10 years goes by, and Jobs has been asked to come back to Apple. Once again he’s prepping for another big announcement – this one the classic see-through model that changed the game for Apple – the iMac. Once again he tussles with people before the presentation.
Lisa is now 19 years old, and he’s cut off her tuition to Harvard because of how much he hates Chrisann. Chrisann has repeatedly, throughout her life, milked Jobs for money under the guise of raising her daughter, and then spent the money herself. And he’s had it. When Lisa comes to talk to him, they finally have it out, everything is thrown on the table, and Jobs has to decide what kind of man – or actually – what kind of FATHER he wants to be. And that choice isn’t just going to affect his relationship with his daughter. It’s going to affect who he is for the rest of his life.
So yeah, you read that right. This movie takes place in three auditoriums before three presentations and lasts 177 pages. In classic Sorkin style, it is ALL dialogue. And that makes things read a little faster than the ginormous 177 number would indicate. But man… I mean…
I REALLY wanted to love this because I respect the hell out of a writer who’s not willing to rest on his laurels, really put himself out there, and just go for it. This is why Sorkin won an Oscar. He’s fearless. But as I talk about today in my Scriptshadow article, taking risks results in either big rewards, or big failures. There’s rarely an in-between.
Here was my issue with “Steve Jobs.” The sequences were too similar. We jump from waiting for a presentation to waiting for a presentation to waiting for a presentation. And these sequences range from 40-60 pages each! It just became too repetitive and even if you’re a dialogue master like Sorkin, it’s hard to keep something fresh if the format is never changing.
Don’t get me wrong. I know the script is really about the evolving relationships with the characters. But to be honest, the only real interesting relationship was the one with his daughter. All the other relationships are pretty bland. I mean the one with Woz, which takes up about 25 pages total in the script, amounts to “Can you please mention the Apple-II team when you introduce the Mac?” I understand that there’s a little more going on in this exchange but we get the gist by the second page of their argument. Yet we still have 23 more pages to go.
On top of all this, Jobs is a tough character to like. And as you know, if we don’t like the main character, it’s really fucking hard to commit to his journey for 177 pages. I thought about this a lot – because in many ways, Jobs is similar to Mark Zuckerberg, who Sorkin famously chronicled (and won an Oscar for) in The Social Network. They’re both selfish ego-driven workaholics.
But there’s one key difference between them. Mark Zuckerberg actually created something. He built Facebook. And he stood up tall to the entitled bullies trying to take his money for doing so. As is made very clear in “Steve Jobs,” Jobs didn’t create anything. He didn’t build a computer. He didn’t code the operating system. He was just a glorified pitch man. Combined with him being a total asshole, compounded by him rejecting the existence of his own daughter, it was too much to overcome. I just couldn’t root for the guy.
The golden rule for likability is that you don’t need your hero to be likable as long as he’s interesting. But Jobs isn’t interesting. He’s just a selfish prick.
So now you have a 177 page screenplay, an unlikable main character, and a structure that repeats itself. Can I have an extra order of eggs with those impossible odds?
I will say that I liked the last sequence when Lisa was grown up and finally able to battle her father on the issues he’d had with her. It was the first time the script really came alive and a lot of that had to do with there being no easy answers. Chrisann had leached money off Jobs under the façade of helping her daughter, then repeatedly used the money for herself. When it was time to sell the house Jobs had bought for Chrisann, she sold it for 500 grand, 1 and a half millions dollars less than it was worth, presumably to spite Jobs. And Lisa had helped her do it. So now Jobs was just supposed to fork over her Harvard tuition? There were so many emotions and so much betrayal and frustration wrapped up in that money that he couldn’t allow himself to do it. That led to the sweetest moment in the screenplay, where he finally realizes that this is his daughter and he has to do whatever she wants. There was no right or wrong in that. And in this way, we finally see Jobs grow.
But the overall experience here, while ambitious, is too muted. I don’t know if this is a movie so much as a play. And even as a play, it’s long and repetitive. I will say this. Sorkin was tasked with a tough job. I tried to read the Steve Jobs biography and holy shit is it dry. And I’m sure Sorkin read it and felt the same thing. He said to himself, “The only way this is going to work is if I do something radically different.” And so he gave it a shot. Unfortunately, the shot didn’t pan out. It’s a noble misfire but it’s still a misfire.
[ ] what the hell did I just read?
[x] wasn’t for me
[ ] worth the read
[ ] impressive
[ ] genius
What I learned: Today’s script is a great example of “leading.” Take the opening sequence. We set up the speech where Jobs will introduce the Mac in half an hour. So the entire 30 minutes prior to that speech is LEADING somewhere. Take the leading element out (the impending speech) and just have Jobs talking to people without an impending presentation, and we lose interest. Why? Because we don’t know where we’re going. “Leading” gives the audience something to look forward to. In the process, it helps us concentrate until the leading element arrives.
What I learned 2: The power of villains – In The Social Network, Sorkin creates villains, the Winklevoss twins, which allows us to root for Zuckerberg, despite Zuckerberg being a hard-to-like guy. In “Steve Jobs,” Jobs is the villain. I think that’s why we’re never really on board with him. This would’ve worked a lot better if there was a truly evil adversary Jobs needed to defeat.
Genre: Horror-Comedy
Premise: (from IMDB) Three scouts, on the eve of their last camp-out, discover the true meaning of friendship when they attempt to save their town from a zombie outbreak.
About: This script somehow made the 2010 Black List. It has steadily moved through the system, securing actor Tye Sheridan (Mud) and director Christopher Landon (Paranormal Activity: Marked Ones). It was written by comedy team Emi Mochizuki and Carrie Lee Wilson, whose only previous credit was the 2008 Martin Lawrence film, College Road Trip. The movie hits theaters later this fall.
Writers: Emi Mochizuki and Carrie Lee Wilson (the production draft you see in theaters was rewritten by Christopher Landon and Lona Williams).
Details: 114 pages (2010 draft that made the Black List)
Boy Scouts Vs. Zombies was one of the last of the zombie wave of scripts to sell back in 2010. You have to remember that this was during a time where a script titled “Zombie Baby” sold. A 2010 zombie spec was the equivalent of a lottery ticket. It was the trend that wouldn’t stop trending, kind of like biopics today.
Still, this specific sale has always baffled me. There’s nothing inherently clever or ironic about the premise. It’s so arbitrary, it’s as if they picked a random group of people, said, “Let’s pit them against zombies,” and that was it.
It’s no different from “Clowns vs. Zombies,” or “Politicians vs. Zombies,” or “Skaters vs. Zombies.” There’s no clear connective tissue between this group and the undead.
“Grocery Store Employees vs. Zombies!”
Yet still they managed to get one of the hottest young actors in Hollywood to join the film. What’s up with that?? I mean this guy was in Mud and Tree of Life. Was his agent high when he read this? “Okay Tye, you’ve worked on some pretty impressive stuff so far. But I found something can’t-miss. Are you ready for this? Boy Scouts. Vs. Zombies. Waddaya say?”
All of this supports my belief that the way things get made in this town is passion. This is the furthest thing from a quality project, yet clearly, somebody believed in it and put all of their effort into pushing it through the system. If you want to know why bad movies get made, this is why. Bull-headed producers who stop at nothing to get that theatrical release.
The “plot” to Boy Scouts vs. Zombies has our core crew of boy scouts, each 14 (there are 14 year-old boy scouts??), heading to the island of Playa Del Amor to engage in some weekend boy scout tomfoolery.
There’s Dylan, the cool one, Matt, the proud one, Lloyd, the geeky one, and then a few other human versions of Swiss army knives. The group is led by asshole assistant scout leader, Scott, and “takes this way too seriously” scout leader, Gary.
Little does the group know that on Playa del Amor, there’s a hidden research facility, and that some guy who works there named Carlos just got infected with the zombie virus. Carlos is able to escape from the facility, where he then mauls a few campers.
“Lawyers vs. Zombies!”
As Dylan, Matt, and Lloyd finalize plans to invade a high school house party (I guess there’s a high school on this island??), their plans are interrupted when some local islanders try to, well, eat them.
Unlike most zombie movies where the main characters don’t know what zombies are, our group is well-versed in zombie lore and know that they must get the hell off of this island or embrace an afterlife of animated rotting flesh. Unfortunately, they have to rescue some girl scouts first, and that’s where everything falls apart.
Boy Scouts vs. Zombies lies somewhere between Goonies and Piranha 3D. It wants that pure B-movie wackiness of Piranha, with a bit of the “kids in danger” heart that drove Goonies. And that’s its problem. Because it tries to be both, it does neither well, and what’s left is its surface-level infatuation with introducing zany zombies.
For example, someone gets bitten inside one of those blow-up sumo suits and becomes “sumo zombie.” And hey, that’s a fun idea, sure. But if all you’re doing with your zombie film is trying to come up with fun zombies, you’ve failed. I’m sorry, but you’ve failed big time.
Screenplays are supposed to be about characters. Connect us with the characters by making them relatable, by giving them flaws we can identify with, and then create problematic relationships (which are also relatable) that need to be resolved. Even if you only achieve the bare essence of this, you’ll probably make us care.
We don’t get that here. There’s a half-assed storyline where Matt is going to private school, leaving his best friend Lloyd all alone, but you get the feeling that the writers cared about that relationship 1/10th as much as they cared about sumo zombie.
And make no mistake. The audience feels that. They feel when you don’t give a shit about your characters.
“Pizza Workers vs. Zombies!”
Speaking of characters, there’s something that’ll happen when I read a script that’s a dead giveaway that I’m reading a bad writer.
As any script reader will tell you, sometimes you forget a character. Maybe their intro sucked. Maybe there were too many characters being introduced together and they got lost in the mix. Whatever the case, I can’t remember the character when his name is brought up again, which leaves me scrambling to figure out who they are.
Now if you’re a good writer, your character will speak and act in a way that’s so unique to them, that I’m able to pick up who the character is without having to go back and re-read the intro. This is ESPECIALLY true with comedy, where characters are exaggerated.
There’s a character named “Jim” here, who’s apparently a main character, whose introduction I missed. Every time he showed up in a scene, I’d try to remember who he was. But because his dialogue and his actions were so generic – because there wasn’t anything unique about what he did or said (or how he said it), I never knew who he was. He was a bland blob for all I knew.
This is important. Your character intro should not be the sole thing conveying who your character is. He/she must continue to act/speak in a unique enough manner that we’re able to identify them regardless of their introduction. In fact, we shouldn’t even have to see their name to know who they are.
“Truck Drivers vs. Zombies!”
Take a script like The Hangover. If you missed Stu or Alan or Phil’s intro, you still would’ve known who those characters were based on their words and their actions. Alan with his complete lack of social awareness, Stu because of how freaked out and OCD he was. Even the blandest of the three, Phil, was a narcissistic asshole who just wanted to have a good time, and that was evident every time he spoke.
You barely see any of that here.
And the script doesn’t even do a good job in the one area it cares about – the funny. There’s one memorable scene, when the group is attacked by a bunch of zombie bunnies. But other than that, it’s sumo zombies, bikini-girl zombies, and Chuck Norris jokes (yes, the second lowest joke on the joke totem pole, right above a fart).
In the end, I think this boils down to a flawed premise. Why a zombie movie about boy scouts? It’s too random – the kind of logline that wouldn’t have even made the Top 250 of my contest. Where’s the clever? Where’s the irony? I’ll be honest. I’m baffled this script was A) picked up and B) made. This freaking movie is getting a theatrical release! Can someone explain this to me??
[ ] what the hell did I just read?
[x] wasn’t for me
[ ] worth the read
[ ] impressive
[ ] genius
What I learned: Let’s say a law was passed that prevented you from writing traditional introductions to your characters (“JOE, 20, is a space-cadet with a penchant for pinball”). Would your characters still be identifiable based on their actions and their words? If not – if you NEED your character introduction to do all the work for you – it means you’re not focusing hard enough on expressing your character through action and dialogue.
“Dog Walkers vs. Zombies!”
