The Tech Comm Café met on April 13 at a café in Burnaby for another wide-ranging discussion of technical communication topics.

A writer asked for tips on setting up a Doc-to-Help system in a way that would allow the client to maintain and update information after the writer had left the project. Though no-one at the meeting had the depth of knowledge the writer was seeking, they were able to suggest some options. For example, search related LinkedIn groups and social media contacts to identify experts in the area. Post a request on the Canada West Coast chapter’s job bank to find someone you can hire to provide a few hours of advice.

We agreed that few people have the time or the willingness to keep up with the barrage of non-stop information on social media. Most choose one or two to follow closely, let the rest stay in the background, and find that information circulates so quickly through so many channels that they still stay up to date efficiently.

Another writer shared a story of a client (no names mentioned) who took more than four months to pay for a quick 12-hour rush job. The writer spent more time trying to get paid than working on the original project, and wondered how to identify or deal with such clients in the future. Continuing the theme of workplace frustrations, someone else described the difficulty of coping when two of a team of three technical writers leave the company and management decides not to replace them, believing that anyone who can use a keyboard can write documentation. Another brought up the delicate dance required when a contractor is asked to train and supervise the client’s daughter, a recent graduate with no experience in technical writing, while maintaining good relationships with everyone. [Follow-up: We are informed that the trainee is doing well on her first project and is considering a technical writing career. Bravo, contractor!]

Other difficulties arise when trying to work with or supervise a person who thinks they know it all, refuses to compromise, and makes life unpleasant for their colleagues. Bottom line: There’s a lot more to technical writing than putting words together. The “soft skills” of diplomacy, negotiation, persistence, problem-solving, and flexibility are part of the writer’s toolbox as well.

Next Vancouver-Area Tech Comm Café: Wednesday, May 11, 2016

The TCC provides networking opportunities, job leads, answers to work-related dilemmas, and a burst of professional energy to keep you motivated. We discuss technical writing tools and techniques, career planning, portfolios, and anything else related to working as a technical communicator.

We welcome anyone who’s interested in technical communication — contractor, in-house, student, long-time tech writer, STC member, non-member, career-changer, or recruiter. We hope to see you at the next meeting!

Date: Wednesday, May 11, 2016

Time: 6:30–8:00 pm Pacific Time

Location: To be announced. If you plan to attend, please RSVP to admin@stcwestcoast.ca

Agenda

  1. Introduction. Take 60 seconds to introduce yourself, your background, current activities. A good chance to try out that new elevator speech.
  2. Announcements and job leads. If you know of an interesting event or a job opening, or you’re looking for work, share it with the group.
  3. Brainstorming Q&A. Ask about a work-related problem and discuss potential solutions.
  4. Speed networking. Spend a few minutes with a new contact, exchange business cards, and discuss your professional backgrounds and goals.