With all the yoga and meditation I do, you would think stress is something I totally take in stride. But I have faced the same challenges many of us do when it comes to managing stress. Technical writing might seem like an innocuous career, with the writers hidden away in the background, quietly working away and almost falling asleep from the dullness. It is not like that at all! We are the bridge between many different groups on a project, including developers, business and product analysts, QA and testing, project management, the SMEs, and so on. We talk to people all the time, and often face extremely tight schedules. It can get to be quite stressful if we don’t learn to balance all the demands for our time in a healthy way. My friends and family know how stressed out I can get and have given me the card shown here on two different occasions! 🙂
I was recently interviewed by Chatelaine magazine to tell my story of being addicted to stress. Vancouver-based Dr. Gabor Maté has written a great book on the subject, When the Body Says No: The Cost of Hidden Stress. I recommend all his books, but this one in particular woke me up to the trap I was in of creating a stressful lifestyle for myself. Quick tip: If you’re feeling stressed, take a breath. Another tip, from the Chatelaine article: sleep naked!
Image credit © 2006 Avanti Press, Inc., Box 2656 Detroit, MI 48231
Back to Top
February 21 marked the 4th annual Yoga for the Office class at the STC’s Canada West Coast chapter, based in Vancouver and serving technical writers in BC and the Yukon territory. (The Society for Technical Communication is a professional organization for technical writers.) This year I added a chair to the mix. Chair yoga has become increasingly popular because the aid of the chair makes the benefits of yoga accessible to almost everyone.
About 10 technical writers came to learn some gentle poses that can be practiced by any office worker, right at your desk at work, to refresh yourself after a stressful meeting or too many hours at the computer. They discovered that simple movements combined with awareness of your breath can transform your state from prickly to peaceful in a few minutes.
The class was wonderful to teach. My students were a very receptive group of technical communicators, highly motivated to ease shoulder tension and various aches and pains. I was very pleased with the turn-out and with the peaceful space for inner exploration that we created together. Namaste!
October 18, 2011 Program Meeting: The Business Side of Technical Communication
I had the pleasure of being one of three presenters at the STC Canada West Coast chapter’s October program meeting. The topic was “The Business Side of Technical Communication.”
Sheila Jones of Wordsmiths was the first presenter, and she shared many decades’ worth of experience about working with clients, estimating project costs, and growing one’s technical writing business.
Mike Smith of IS Solutions presented the perspective of project managers who provide technical writers for large projects. Unlike some recruitment or placement agencies, IS Solutions actually manages the project, oversees the technical writers’ work, and trains and mentors the writers. Definitely the way to go!
As an independent contractor and consultant, I shared my perspective on contracting directly to my clients versus going through a recruiting or placement agency. I had a fabulous time sharing some of the trials and tribulations I’ve gone through in this business. I also shared my recent experience of targeting a company I’d like to work for and convincing them to hire me. I think I’ve come to the conclusion that contracting is similar to dating—it’s better to let the guy/client make the first move. Then they know they want me, and are more invested in making the relationship work! 🙂
Back to Top
What is the difference between software implementation and software development? They sound like two very different things, don’t they? However, it depends on the nature of the software involved. Since February 2010, I have been working as the technical writer on a team for a Vancouver-based financial institution that is implementing Temenos T24 software. My role has involved developing customized online help to go with each screen of the software.
You might wonder why this is necessary. The reason is that Temenos is not an “out of the box” solution, like Microsoft Word, that is ready to go the minute you buy it. Though for those of us who have upgraded through various releases of Word, it is not really ready to go, as we have favourite ways of setting up the program to work for us. Come to think of it, the more expert a user is, the more they are likely to customize aspects of a software package before starting to use it. But I digress!
Used by over 600 banks world-wide, the Temenos T24 software is a very robust package that is customizable for each financial institution’s unique needs. The implications of this might not be obvious at first, but the software is actually intended to be developed further once it is purchased by a client. The documentation that comes with the Temenos T24 software is not intended for end users in banks and credit unions, such as front-line staff and people working in the back office to complete the behind-the-scenes aspects of banking. The Temenos T24 documentation is very comprehensive, but its intended audience is the implementation team of software developers, business analysts, and others who need to understand the nuts and bolts of the software’s structure of tables, applications, and modules. Using this knowledge, the implementation team must develop their own databases and screens for use with their company’s existing member structure, products, and processes.
Thus, the implementation team becomes a development team. Once development is involved, it necessitates an entirely different set of skills than implementation. Coding, testing, designing user interfaces, creating business requirements (if you don’t have them already! 😥 ) and functional specifications, and creating end user documentation. And that’s where I come in. To the best of my knowledge, I was the first technical writer in Vancouver with experience developing end user documentation for the Temenos T24 software. [Later update: I have assisted 2 companies with their T24 implementation and consulted with a third to provide advice about supporting banking software users with appropriate documentation. I also assisted with user interface design on several implementations.] If your company is undergoing a Temenos implementation, I would be happy to assist you with creating online help and quick reference materials that are suited to your banking processes. The key to a successful implementation is ensuring that everyone knows how to use the new software! I can help you do that.
Back to Top
Great news! The Canada West Coast chapter of the Society for Technical Communication is offering a new service to the technical writing community in Vancouver.
The information interview service connects volunteer senior technical writers with people who are requesting information interviews, whether they are tech writing students who are required to do interviews for their programs, or people considering entering the field of technical writing.
The service offers a 30- to 60-minute interview (length is at the discretion of the senior writer). It could be in person or on the phone, depending on what the two people decide.
This service gives new writers access to some of the best technical writers in Vancouver, and gives you a chance to get an insider’s view of the field of technical writing, current market conditions, what type of skills are needed, what employers are looking for, what rates to charge, and anything else you have been wanting to know.
The chapter won an STC Pacesetter award for this service, for the contribution it has made to the Society for Technical Communication through innovative community operations. I published an article on the mentorship aspect of the information interview service in Intercom, the professional journal of the Society for Technical Communication.
For full details about the service, see the chapter website. To request an information interview right away, please email firstname.lastname@example.org.
Back to Top
As an established technical writer, I occasionally receive requests to grant information interviews to people who are interested in entering the field of technical writing. Teachers in the various technical writing programs around town (Vancouver and environs, including the fantastic program at BCIT in Burnaby) advise their students to seek out these interviews, and I think it’s a great idea.
I recently had the most remarkable experience at an information interview, which has inspired me to write this top ten list of things not to do at an information interview!
- Show up at the interview location extremely hung-over, wearing your best wild animal t-shirt.
- When you first meet the professional technical writer (that would be me) you have asked to interview, who is probably in a position to hire you or recommend you for a job, say “I’m sorry I look like this, I’ve had hardly any sleep, I’m hung-over, and I can barely talk.” That will make her glad she took a precious half hour out of her Saturday to come and meet with you.
- Don’t offer to pay for the writer’s coffee and biscotti. I know you’re probably a starving student and spent all your money on drinks the night before.
- Ask in a smarmy voice, “Who else do I need to talk to to get into this field, besides you, of course?”
- When advised to join the technical writers’ professional organization, or at least come to their meetings, which cost $5 for students, say you’ve gone to a meeting and didn’t find it that interesting.
- When advised to create writing samples for your portfolio, perhaps volunteering for a non-profit organization in order to get some experience, say you don’t want to volunteer because you want to spend all your time playing guitar.
- Ask if the professional writer knows Bob Rock. (Just kidding, I made that up.)
- Present a copy of your resume, totally covered with ink from someone else’s hand-written comments, and ask the professional writer to look at it.
- Remain seated when the professional writer stands to leave. I know, you can barely move.
- Be sure to put a typo in the thank-you email you send to the writer six days later.
I hope this will help all you aspiring technical writers feel confident to seek out and conduct information interviews, knowing that the bar is not that high!
Back to Top
For technical writers
It seems that no matter how good our technical writing services are, these days we have to rank well in search engines for our clients to find us. I had a recent exchange with fellow Vancouver-based technical writer Stephen Arthur about the value of being searchable. While potential clients may be more inclined to look for technical writers on a site such as LinkedIn, monster.ca, or workopolis.com, and also in the Contractors Directory of the local chapter of the Society for Technical Communication, I think that it’s also imperative to ensure that clients can find our lovingly crafted websites through conventional search engines.
For technical writing clients
What I say here applies equally well to anyone who has a website and wants people to find your site on the internet. You must be searchable! And findable! So this article gives a few tips.
I tend to focus my efforts on Google, but there are many other search engines that people use. So here is a list to consider checking your site on:
For an unbelievable list of search engines, see the Search Engine Guide.
If your site is new, you’ll have to be patient, as it can take up to 3 weeks for the “robots,” “web bots,” or “crawlers” of the search engines to find your site and glean what’s on it. Google offers Webmaster Tools and Google Analytics to assist you. These free tools help you track what Google is finding on your site and get statistics about visitors to your site.
Try this simple trick:
In the Google search box, type site:yourwebsitename.com
This will show you whether Google has indexed your site yet. Indexing means it has found your site and made a list of keyword terms. Webmaster Tools will show you what terms it has found.
In the Google search box, type link:yourwebsitename.com
This will show you the links to your site that Google has found on other websites. This is the number one way to increase your website ranking in search engines. The more sites that link to your site, the more important Google thinks your site must be.
For a final tip, make sure you frequently use terms on your site that you think your clients will search for. The more times a term is used, the more relevant Google will think your site is and the higher it will rank your site if someone searches for those terms.
Back to Top