Marketable skills

I’m a sucker for headlines with numbers in them—you know, like “Five Reasons the iPad will Take Over the World” or ‘The 10 Phoniest Movie Monsters of All Time.” So I read with interest “Seven Marketable Skills that Most Technical Writers Have,” by Laura Spencer, on the blog ihearttechnicalwriting.com. To summarize, her list is:

  1. Interview skills
  2. Teamwork
  3. Detail orientation
  4. Ability to meet deadlines
  5. Peer management
  6. Ability to learn quickly
  7. Communication skills

As it happens, I was part of a workshop earlier this month in which a small group of experts talked about the six certification areas of practice
and the knowledge, skills, and abilities (KSAs) you need to perform competently in them. And these skills certainly came up! I take Laura’s piece as an affirmation that we’re on the right track.

A new source for STC certification news

STC is beta-testing a new community networking site, MySTC.STC.org. The Certification Committee is participating in the beta test, and we have started a group there. So far, so good… It has blogs, forums (which I think can be opened up to the world), and a listserv we will use for committee correspondence. We hope the group will become a central source of news about STC certification, as well as a respository for committee records and information.

I will be posting certification-related information on that site, so if you’re interested, you should bookmark it. You need to register on the site, even if you’re an STC member, but you don’t have to be a member to read the blogs and stay abreast of developments.

Hope to see you there!

What will certification do for me?

In speaking with people since the Summit about certification, I’ve been asked many variations on the question “what’s in it for me?” It’s a natural question that must have a good answer, but there’s more than one way to look at it.

The primary driver we identified for certification in technical communication is to legitimize the contributions of, and respect for, our profession. How many times I’ve heard technical writers complain that no one respects us! It’s painful, and I’m for anything that would improve things. But what people really want to know is whether certification will be valuable for us as individuals. What is the value of certification? I’ll answer that, but first I’ll reframe the question.

An analogy comes to mind. Imagine that you are an organically grown apple. Of what use to you is a label that says “USDA Organic”? Does it matter to you? No! One way or the other, you’re going to end up eaten.

But now imagine that you’re a consumer of apples. Of what use is the label to you? A lot, if you’re interested in organically grown apples. The label identifies the apple as something you want. In fact, people pay a premium for organically grown apples, and the label identifies the apple as what you’re looking for.

And how about the grower of organic apples? The label validates that the apple is, as priced and advertised, organically grown. Since there’s a premium market, the grower realizes additional revenue. I have also read that it’s cheaper to grow organic food, but I wouldn’t know. But either way, there’s value in that certification for the grower.

(Disclaimer: I live in apple country in Massachusetts, and tend to one apple tree that has, from time to time, yielded some excellent apples. But I don’t grow them organically.)

The question you should ask is “what’s in it for employers?” Obviously, we want, among other things, higher salaries as certified professionals. But why would an employer pay more for one? It turns out that there’s a general economic argument that explains why they do. Employers find that certified professionals are cheaper to hire, because HR departments can screen on the keyword, and because it takes less time to establish the credentials of certified professionals, because you can safely assume that they know certain things. Employers find certified professionals are cheaper to train, partly because they know their domains. Finally, employers find certified professionals cheaper to replace, simply because they don’t have to replace them as often. (This is also why training is cheaper–it has to be repeated for replacements less often.) Replacing an employee means going back through the recruitment and training phases again, and it’s expensive: I’ve seen estimates of four months’ salary per position. Given these conditions, employers seek out certified professionals. And once this competition begins, the demand has increased, and salaries naturally rise.

This is not some economist’s pipe dream, this is reality, demonstrated time and again in other certified professions. The Project Management Institute, for example, has 25 years of salary data, and they see that PMP-certified mid-career professionals earn on average 17% more than uncertified professionals. That’s not a one-time boost, but more per year, every year, until retirement.

Now, no one can promise you a direct line from certification in any profession to an immediate, or even an assured, higher salary. And it won’t happen overnight. Life doesn’t work that way. But as a general rule, certification boosts salaries across professions, for reasons that have nothing to do with any specific profession. The laws of supply and demand hold for all goods and services. We have seen no reason why technical communication would be any different. So, speaking in the broadest sense of the word “you,” that’s what’s in it for you.

Steve’s upcoming speaking engagements

[Updated 2010-08-25] So far I’ve talked about certification at the New York metro chapter, in June. I have a few more engagements lined up, some in person and some virtual:

  • On Thursday evening, August 19 I will be speaking at the Carolina chapter in Morrisville, North Carolina on certification. This trip and the meeting venue is courtesy of Tekelec, my employer. (Thanks!) The presentation will be webcast; for more information, go to http://tinyurl.com/26dugf8
  • On Wednesday evening, September 8, I will be speaking at the Northern New England chapter on structuring information from the ground up.
  • Later in the fall I will be speaking at the Boston chapter on certification (date (TBD).
  • On Tuesday afternoon, January 11, 2011, I will be speaking virtually to the Eastern Iowa chapter on certification.

I am willing and able to speak to your community on certification or any other topic you’d like. Let me know and we’ll see if we can work something out!

California Tech Writers win overtime settlement, and why it may be bad news

In 2006, a technical writer filed a wage and hour lawsuit against Sun Microsystems, alleging that the company violated California labor law by not paying overtime. Well, a judge has given preliminary approval to a $5 million settlement in the case, which grew to a class action with 152 plaintiffs.

I have mixed feelings about this development. The settlement works out to $21,000 per plaintiff after attorneys’ fees, and I’m happy for my colleagues. We know the kind of hours technical writers put in as deadlines loom. I have worked at companies where overtime was considered normal, and it’s not conducive to good work, good health, or good family relations. I’ve also worked contracts where I’ve received overtime, which made staying up all night finishing a proposal much more palatable. In future, more tech writers may find their long hours of effort renumerated, or their employers may put more effort into planning and staffing to avoid the need for overtime.

But the plaintiffs’ case in part rested on the argument that technical writers do not exercise discretion or independent judgment. They deprecated themselves as inferior in that regard to software engineers. As someone who has always considered himself a professional, and who is actively trying to establish technical communication as a profession, the argument, which has apparently carried the day, is self limiting. It’s great to get overtime pay, but not at the expense of becoming an administrative worker.

Even worse are the possible repercussions. Exempt employees earn a fixed salary, so there’s no upside, but there’s no downside, either: you don’t punch a clock, you don’t get docked if you come back a few minutes late from lunch. It’s a two-way street. And that’s peanuts compared to losing your job altogether. Before the settlement, one employment attorney said he would advise his high-tech clients to move their technical writers out of the state rather than pay them overtime in California. So this could wind up being a Pyrrhic victory–excuse me, an epic fail.