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.
