TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Acquisitions (WAS: RE: Sterling Software) From:George Mena <George -dot- Mena -at- ESSTECH -dot- COM> Date:Tue, 23 Jun 1998 10:36:20 -0700
In mergers, documentation departments eventually get merged.
This was certainly what happened at a previous employer of mine. First,
the tech support people at my place went down to Orange County to
educate the tech support people down there on our hardware and software
products. Then, the tech support calls started being shared between
Mountain View and Irvine. Ultimately, the documentation department in
Irvine took over Mountain View's workload.
Update your resume and start looking around right now.
George
> -----Original Message-----
> From: Eric J. Ray [SMTP:ejray -at- RAYCOMM -dot- COM]
> Sent: Tuesday, June 23, 1998 10:20 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: FWD: Sterling Software
>
> Name withheld upon request. Please reply on list.
>
> *************************************************
>
> My company, Synon, has been acquired by Sterling Software. So, they
> say
> that layoffs are inevitable, but are trying to convince us that
> engineering (of which the writers are a part) is pretty safe. But I'm
> wondering how documentation departments usually fare in mergers and
> acquisitions. Anybody out there been through this, before?
>
> And, on a more individual note...any Sterling Software doc people out
> there? If so, is there anything you can share about what it's like
> working
> for that company? Should I be worried?
>