May 10

Layoff anxiety

I’ve been an IBM employee for a year now; the beginning of May was my anniversary. I hope I will still be one a month from now. But that may not be the case.
The Wall Street Journal and other news sources are reporting that IBM will announce layoffs in its U.S. operations later this month. I’ve been expecting something like this. Technology companies are not doing especially well right now, and IBM’s earnings for the first quarter were disappointing. The stock price has fallen, and investors want to see evidence that costs are being cut. The traditional response is a layoff.
If my team is affected, it seems inevitable that I’ll be the one to go. I was the last one hired, and even after a year of acclimation, I’m still not as effective as my colleagues who have been here longer. Letting me go would be the logical thing to do. I can only cross my fingers and hope my team won’t be affected.
When I was laid off from Alcatel a year ago, I found a new job almost immediately. But I was very lucky: I had a brother already working at IBM who was in a position to put my resume in the hands of the right person at exactly the moment when a position opened up. That sort of thing is not likely to happen again, and job prospects in the current market are pretty grim.
But if it comes to that, I’ll find something. I always do. I’ve spent most of my technical writing career as a contractor, and that experience has taught me that any job can end without warning, whether it’s “permanent” or not. (In fact, my five-year stint at Alcatel was arguably the most permanent job I’ve ever had, even though it was a contract.) You just have to suck it up and hit the street the next day as a full-time job hunter.
In theory, it’s better to have a little warning that something like this is going to happen. But in practice, there’s not much you can do about it except worry. I’ve been laid off without warning before, and I actually prefer it that way. At least it’s over quickly and you can move on.
Well, if I didn’t want to know about this, I guess I had no business reading the Wall Street Journal. Nothing to do now but update my resume and then try to think of other things until the announcement comes. Either way, life will go on.

Apr 02

Letting go

One year ago today, I was laid off from my job at Alcatel. As I’ve mentioned here before, that turned out to be just about the best thing that could have happened. It freed me up at precisely the right moment to take a much better job at IBM, and it got me out of an environment that had been deteriorating for some time and was about to get much worse.
The prospect of being unemployed can be daunting, but sometimes it’s the first step toward much better employment. Before April 2 of last year, I was reflexively clinging to a job that I no longer enjoyed and that had become a dead end, just because I was afraid of the unknown. I shouldn’t have needed a layoff to shake me loose. Sometimes, the best thing to do is to admit that you’re not happy with what you have, and let go of it.

Mar 25

Welcome back from the abyss

The beta crunch is finally over. On Friday, my documentation team finally delivered our help files and manuals for the beta release of the product. And I went home and went to bed. I slept for the entire weekend, except when I was away from home on previously scheduled engagements (Diversions on Saturday, and the memorial service for Miles’s stepfather on Sunday).
Now it’s Monday, and time for my life to get back to normal. Last week was a remarkable experience — I’ve always said that I do some of my best work under extreme pressure at the last minute, and this was no exception — but one can only live for so long on adrenaline, coffee, and three to four hours of sleep per night. I’m proud of what we accomplished, but I think I’ve had enough white-knuckle technical writing for a while.

Feb 06

Ghost town

