More Than a Technical Writer

December 17th, 2008

The term “technical writer” isn’t one I like much, at least not to describe myself. It calls up an image of someone who sits and writes simple procedures that are printed on sterile-white sheets of paper. (It’s sad when I’m a technical communicator myself, and I still have certain stereotypes in my head.) To me, a technical writer does just what the title suggests—just writes.

To prove to myself that I’m more than a tech writer, I tracked my work time last week, classifying my activities in general categories. Out of a full work week, I spent only about four hours writing, not including emails because I don’t count email-writing as technical writing. These four hours of writing activity included on-the-fly revising that is a standard part of writing for me, so I didn’t break out how much of that time was revising vs. active writing.

I was involved in more meetings than usual due to coordinating training for an application rollout, but the total amount of writing was probably on the lower end of normal.

The following list describes activities I tracked last week, plus other tasks I may perform on other days but may not have had to do during last week, not listed in any particular order:

  • Staff meetings
  • Information gathering
  • Help debugging
  • Translation work
  • Training planning
  • Documentation writing/editing
  • Helping designer with prototype text
  • Answering customer questions
  • Prototype feedback
  • Task for team manager
  • Coworker help
  • Project meetings
  • Email
  • Training setup
  • User training
  • Demo scripting
  • Demo recording and manipulation
  • Training scripting
  • Image creation and editing
  • CSS editing

It’s not like my self-image will suffer if someone calls me a tech writer, or if I refer to myself as one. But if I tell people that’s what I am, they have notions about what that means, and I’d be surprised if those notions matched what I actually do. I used to think it’s ironic when the wordsmiths can’t come up with a good title for themselves, but in a recent conversation with my manager’s manager, we decided that it’s a symptom of the perfectionism in us.

4 Responses to “More Than a Technical Writer”

  1. Craig Says:

    I wouldn’t mind being “more than” a technical writer, but right now that describes what I do.

    I am updating and revising the BIG manuals that accompany the main applications our company produces.

    I write, edit, revise, analyze, and get screen grabs. The heavy editing is done. Now I’m trying to make the updated guide I’m working on look good.

    My manager has mentioned video tutorials in passing — while look right at me — so I suppose that’s in my future AFTER I put this latest guide to bed.

    I love refreshing older user guides, but I wouldn’t mind doing something a bit different.

  2. Gryphon Mountain Journals » Blog Archive » More Than a Technical Writer Writer River Says:

    [...] More Than a Technical Writer | Gryphon Mountain Journals Tom Johnson | December 18, 2008 | permalink Tags: career, daily work, name, profession, technical writer   [...]

  3. Thomas Says:

    I’m not sure why our industry has so little self-confidence that we agonize over titles like this. Sure, there’s more than putting words on a page, but isn’t there more to most professional jobs than what the title implies?

  4. Ben Says:

    Craig, I don’t belittle someone who is actually writing all or most of the time. In fact, the time I do get to write is one of the reasons I’m in this field in the first place.

    Thomas, you’ve brought up a good point. There’s a lot of title-inflation out there that people think will boost self-esteem. For example, I was a bagger for an Albertson’s food store in high school, and they called us “courtesy clerks.” That didn’t change the fact that I was a bagger and janitor.

    For technical communicators, I don’t think it’s a matter of self-confidence as much as it is the problem of being pigeonholed. Tom Johnson recently posted a good example of this. When people (read “managers”) have limited expectations about what you can do, they don’t give you opportunities to do more and expand your area of impact.

Leave a Reply