Letting the engineers write within guidelines works for me. I am the sole technical writer in the company. I also installed and manage two wikis - one is a mirror image of suitable parts of the internal one containing material suitable for the outside world.
Simon North On Mon, Oct 7, 2013 at 6:41 PM, Robert Lauriston <robert at lauriston.com>wrote: > That's a proven approach. If you're going to do that, you should look > into using a wiki. > > > On Mon, Oct 7, 2013 at 7:26 AM, Stephen O'Brien <sobrien at innovmetric.com> > wrote: > > > > Or, maybe the role of the engineers should be to write rough content > within guidelines (get the ideas and workflows on paper), and my team of > technical writers could be responsible for formatting the content and > expressing their ideas/workflows correctly in English. This would take much > less time for the engineer (less of a learning curve). > _______________________________________________ > > > You are currently subscribed to framers as simonxml at gmail.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/simonxml%40gmail.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20131008/b54ab42c/attachment.html>
