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.
I worked for a company that was acquired by Microsoft several years ago
(Microsoft recently sold it). The technical writing dept. was not touched,
nor was there ever any real concern that it would be touched. The only dept.
that was cut was the marketing dept. It also helped that we were located
not only across the country, but in different countries (US and Canada). I
think whether the two writing depts are integrated or not depends a lot on
the similarity of the products.
Suzanne Gerrior
Documentation Specialist
Jazz Media Network
Montreal, Quebec
Tel: (514) 931-7009, ext. 255
Fax: (514) 931-9495
suzanne -at- jazzmail -dot- com
-----Original Message-----
From: Eric J. Ray <ejray -at- RAYCOMM -dot- COM>
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU <TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU>
Date: June 23, 1998 1:23 PM
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?
>
>