Collaborating with a Non-Writer/Editor

Image by Alejandro Escamilla via Unsplash.

In my limited time as an editor, I’ve learnt two things: editing writers is hard, and editing non-writers is really hard. Editing always comes with its challenges, but they’re tenfold when the person you’re editing isn’t a writer.

Recently, I collaborated on two projects with some photographers, neither of whom was a confident writer and both of whom needed lots of guidance. The process was tough, but ultimately rewarding: there’s nothing like working hard and seeing the final product in print.

Below is a list of things I wish I’d known before I started, which I believe are helpful to anyone collaborating with a non-writer and/or -editor.

1. Set expectations early on: this isn’t your usual editor-writer relationship—in fact, the person you’re working with may not even know what an editor does. The earlier you each outline what you can and are prepared to do, the better. This may not match up initially, but don’t worry—collaboration is all about negotiation. I went into my project expecting to edit and not write, but both of my collaborators outright said they weren't writers. This threw me off, but through a discussion we were able to come to an agreement (we would work together on the writing, and I would edit). It’s best to sort this out as soon as possible, and don’t forget to make a record of it—you don’t want any confusion down the track.
2. Set deadlines: many projects fall apart at the end, purely because everything was left until the last minute. Even if you believe you work best this way, it simply can’t work in a collaboration: there’s somebody else relying on you too. Therefore, deadlines are your friend. Agree on them with your collaborator and do your best to stick to them. Estimate how long you think a job will take you, and allow yourself a little extra time—it’s always best to overestimate how long something will take than to underestimate. If you know that you have underestimated, let your collaborator know as soon as possible—if you have to push back your deadlines, they probably have to too.
3. Be prepared to compromise/renegotiate: sometimes, things don’t go to plan (in fact, they rarely do). That’s okay; the only time it isn’t okay is when you aren’t prepared to roll with the punches. While it’s best to set your expectations and deadlines early on, you have to make them flexible enough that if something unforeseen arises, you have the time and resources to deal with it. Roles might shift, deadlines might change, and it’s very easy for a project to go down hill if you aren’t prepared to shift with them.
4. Tailor your approach: it’s easy to forget, when you’re used to working with writers and editors, that a lot of the language we use doesn’t make much sense to non-writers and -editors. Make sure to use language that your collaborator can understand, and foster a relationship so they’re comfortable telling you if they don’t (which, I admit, is easier said than done). This also applies to the actual editing; if you’ve never learnt editing mark-up it can seem like a foreign language. Discuss these challenges with your collaborator, and come up with an approach that works for both of you.
5. Use your resources: chances are that if your collaborator isn’t a writer and/or editor, they’re not going to have many thoughts on whether the textual dashes should be ems or ens, or whether something should be in italics or quote marks. That’s not to say that they definitely won’t, but if they don’t, just leave it. It won’t be useful for either of you to bog them down in minute details and confuse them. Instead, create a style guide, and use your editing resources—dictionaries, style manuals and, most importantly, your peers.
6. Try to make your writers comfortable — remember, this is not what they do: it can be daunting to do something new, and even more so to share it with an expert. Don’t forget that your collaborator isn’t a writer, and that they may not be confident writing. Encourage them, let them know when they’ve done well, and remind them that it’s okay if something isn’t perfect; after all, that’s what you’re there for—to edit.
7. Take it one step at a time: don’t get ahead of yourself. If you get caught up in everything you have to do at the beginning of a project, you’ll never get anything done. Instead, take it one step at a time, and deal with any problems if and when they arise. Though it may be hard in the moment, try to remember that if something is difficult, particularly if it’s something new, it means you’re learning something. If everything were smooth sailing all the time, none of us would learn anything. Anything and everything you do in a project will help you in the future (even if it’s what not to do), and though it may be stressful and at times even feel impossible, nothing beats the feeling of finishing a project and seeing the final product.