Skip to main content

20 Technology Skills Tech Writers Should Have

Inspired by this post at the Shifted Librarian:

  1. Spreadsheet Skills

  2. Database Skills

  3. Scripting Skills

  4. Electronic Presentation Skills

  5. Web Site Design Skills

  6. Email Management Skills (including outgoing mail)

  7. File Management Skills (non-Windows)

  8. Computer Network Skills (including Wireless)

  9. Installing Software Skills

  10. Distance Learning Skills (vendor agnostic)

  11. Computer-related storage devices (DVDs, SANs, USB Drives)

  12. Knowledge of PDAs and cell phones

  13. Advanced Electronic Research Skills

  14. Electronic Copyright Knowledge

  15. Computer Security Knowledge

  16. Web Content Delivery Skills (RSS, Newsreaders, Forums, Blogs, etc)

  17. Fontography Skills

  18. Basic to Intermediate Electronic Page Design Skills (using Word templates doesn't count)

  19. Advanced Markup Skills

  20. Basic to Intermediate Skill in at least one area of expertise that doesn't relate to writing.

You might get away with not having one or two of these, but you better be supplementing them with other items. It never ceases to amaze me the number of people who can "write" but have zero clue who they are writing for. I saw a comment the other day in reformSTC that every minute spent using the product of a tech writer is a minute not spent completing the task the user needs to accomplish. What a profound statement. It was, in true writer fashion, pounced on and flamed out of conversation.

That's too bad. Maybe it's not a true portrayal of the concept, but it's a hell of a lot closer than the attitude that users are idiots because they didn't read the entire chapter of Help on composing a widget.


Popular posts from this blog

Google Inbox: A classic Google product

My work domain (an EDU) recently had Google Inbox enabled so I had a good chance to try it out. My personal email is relatively quiet and, I believe, doesn't provide a good Inbox experience. Work is more active and requires actual management, something I've tossed many a tool at over the years. As part of my work life, I supported the Google Apps for EDU installation here and took a pretty extensive presentation to campus about how to manage large amounts of email.

Inbox is a classic Google product: the distillation of a number of excellent ideas into a set of half-complete features built for a use case most people don't meet. We've seen this in the past in products like ChromeVox, Google's Chrome extension for accessibility. ChromeVox works great on ChromeOS devices, but completely ignores the point that most users of accessibility tech (AT) don't have or want ChromeOS devices and come to services with their AT in tow. ChromeVox also ignores decades of convent…


Evernote, for better or worse, is the best note-taking service for my needs. It works across all my devices/computers/modes. It's fairly easy to get stuff into it. Hell, they even have 2-Factor authentication. The Windows app is a little clunky and my girlfriend and I have never been able to get shared notes to work properly (conflicted note! three times in the same grocery trip!), but what service is perfect? At least they have nice socks.

Everything, in fact, is pretty good as long as you don't screw up. And screw up I did. I'm not very regular about making backups, but I do make them every month or so. Once you figure out how to create a backup, that is.

There's a helpful Export Note option (which turns into Export Notes when you select multiple notes HINT). The export process is essentially opening All Notes, selecting every note, and then choosing Export Notes. Or something like that; Evernote never tells you, you're left to figure it out on your own. The file…

Happy Retirement Pat Sweeny!

In a previous life, I was an active member of the West Michigan Shores Chapter of the STC. I met a lot of really cool people there and learned a lot about what it meant to be not just a technical writer, but more about how technical writers can break out of the mold and accomplish things.

One of the people who did that was Pat Sweeny. Pat is (or was, by this point) the President and owner of The Bishop Company, a contract do-it-all house; they document, streamline and illustrate your process, and they do it damn well. Pat was one of the first people in that chapter to "get it", which is to say, he and his company understand that technical writing isn't going to be a department for very much longer, it's going to be a business.

He had the foresight to actually make it a business, but he also had something else. Pat was forever trying to better those around him. He would come to meetings (which was a big step beyond most people) and teach you things. Or he would come to …