From the archives: My brain’s helping hands are ready to go

No job too small! (schedule permitting)

There’s been a slight uptick in my recent coffee chats with connections new and not-so-new. A majority of them have been of a more “just catching up”-type nature, but a few have included the exchanging of script notes and related items. That prompted the re-posting of this gem from July 2018. Enjoy.

Thanks to my ever-expanding network of savvy creative types, I get lots of chances to be on both the giving and receiving ends when it comes to reading scripts.

I consider myself extremely fortunate to be able to get exceptionally helpful notes from a lot of really talented folks. All this feedback has somehow managed to influence my writing for the better, and for that I am overflowing with gratitude.

So the least I can do when somebody asks me “Will you read my script?” or “Can I pick your brain about this idea?” is to say “Of course.”* Maybe I can offer up a few scraps of advice that might somehow work to their advantage. If anything, I can at least point out where a fix in spelling or punctuation is needed. For a script, anyway. That counts, right?

*caveat – it’s taken a lot of work spread over a long time for me to build up my network and establish connections, so I don’t mind if somebody I actually know drops me a note with such a request. If our only connection is being connected on social media and we’ve never interacted – at all, you’re little more than a total stranger to me. So heed that one word and be social. It makes a difference.

I had the pleasure of such an experience this week. I’d connected with another Bay Area creative, and we’d been trying for a while to arrange a face-to-face meeting. After much scheduling, cancelling and rescheduling, we finally made it happen.

This person had an idea for a project, wanted to talk about it, and see if I was interested in being involved. I stated at the outset that I had enough work on my own for now, but would be open to giving notes – time permitting.

After the initial introductions and our thumbnail backstories, we focused on their project. I won’t go into specifics or details about it, because those aren’t the important parts.

What was important was:

-this was a story they’d had inside them for a while, and even though they knew it needed A LOT of work, they were still happy with simply having written it all out

-they were totally open and willing to listen to my suggestions. Some they liked, some they didn’t. Totally fine.

But the more we talked, the more the seeds of ideas were planted in their head. Even though a lot of the details we came up with, including possible paths the story could take, ended up being totally different from their original incarnation, it was easy to see that spark of excitement reignite inside them.

Seeing that happen with somebody you’re trying to help is more satisfying than you can possibly imagine.

We parted ways, with them really rarin’ to go and start developing the latest draft. They added that they really appreciated me being so willing to help out.

I just like doing that sort of thing. I never had that kind of person-to-person help when I was starting out, so why not do what I can for others? Granted, the internet and social media didn’t even exist then, so it’s a lot easier now.

I got a few emails from them the next day showing me what they’d come up with since our meeting. Same concept, but a totally new approach (and, in my opinion, provided the opportunity for a lot of new possibilities). This also included a more thorough write-up of “what happened before the story starts”.

Even though it can be tough to read emotion in text, it was easy to see the spark was still burning strong within them. The way they talked about their plans for what comes next, I could tell they were actually looking forward to working on this.

It was nice knowing I had a little something to do with it.

We exchanged a few more emails (mostly me asking questions about story and characters and them providing sufficient answers), and I wrapped up with “Keep me posted.”

Their response: “Definitely. Thanks again. You’re a good dude.”

That was nice too.

Thank you for the positive reinforcement

Got some notes back on the animated fantasy-comedy spec.

I’ll be the first to say it still needs work on a few fronts, but the overall consensus is “I really enjoyed it”, which means a lot. On several levels.

Added bonus: they liked the jokes. Always great.

Despite all this, for as long as I’ve been at this, I still feel a twinge of anxiety as I open the email to see what the reader thought.

Impostor Syndrome? Possibly.

I know I can do the work, but there’s always that hidden fear that somebody’s going to say “wow, does this suck”. I suppose it stems from that initial sense of just hoping the reader likes it.

While it’s great to get notes of a positive nature, I tend to focus more on the sections that deal with what didn’t work or needs work. Every writer wants their script to be the best it can be, and notes of a critical nature can be invaluable in helping you get there.

And a lot of the time I find myself agreeing with what the notes have to say. Sometimes they even help me navigate my way out of a problem I already knew was there, but was having trouble finding a solution. Those are fantastic to get.

Even as I wait to hear from a few more readers, I’ve already started jotting down ideas to incorporate the strongest suggestions from this batch into the next draft.

Which I will then send out, once again thinking “I hope they like it.”

-Just a friendly reminder that my two books – GO AHEAD AND ASK! INTERVIEWS ABOUT SCREENWRITING (AND PIE) VOL 1 & 2 are available on Amazon and Smashwords.

Reading: good and good for you

Wrapped up reading for a contest earlier this week. Happy to have helped, but it was exhausting.

And a good percentage of the writers could really benefit from this recent post.

Now that that’s out of the way, I can return to devoting more time on a few of my own projects, as well as start getting to the scripts in my “to read” queue.

I’m really looking forward to both, and especially the latter.

Some were sent with a request for notes, others were “thought you might enjoy this”, and the rest were ones that got my attention with the logline or the concept.

I’m extremely fortunate to have a professional relationship with a lot of these writers, and many of them are great writers to begin with, so it’s a pretty sure bet their scripts will also be of exceptional quality. And those are always great to read.

It can’t be stressed enough that reading scripts helps a writer become a better writer. So take it upon yourself to start making that a regular practice.

You’ll be glad you did.

And speaking of reading, my new book GO AHEAD AND ASK! INTERVIEWS ABOUT SCREENWRITING (AND PIE) VOLUME 2 is now available in paperback and ebook here and here. It makes a great companion piece to Volume 1, and Volume 3 will roll out a little later this year.

