
Do you often have to write for a supervisor? Or are you, perhaps, a supervisor for whom other people have to write? In either case, it's worth noting that not every textual change is a judgment of the writer's ability. Often, changes are made because of a sense of voice. And voice is something unique to each of us.
In my own work, sometimes I receive and edit text from other writers, and sometimes I have to submit my own writing to superiors. In both cases, textual changes occur. Sometimes it's a matter of correcting errors. (No one can write, edit, and proofread all at the same time. That's why publishing companies have writers, editors, and proofreaders, each focused on a different step.) But just as often, a technically correct piece may be adjusted for tone, perhaps to better match the company's voice.
Certainly it can be exasperating to pour your best work into a piece of writing and then have it changed - perhaps dramatically. We often hear from office writers worried that their jobs might be in jeopardy because of how much their text gets edited. My best advice comes from the Tao te Ching, "Do your work, then step back. The only path to serenity." Do your best. Let it go. Fretting never makes things better. Calm - on the other hand - definitely does.
For supervisors reviewing other people's writing, I'd point out again the H.G. Wells quotation above. It hangs above my own desk as a reminder not to change things just for the sake of change. If you do make changes to a draft, be aware of how it reflects upon the writer who submitted it. If the changes are to correct errors, make sure the original writer understands those errors, to avoid them in the future. (This may mean firming up your own understanding of the grammar or punctuation rule involved. I work full time in publishing and frequently have to look things up again.) If you can't explain why a change is being made, ask yourself whether it's really necessary.
I suspect that's what H.G. Wells would ask about my red pen marks above.
- Lester Smith






Comments
Post has no comments.