Taming the beast we all must face

lion 2
Intimidating at first, but eventually, just a big ol’ pussycat

When I was part of a writing group last year, each week we would read and critique a few members’ sets of pages. Some were just starting out, some had a few scripts under their belt, and some had been doing this a while. You can probably figure out which category I fell into.

Simply put, some of the writing just sucked. Really sucked. Like painful-to-listen-to sucked. To my credit, tempted as I was, I never actually expressed my thoughts that way.

I fully understood that not everybody had a firm grasp on the basics, and I, along with a few others, made a sincere effort to explain what would help improve their work. While a majority were appreciative of our comments, a select handful got defensive, some even to the point of flat-out dismissive, of any kind of comment that didn’t reinforce their belief that their writing was fine just the way it was.

This was one of the things that helped me decide to leave the group.

One of the universal truths about being a writer is that not everybody’s going to like what you’ve written, and just about everybody will have a suggestion as to how it could be better.

While there’s nothing you can do about the first part, the great thing about the second is that it gives you options. A lot of them. You like what this person said? Use it. Don’t like what that other person said? Ignore it.

Some people will make suggestions based on how they would do it, which is all well and good, but what’s more important is how you would do it. Do you agree or disagree with what they’re saying?

You’ll be bombarded with a wide variety of opinions, but don’t feel like you have to incorporate every single one. And while you may be the final word on what works and what doesn’t for your story, you shouldn’t dismiss every suggestion either. Some of them may be more helpful than you realize. There are a lot of  writers out there with more experience than you, so their opinions should be at least taken into consideration. But it’s okay to disagree with them, too.

Speaking from experience, it takes time to learn not to take criticism of your material personally. The comments you receive may sting at first, but you have to remember they’re about the material, not you. Read them with a “How can I use these to get better?” frame of mind. That’s the only way you’re going to improve.

One last thing – make sure to thank the person for giving you notes, even if you totally disagree with everything they’ve said. Doesn’t matter if you asked them to do it or they offered. They took the time to help you out, and the least you can do is acknowledge that and express your appreciation for it. And it’s the polite thing to do. Manners still count.

An education most painful

scared
Please don’t make me watch that again!

Once again, your stalwart author makes the necessary sacrifices so you don’t have to.

This time around, I had the misfortune of watching an extremely bad large-budget movie from the semi-recent past. It was painfully obvious that a larger percentage of the budget should have been diverted to hiring quality writers, rather than on everything else. A pipe dream, I know.

But trust me. It was bad.

What made it so bad, you may ask?

Oh, where to begin.

My biggest problem was that too much of the story felt glossed over, with vital elements explained in a very lazy and haphazard way, if they were even explained at all. It felt like they were trying to force events to match how they wanted the story to play out, rather than deftly setting things up.

Reasons why something would happen, or were supposed to have happened, seemed to have simply been thrown against the wall, and whatever stuck, that’s what they went with. Did it matter if it fit within the context of the story?

Nosireebob.

Once again, there were too many questions raised that were never sufficiently answered. When this happens, it simply takes away from the movie-watching experience. The only reason I knew the film had to have been around the midpoint area was because of its running time, and NOT because of what had transpired over the course of the story.

I could say I had a vague inkling of what was supposedly going on, but was just never sure, since the story was being told in a very sloppy and unorganized way. It irked me to no end to be see such terrible writing so prominently displayed. And apparently I wasn’t alone in my opinions. The film was a major flop at the box office.

So what silver linings can we extract from this pitch-black cumulonimbus that stole away just under two hours of my life?

-Write a story that’s easy to understand. Keep it simple. This doesn’t mean dumb it down. Keep us informed, unless withholding that information is absolutely necessary.

-Let the story play out organically. Don’t try to force it because that’s what you want to happen. It’s easy to tell when that happens, and it ain’t pretty. If you didn’t put in the effort to figure it out, why should we?

-Have things happen for a reason. “Because it looks cool” is not one of them. Would it drastically change things if it didn’t?

-Set up, pay off. If something happens, we want to see what happens as a result. Don’t leave us hanging. And counter to that, don’t suddenly spring something on us out of thin air. It reeks of desperation. Audiences don’t like that, either.

One of the things I always strive for in my scripts, be they big or small budget, is to respect the intelligence of the intended audience. That is one lesson I believe the writers of this abomination should have kept in mind.

Flashing back in less than 12 parsecs

The big project continues, but I’m definitely in the home stretch now. Feeling very confident and rejuvenated about wrapping it up in the next couple of days. Planning to offer up all the sordid details once it’s completely finished.

