So, I’ll be running a new series on B2W, this time “Top 5 Mistakes”. I’m kicking off with Feedback and will be following up with my top 5 mistakes on Submissions. Have an idea for another in this series? Then let me know in the comments, on Twitter or via email.
First off then, here’s my top 5 mistakes on GIVING feedback – Enjoy … and BEWARE!
1) Highjacking Another Writer’s Vision
Look, we get it – it might seem OBVIOUS to you how the story has missed opportunities, or that writing a story *that* way just doesn’t work. But writers may be too close to their work, which is why they’re asking for your help, not your condemnation.
Equally, just because YOU think your idea for the story works, doesn’t mean the writer will. Your job is not to give solutions per se, but provide a springboard for the writers’ OWN ideas, remember. MORE: 6 Things To Remember When Dealing With Writing Feedback
2) Forgetting writing is about DEVELOPMENT
No one can write a first draft that’s top notch straight off the bat. NO ONE. Sure, some first drafts are better than others; plus some will be absolutely awful. It’s not your job then to express surprise or disappointment that the draft is not “better”; it helps no one, least of all the writer. In fact, it’s demotivating. Besides anything, it makes no sense to do this, because *any* draft can always be BETTER. That’s what development is for! MORE: How Do You Script Edit Without Rewriting It As Your Own Story?
3) Thinking your job is to FIX writing
We’re back to number 1 on this list again, essentially. Opinions on what “works” and what “doesn’t” are just that – opinions. There are multiple ways of looking at story and characters and forgetting that is a huuuuuuuuuuuge error when giving feedback.
But more than this, the best feedback-givers FACILITATE writing, they don’t “fix” it. They go beyond what is solely on the page and motivate the writer, encouraging them to connect with both their talent and grit, to get their best work done. What’s not to like? MORE: What Script Editors Do AKA 5 Tips To Edit Your Own Screenplay
4) Not having the vocab to explain issues
There’s a reason new feedback-givers focus on little niggly things like Format, such as HOW the script looks on the page.
They may also focus on strange little details to do with the story – random, tiny moments, as opposed to elements that might actually DEVELOP the story and its characters.
Put bluntly, this is usually because the feedback-giver doesn’t know what s/he is doing. Sure, we all have to start somewhere, but if you want to be taken seriously as a script reader or editor? You have to get the skillz – and QUICKLY.
This means, you have to understand how structure and character works, STAT. And no, I don’t mean reading a single book on structure; I mean IMMERSING yourself in the subject. And no, I don’t mean talking about character “tropes” and how terrible they all apparently are – I mean character motivation vs role function (and that’s just for starters!).
5) Forgetting these are people’s hopes and dreams
It comes down to this: if you’re a writer, you’ll probably know how much vitriol and rejection can sting. Do as you would be done by.
But okay, maybe you’re one of those thick-skinned writers, or perhaps you don’t write yourself. So think on this, instead: yes, the work in front of you might be awful in your opinion. But someone worked hard on it, sacrificing time, money and more to do it.
These are not just spec screenplays and unpublished novels; these are people’s hopes and dreams. Forget that at your peril. MORE: How Do I Become A Script Reader?
My sell-out course, BREAKING INTO SCRIPT READING will be back for its THIRD year in 2017! If you’re interested in becoming a script reader, or finding out more how script readers may assess YOUR own writing – or both! – then this is the course for you. The course will run 11th-12th February and early bird tickets are on sale now. GET THEM HERE, or click the pic on the left. See you there!
Like this post? Then please check out my books, HERE and share on your social media profiles. Happy writing!