TECH EDITOR/DESIGNER RELATIONSHIPS
As a new tech editor, I frequently brain storm methods of attracting and keeping designer clients. Regardless of your unique attributes as an editor or your areas of specialization, you must reach out to designers and convince them to sample your services. Equally important, after attracting a designer, you must meet their needs effectively in order to retain them on your client list.
How do you attract and retain designer clients? You find out what they want and expect from their tech editors. How do you do that? You ask.
So I did.
The primary quality designers said they look for in their editors is someone who communicates with them. The primary problem designers said they experience with editors is a lack of communication.
The Good: things designers love in a tech editor
Editors that set clear policies and guidelines. Be upfront about the skill levels you edit and whether you work with beginning as well as experienced designers. Advise designers of your turnaround times, whether you offer follow-up edits after test knits, and if you can create charts and schematics.
New tech editors that recognize they are likely to be slower than experienced TE’S and are, accordingly, willing to negotiate a flat rate fee rather than hourly.
TE’s that take the time to consult with the designer when some pattern element is unclear or confusing.
Editors that also offer positive feedback rather than only emphasizing problematic areas.
Offering explanations of editorial issues—explaining why an item or problem needs attention or needs to be changed.
Willingness to engage in multiple contacts with the designer in order to clarify and edify.
The Bad: things designers don’t love in a tech editor
Editors who don’t respect a designer’s voice and style.
Editors who are not sensitive to the designer’s goal for the knitter in that the edit results in an overly-complicated or overly-simplistic pattern that does not match the skill level the designer intended for their target knitter.
A TE that adds, removes or changes abbreviations, chart symbols, instructions, or explanations without the designer’s okay.
Less than thorough edits with missed editorial issues or problems later found by pattern purchasers.
Not being willing to admit to a missed editorial issue; or, not being willing to rectify it.
Overlong turnaround times; or, not sticking to an agreed upon timetable.
Failure to follow through with a designer’s request.
TE not being upfront about their ability to edit certain techniques or skill levels. This can result in editing delays, incorrect edits, or the necessity for another independent edit costing the designer more fees.
Not following a designer’s style sheet.
Not offering a second or follow-up edit to make sure no new problems were introduced after updating the original edits or after a test knit.
Failing to respond promptly when a designer attempts to contact the editor.
Receiving an invoice that bills far above the original estimate without being notified of the additional charges.
There You Have It
Yes, there are more bads than goods—twice as many. Yes, the lists rely heavily on the designer’s point of view. Yes, tech editors have their own lists of designer goods and bads. Many of the above items work both ways. Realistically though, designers generally choose the editors, not the other way around. In order to earn a reputation among designers as a “go to” editor, you really must consider the designer’s point of view.
As I reviewed the responses I received from designers, I noticed that there is not a single issue in the “bad” list that couldn’t be improved by a proactive communications policy. Not every issue can be resolved between an editor and a designer. Sometimes there is just not a good fit. However, the editor/designer relationship consists of two individuals working together to achieve a common goal. Good communication of your policies, fees, methods, and specialties will bring designers knocking. Just as significant, keeping designer clients coming back is critically dependent on building relationships through open and honest communications.
The Facts
Tech editors need to recognize that designers frequently get emotionally attached to their designs. It can be painful for them to receive page after page of negative edits. I know. I know. That is essentially what they pay us to do—find their boo boos and make them all better. But step back a second and think about how, as an editor, it made you feel to see that designers list twice as many dislikes as they do likes related to their experiences with tech editors. A wee smidgeon of empathy can go a long way. Now, I am certainly not advocating smiley faces plastered all over a pattern. Not only is that not helpful editing, it’s downright smarmy. But an occasional positive comment can ameliorate a painfully negative edit. Wouldn’t hurt to dish out a little good with the bad.