Engineers as authors

[Stephen O'Brien]

Excellent question.

It is my experience that writing obliges one to structure one's thought and make clear concepts that otherwise, expressed orally, are presented more vaguely.

This is certainly a benefit, as is good, solid procedural documentation.

There is the general question as to whether tech writers or engineers should be doing the work of documentation creation.

To answer your question, it is seen as more work at this initial stage.

Stephen O'BRIEN
Coordonnateur à la documentation et rédacteur technique senior | Documentation Coordinator and Senior Technical Writer
T (1) 418.688.2061

-----Message d'origine-----
De : Milan Davidović [mailto:milan.lists at gmail.com] 
Envoyé : Monday, October 07, 2013 12:45 PM
À : Stephen O'Brien
Cc : Frame Users (framers at lists.frameusers.com)
Objet : Re: Engineers as authors

It looks as though the documentation they create has the potential to reduce the time they spend on those tasks. Aside from being "open" to the new responsibilities, do they see how it benefits them? Or do they simply see more work?

--Milan Davidović

Sent from my Yost 10


On Mon, Oct 7, 2013 at 11:40 AM, Stephen O'Brien <sobrien at innovmetric.com> wrote:
> They are wondering what their exact responsibilities will be. They 
> have many other tasks (training, solving client problems over the phone or on-site).
> They are open to contributing content but at the same time have 
> questions about the time that can take.