While all energies are focused on that, here is another throwback post from a long time ago in a galaxy not so far, far away. From me, anyway.

And yes, I still have the t-shirt and chopsticks.

K’s Advice on Supporting the Writer

11333911 - retro secretary
More Than Your Average Support Team

As mentioned previously, I’m up to my eyeballs on two big projects through next week. My wife K suggested – begged – to provide a guest post this week. So, without further ado…

Regular Maximum Z readers know Paul has been at this for a long time. While he comments regularly on what it’s like to be a screenwriter and what is happening in the filmmaking world, he’s never addressed the world around him. As the long-time significant other, it’s my chance to give advice that you can choose to subtly share with those around you.

Although every creative couple is different, after 25+ yrs together, there are definite hits and misses of how to support your partner/spouse or guy/gal who writes.

They are:

First and foremost, they are the writer. Unless you are invited to give notes, you are NOT part of the writing process. It may be killing you inside, but no matter how much you just know it should be written differently, it’s not for you to say. I will confess there’s one script of Paul’s that my only feedback was: did you mean to make the protagonist look like an idiot in this scene? Yes, it was less than constructive notes, but I did wait to be asked.

Which leads to the second bit of advice: if you are invited to give notes, don’t be an asshole about it. The screenwriter is already getting that from so many others, including their own self-doubt. There is what should be an obvious line between giving feedback and ultimately rewriting a script to match what’s in your brain.

Rule of thumb: if you aren’t going to get WGA credit on the script, you shouldn’t be adding enough to have warranted it.

Third, know their writing schedule and style. Does your writer want breaks or is it heads down at the laptop until rewrites are complete? There’s a scene from TRUMBO where Bryan Cranston writes sitting in a tub. He yells at his teenage daughter for bothering him to mention they are singing Happy Birthday to her. Luckily, Paul doesn’t take his laptop into the tub, but we have arranged for the dog not to visit her favorite human when he’s at his desk.

My fourth suggestion is probably the hardest and most controversial. Don’t say “I know you will be successful.” Or, “it will happen with this script, I just know it.” No. You don’t know it.

In Jim Collins‘ book From Good to Great, he talks about the difference between being confident and being an optimist. The gist of it is the optimist believes so much that things will work out in the universe if they believe hard enough. That is a recipe for disappointment. In contrast, being confident in someone’s ability means that you believe they have the ability to do what they’ve set up to do.

That means for as much as I know I’m married to a talented writer and for as much as I love him to pieces, I can’t promise him it will work out. It hurts, but it’s the truth. I do know that if he continues to work as hard as he does and shows his scripts to the right people, he has the ability to be successful.

Ultimately, that’s the rub. We love ’em. We support ’em. Now, we need to get out of their way.

Bye for now.

-K

No, I’m making all of this up

And here's another reason why you're wrong!
The louder I yell, the more you’ll agree with me

It’s probably safe to assume you’ve found yourself in this situation before:

A colleague asks you to read their material and give your thoughts on it. “Don’t hold back,” they say. “Be as brutal as you need to be. I can take it.”

So you read it, compile your notes (making sure to be critical, but fair and helpful) and send them off. Most of the time this results in one of two ways.

1. “These are great! Thank you so much!”

Or…

2. “What do you mean ____? How could you miss that? Did you even read the script?”

Urgh. I hate, hate, hate when they say that.

Did you want notes or gushing praise? You asked me for the former, but it sounds more like you secretly meant the latter, and now you’re not happy with the results.

If I think your script is good, I’ll say so and tell you why. On the other hand, I also won’t hesitate to point out what I think needs work, or if there’s something I didn’t understand.

There’s no need to remind me how much you’ve slaved over this for months/years, but I’m not going to say it’s good just to make you feel better. You know every single aspect of the story. I don’t, and only comment about what I can (or can’t) see on the page in front of me.

This doesn’t mean I’m a bad reader. Have you considered the remote possibility that your writing just might not be the perfection you think it is? I’ll fetch the smelling salts while that one sinks in.

Believe me, I’m not saying these things to be mean. You asked me for my opinion, and I gave it to you. There are professional analysts and consultants who do the exact same thing, and you’d pay them for it. Not everybody is going to love your script or pick up on every intricate detail you think is painfully obvious to any moron with half a brain.

If you put your script out there for review, you’d better be prepared for the worst. It’s an unfortunate part of how this works.

And one more important piece of advice: getting defensive or arguing with me because I didn’t like your script or “just don’t get it” isn’t going to change my mind, and will definitely make me not want to do this for you again.