Eye for Editing: The Editor as Teacher

Editor’s Note: A version of this article was originally published in the STC Notebook in 2014 as part of a series. To make it easier for you to find these articles again in the future, they are tagged with the Eye for Editing tag, and the titles prefaced with the same phrase.

Author's Note: This is the last article (that currently exists) in this Eye for Editing series. It has been fun to revisit my thoughts from the “first edition” in STC Notebook to find that most, if not all of it, still holds true to the editing experience. 
Do you have an idea for a follow-up article that you’d like to publish in Corrigo? Would you like to put together your answers to my questions for others to read? Submit your ideas and articles to the Corrigo editor at editor@stc-techedit.org.  And you are welcome to contact me any time to keep the conversation going

By Paula Robertson

How do you think of yourself in your editing role? Is each document, article, topic, or book by the same author or team of writers an isolated editing task? Does each task seem to start from scratch as if you’d not edited that author’s work before? Or does each subsequent edit you deliver build on your previous suggestions and comments? Do subsequent documents indicate that the writer “got it the first (or last) time”?

Continue reading “Eye for Editing: The Editor as Teacher”

Eye For Editing: Do *Not* Edit…

Editor’s Note: A version of this article was originally published in the STC Notebook in 2014 as part of a series. Over the course of 2022, we hope to publish more of these articles. To make it easier for you to find these articles again in the future, they will be tagged with the Eye for Editing tag, and the titles prefaced with the same phrase.

By Paula Robertson

Just because you can. Please, do not mark something for the author to change just to prove your superior knowledge of seldom-used symbols.

You wouldn’t do something like this, would you? In the throes of final review to meet a draft document deadline, please don’t waste the author’s time—the author who is already stressed and has worked many overtime hours to meet the deadline—by demanding revisions that no one but you will notice. You will get your chance later, but at this stage, please resist the urge to point out every tiny flaw that presents itself.

Because it’s just not important. And does more harm than good. The readers of the draft won’t care; your writer will. Is it worth it?

Continue reading “Eye For Editing: Do *Not* Edit…”

Eye for Editing: Caught Between Two Edits

Editor’s Note: A version of this article was originally published in the STC Notebook in 2014 as part of a series. Over the course of 2022, we hope to publish more of these articles. To make it easier for you to find these articles again in the future, they will be tagged with the Eye for Editing tag, and the titles prefaced with the same phrase.

By Paula Robertson

Once upon a time, I found myself in an interesting position. I had a freelance client for which I did editing exclusively. I also had a full-time contract gig where my job descriptors were writer, editor, designer, trainer, developer, project manager… My deliverables were primarily original content as a writer, and editorial reviews of the original content of my writer peers, on a team of three.

Continue reading “Eye for Editing: Caught Between Two Edits”

Eye for Editing: The Extracurricular Edit

Editor’s Note: A version of this article was originally published in the STC Notebook in January 2014 as part of a series. Over the course of 2022, we hope to publish more of these articles. To make it easier for you to find these articles again in the future, they will be tagged with the Eye for Editing tag, and the titles prefaced with the same phrase.

Have you ever had the experience in daily life where someone gave you instructions for a certain task, and upon trying to follow them, you found them to be incomplete and inaccurate?

That’s not meant to be as rhetorical as it sounds, because I will add that when you pointed out to the provider where the instructions went awry, did they ignore your helpful suggestions and continue to use the same inadequate instructions?

Continue reading “Eye for Editing: The Extracurricular Edit”

Eye For Editing: Practice What You Preach

by Paula Robertson

Editor’s Note: A version of this article was originally published in the STC Notebook in December 2013 as the fourth in a series. Over the course of 2022, we hope to publish more of these articles. To make it easier for you to find these articles again in the future, they will be tagged with the Eye for Editing tag, and the titles prefaced with the same phrase.

I know it’s April, but have you ever made a “new year’s” resolution related to your work in technical communication? Once, when I was asked to do so, the only resolve that came to my mind was “to practice what I preach” in terms of editing.

And that just didn’t seem to be a worthy resolution. To be honest, I was hesitant to admit that I continue to struggle with the all-important aspect of editing that is for me “learned” rather than “innate” (see Eye for Editing: Learned or Innate?). Although I write and speak about the importance of it, I struggle in the practice of people skills.

An editor can possess all manner of confidence in their command of technical communication rules and practices, years of exceptional prowess in turning textual sows’ ears into silk purses, a wealth of professional accolades, a lengthy resume of experience and training. But if they don’t have a soft touch in communicating their editing expertise, their marks are nothing more than unwelcome clamor to the recipient. My last article, Eye for Editing: Taking It Personally, provided a “good” example of a time when I failed miserably.

I will add that whether the soft skill, people side of editing is learned or innate depends largely on one’s inherent temperament and personal emotional journey since the birth of their personality. Oops! That’s getting dangerously close to psychoanalysis, and I am not going there.

But my point is that what might be “innate” about a particular editor’s skill is not entirely or necessarily related to content or language expertise. Am I backtracking on my original thesis? Not exactly. Only adding breadth to the discussion, as well as underlining how complex the editor’s role is.

In plain terms, relating effectively in the editor role is harder for some than it is for others. If you aspire to be an editor, are you aware of how you come across to others in general? I suggest that learning to be an editor means working just as diligently on people skills as on technical practice. If you’re like me, you have to work harder at learning and using those people skills that make you a sought-after, effective editor. And that’s why I resolve to practice what I preach.

Paula Robertson has learned her editing skills over a long and varied career, while swapping among the various titles of writer, editor, and designer. No matter what her current job title, she has earned the right to call herself the Full-service Editor, because of her ability to review text and graphics as cohesive parts of a whole. In STC, her current job title is facilitator for the Solo Technical Communicator SIG/COI. You can reach her at: solotechnicalcommunicator@gmail.com