Notes: givin’ ’em and gettin’ ’em

Simply put: notes can help make a script better. This also heavily relies on several factors, including the experience level of the person giving the notes, the notes being of high quality, and the relevancy of the notes in relation to the script.

I’ve had the recent experience of being on both sides, and both proved to be extremely helpful on several levels.

First: the giving.

I’d been invited to take part in a group Zoom call giving notes on a new script from an established writer-producer.

I thought the writing was okay. Nothing stellar.

As the call progressed, the comments seemed to go back and forth between honest, critical feedback and flat-out gushing. Were those doing the latter doing that in order to get in the writer’s good graces? I hope not.

When it was my turn, I started with what I liked about it (the characters and the strong establishment of tone, in particular) and then segued into what I thought could use some work, which was mostly tightening up the writing, and trimming scenes or sequences.

Just to clarify – I wasn’t trying to tear anything down; just offering some suggestions of what I thought could help make the script better.

The writer appreciated my positive comments, but the other ones were met with a lot of “well, these other people I work with in the industry LOVED that” or “Nobody else mentioned that. This doesn’t mean you’re wrong; just in the minority.”

I’m not really the biggest fan of a writer who gets defensive when they get notes. It’s what they asked for. I don’t have a problem if you disagree with what I’ve got to say. Just say thanks and move on. Don’t try to make me feel small or wrong. If you wanted praise for your script, you should have started with that.

I had to hop off the call soon after that for work-related business, so don’t know how the rest of it went. While I’m slightly curious if any of the other participants had a similar experience, I’ve no pressing desire to find out.

Despite this bump in the road, I still enjoy giving notes and will continue to do so; maybe just a little more selectively.

Second: the getting.

A few weeks ago, I wrapped up the latest rewrite on the animated fantasy-comedy spec. My usual m.o. is to contact a few colleagues to ask their availability to give notes. This time, I opted to keep the number even lower and asked two.

Still waiting to hear back from one, but the other sent back a thorough set of notes. They explain what worked for them, what didn’t, and ask a lot of questions centered around the story and the characters.

It was my intent to get notes that would help make the script better, and that’s exactly what these are – and what I need. Yes, it would be great for someone to say what a fantastic script it is, and how much they loved it, but that’s not going to help improve the script, or why I asked them to read it.

An outside pair of eyes is more likely to see things that I, as the writer, might not. How could I argue with that? Maybe there’s something in there I don’t initially agree with, but would still want to know why they said it – the “note within the note”.

Getting solid notes from those within your network of writers can be a priceless resource, and hopefully you’ll be able to reciprocate with the same level of quality.

Let’s start with the basics

I’ve been reading for a contest these past few weeks.

It’s a safe bet to say that a lot of the writers who entered may not be as familiar with how to write a screenplay as one would expect.

This, in turn, inspired some helpful suggestions for any writer to keep in mind:

-SHOW, DON’T TELL. Convey the information in as visual a way as possible.

-GET IN LATE, GET OUT ASAP. Get to the point of your scene as quickly as you can, then move on to the next one. Don’t have the characters chitchatting back and forth for another page.

-GET THINGS MOVING. Get us into the story from the outset. Keep the momentum going.

-EVERY SCENE NEEDS CONFLICT. Two opposing forces; anything from a subtle gesture to an epic battle.

-INVEST IN SCREENWRITING SOFTWARE. It makes a huge difference to write something in Final Draft as opposed to Microsoft Word. This can also help with..

-FORMATTING IS IMPORTANT. If you’re not sure how a script should look on the page, there are tons or resources online with good examples. You can also read some other scripts to get an idea.

-DO YOUR RESEARCH. Fleshing out a story or characters with relevant info adds to the authenticity of the material. Don’t go for the information dump; use what’s important/necessary.

-SPELLCHECK IS NOT YOUR FRIEND. There’s no ‘e’ in ‘lightning’, nor should somebody ‘waist’ an opportunity, just to name two.

-THE THESAURUS IS YOUR FRIEND. Mix it up. There are 142 alternate words for “walk”.

-CHARACTER INTROS. Describe their personality, rather than just their height & appearance – unless either plays a part in the story. Also, their name in ALL CAPS only when they’re first introduced; NOT every single time after that.

-“HOW DO WE KNOW THAT?”. Action lines are for describing what we’re seeing transpire onscreen (i.e. action), not explaining why something’s happening, why somebody’s doing something, or what something really means. Find a way to get that across visually, or through dialogue.

-KEEP IT BRIEF (or WRITE AS IF INK COSTS $1000 AN OUNCE). While a book may allow for lengthy descriptions, a screenplay needs to be tight. Lots of unnecessary text will slow things down, and an important detail might get overlooked if it’s in the middle of a dense paragraph.

-IS THIS IMPORTANT TO THE STORY? While you may consider it vital to meticulously describe the decor of your protagonist’s living room, or every item of clothing they’re wearing, unless that information plays a part in the story, it’s unnecessary clutter.

-IS THIS HOW PEOPLE TALK? Do your characters talk like real people or like they’re in a movie? Helpful tip – read your dialogue out loud to see how it actually sounds.

-ACTIVE, NOT PASSIVE VERBS. “Bob runs” is more effective than “Bob is running.”

-WE SEE/WE HEAR. Personally, not a fan. If you have to use them, do so as sparingly as possible.

-CAMERA DIRECTIONS. Again, not a fan. I find them distracting. You don’t need to remind us we’re “watching” a movie

These, of course, are just the tip of the proverbial iceberg, but still pretty important to keep in mind.