“I hate this!! Please change.”
True story: I once opened up a client’s project document to find these immortal words hovering over paragraph one of a 2000-word blog post.
Reader, I don’t mind telling you that a teeny tiny piece of my soul withered away that day as I questioned my entire career choice thus far.
I’d worked so, so hard on every single paragraph, every line, every word. And yet, the client hated it. I was going to have to scrap it, start again, rewrite every word through a film of tears.
Okay, I’m exaggerating. But I was pretty freaked.
Not just because I felt like I hadn’t done a stellar job, but because I didn’t have the first idea how to fix the problem.
Until I found out that the client didn’t actually hate the entire post. They just didn’t like one word that I used in the intro because it reminded them of an annoying catchphrase their high school nemesis used to have. All I had to do was switch out that one word and — boom — a perfect post they couldn’t wait to publish.
And that’s the risk inherent in the feedback stage of a writing project.
Feedback delivered in the wrong way won’t just crush your writer’s soul a little. It’ll leave them feeling confused about what you actually want and reduce the chances of them delivering a final draft that you absolutely love.
So here are 5 things to consider when providing feedback on a first draft.
-
Take your time.
Quick story about a website project I worked on a few years back. During our business deep dive meeting (more on them here), the client said something really interesting about their approach to business that stuck with me. I used it as a springboard for the entire concept of their web copy but when I delivered the first draft on a Friday afternoon they weren’t sure. It was totally unexpected and they later told me that their first instinct had been to tell me to start again.
But their partner liked it and told them to sleep on it. So they did. And by Monday morning, they’d emailed me to tell me they absolutely loved the concept. It was unexpected…but it worked! And they were going to use it not just on their website, but throughout their branding!
So two points here. The first: thank fuck for that client’s partner! And the second: be wary of knee-jerk reactions. Give yourself time to go through your copy. Always, always read it from the headspace of your potential readers rather than from your own point of view.
And know that sometimes the unexpected is exactly what you need.
-
Cover the big stuff first.
Most writers will include a couple of revision rounds in their quote.
The focus for the first round of revisions should be the big stuff — the conceptual stuff, the structure and flow, any glaring omissions or things you think maybe shouldn’t be in there or should be moved to a different page or different section.
You can also mention any words or phrases that don’t you don’t love, anything that you think just doesn’t sound like something you would say, or anything that stands out as being not right for your brand.
That way, your writer can work on getting the second draft pretty close to perfect before using the final round(s)of edits for tiny tweaks, like clearing up typos that snuck in during the editing process or refining any of the phrasing that you’ve been noodling over.
-
Be specific.
Over the years, I’ve had more than one comment along the lines of “I hate this part.” And that’s fine: you’re allowed to hate things. In fact, if I’m writing multiple pages for you, or creating documents thousands of words long, you’re not going to love every single bit.
But here’s the thing:
I can’t work with feedback like “I hate this”. Because it’s just too vague. I need to know WHY you hate it. Is it just that it’s not a word you’d be likely to use? Is it likely to have connotations for your reader that I’ve missed? Is there something about a certain phrase that grinds your gears, even though you can’t explain why?
If you let me know what the problem is I’ll know how to fix it. And I’m far less likely to switch it up for something you’ll hate just as much.
It’s also important that you highlight which bits, in particular, you don’t like so I know whether I need to edit just one word or a whole paragraph or section.
Also useful: let your writer know if there are bits you really love about their work. Knowing that a particular phrase made your heart happy helps direct how we approach not just the rest of the edits on this project, but the work we do on future projects together.
So be specific in your feedback (because your writer isn’t a mind reader!).
-
Be timely.
It can be hard to estimate how long edits are going to take — if you loved 99% of the first draft, your writer could turn things around in a day. If you need huge structural or conceptual changes, it’s going to take longer.
Respecting the timeline your writer gave you for providing feedback will help them deliver the final draft in time to hit any launch deadlines you’re aiming for.
-
Be kind.
You’ve paid a lot of money for your copy or content — and you deserve to love the results.
But remember that there’s a person behind the document. A person who worked really freakin’ hard on your project. A person who isn’t just willing, but supremely capable of fixing things you don’t like.
So be kind when giving feedback. For the most part, writers develop fairly thick skins over the years. Writing is so subjective we kinda have to. But unnecessarily harsh feedback can dent the confidence of even the most self-assured of writers. And it’s without a doubt the quickest way to kill both a writer’s creativity and your chance of getting a stellar final draft!


Leave a Reply