On Monday, I talked to one of my former coworkers at Alcatel. He informed me that the technical writing group that I used to be a part of has basically ceased to exist.
I was laid off from my contract position at Alcatel on April 2, 2001, after working there for five years. It was a shock, of course, but I had been laid off before. Most of my fifteen-year career as a tech writer has been as a contractor, and contracts sometimes end with little or no warning. Thus, I was better prepared than some of the half-dozen others in my group who lost their jobs that morning. (One of them was a graphic artist who was not a contractor and had been with the company for twenty years.) No, what was most shocking about the layoff was that Alcatel Raleigh had been steadily expanding for the entire time I was there.
When I arrived at Alcatel in March of 1996, the building where I worked included a big empty space that my new coworkers called the Ballroom. It had previously been a factory floor, but the manufacturing operation had been moved to another building. To give you an idea of how big it was, I have to describe the one time I actually saw it used. Every year, in early December, the company treated everyone to a free holiday dinner. It was a company tradition: turkey, roast beef, ham, dressing, vegetables, rolls, dessert, the works. In 1996, Alcatel rented enough folding tables and chairs to fill the Ballroom and was able to seat the entire workforce of the Raleigh site — not just my building, but all the manufacturing folks, and everyone else from several other buildings — in that one huge room.
By the following December, this was no longer possible, because the Ballroom was gone. The company had renovated it and turned it into office space, subdividing it into several smaller spaces and filling them with cubicles. (Subsequent holiday dinners were served in the company cafeteria in multiple shifts.) Similar renovations were going on in other parts of the building; most of the Receiving area, for example, was walled off and turned into offices and meeting rooms. This was all necessary because the workforce of the Raleigh site was growing rapidly, and office space was needed for all the new people. My department was no exception — our area had several empty cubicles when I arrived, but these were soon filled with new employees. We eventually ran out of space and had to move to another part of the building after it, too, was renovated to maximize the number of offices it contained. By 2000, the building was pretty much maxed out, and there was talk of Alcatel acquiring another building in the area and moving some of us there.
That’s why the layoffs in April 2001 came as such a shock. After five years of continual expansion, the last thing I expected was for the company to start cutting its staff. I still don’t know exactly what happened, but I can guess. Like a lot of companies in the data communication business, Alcatel was riding the crest of the Internet boom, selling networking hardware to the companies that were building the new online economy. The company’s rapid expansion was no doubt based on the assumption that the boom would continue. When the dot-com meltdown occurred, Alcatel must have found itself with a lot more employees than it needed.
I was fortunate to be in the first wave of layoffs. The job market hadn’t gotten nearly as tight as it would later in the year, and a writing position came open at IBM just when I began looking. (It also didn’t hurt that I had a brother working at IBM who was able to put my resume in the right hands.) In the months that followed, I read news reports of further staff reductions at Alcatel Raleigh, and realized that I was one of the lucky ones. Had I managed to hang onto my job beyond April 2, I would have still have found myself unemployed a few months later, when jobs were scarcer and IBM was no longer hiring.
When I called my ex-colleague Mark this week (to arrange to return a couple of books I borrowed), he brought me up to date. Alcatel Raleigh had announced another wave of layoffs (the fourth, I think) earlier that day. Mark hasn’t lost his job, but the entire technical writing group (what’s left of it) has been outsourced. They are still sitting at the same desks and doing the same work, but they are now employees of an outside agency that provides services to Alcatel. Their jobs have been “guaranteed for six months” (for whatever that’s worth), but no one really expects to be there much longer than that.
Mark describes the building I used to work in as “a ghost town.” Almost all of the new offices are empty. Mark thinks that the building, and perhaps the entire Raleigh site, will probably be closed down later this year. I’m sure he’s right; it can’t be cost-effective for the company to keep it open with so few people working there.
I try to imagine what the place looks like now, but I can’t. I suppose I could go visit Mark during the day, and he’d probably be happy to show me around. But I don’t think I want to do that. I’d rather remember Alcatel the way it was when business was booming, the future was bright, and we all thought the good times would last forever.

Oct 24

We’ve been on this shift too long

The deadline crunch that kept me from posting here for a while has now officially passed. In the part of IBM where I work, iterations of the software and documentation are called drivers for some reason. When I started this job six months ago, work was just starting on Driver 6, to which I contributed nothing worth mentioning. The deadline that just passed was for Driver 7, and this time I wrote a bunch of online help pages (which is why I was so busy the last couple of weeks).
Now we’re starting on Driver 8, and when my manager sent out an e-mail about the schedule, he attached an MP3 file containing an R.E.M. song called “Driver 8.” (You can hear a sample of it here.) Playing it through my headset, I found that I really liked the sound of it, but couldn’t make out all of the lyrics. And in the process of tracking them down on the Web, I discovered that the guy playing drums on this song was named Berry. Isn’t synchronicity fun? No, wait, that was The Police. Never mind.