RE: Structuring Tech Pubs

["Debbi Leipold" <debbi@xxxxxxxxxxxxxxxxxx>]

I would suggest Tech pubs be its group at equal management level to
marketing, eng, graphics etc.  Not a part of another group.  That is if
there are enough people to have a tech pubs dept.  We really do have a
place.  A lone TW usually works well in engineering as the voice of the
user.  I think it depends on your situation.

As with any well structured organization there needs to be a leader and a
coordinator with other depts.  Good communication is essential bewteen
depts.  For instance, something as easy as an engineering task database can
be accessible by writers and marketeers who can see the same info but put a
different spin on it.  You can then work with marketing to ensure that there
is no conflicting info but the message is the same.  technical Writing is a
field and has its own place in the world and should have an appropriate
department.  Now if we can just convince the rest of the world.

> -----Original Message-----
> From: Carolyn Stallard [mailto:Carolyn.Stallard@Coastek.com]
> Sent: Tuesday, March 30, 1999 2:35 PM
> To: Jim Stauffer
> Cc: Turner, Will; debbi@diehlgraphsoft.com; Framers@frameusers.com;
> jim@grounder.com; framers@omsys.com
> Subject: Re: Structuring Tech Pubs
>
>
> This is one of the best reasons to align Tech Pubs with Engineering:
> to bring some semblance of customer focus to the design process, early
> enough to make a difference in product usability.  Think how much
> easier to use certain unnamed complex applications might be, if this
> was the way the product team had been organized.
>
> Jim Stauffer wrote:
> >
> . . . Being in Engineering was
> > OK, but they are so abstracted into their technology they tend
> > to forget about the customer.
> --
> Carolyn Stallard
> Documentation Manager
> Coastek, Inc.
>


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **