Clear and to the Point

10 March, 2020

New contract

Filed under: technical communication — monado @ 12:53

I’m working again at a very nice startup, doing some rather technical documentation. The people are extremely nice and the technology is good.

2 January, 2015

Job qualifications I hate to see

Filed under: technical communication — monado @ 13:00

There’s something a little depressing and a little frustrating in to of the items I see listed under Qualifications for many technical writing jobs. I’m sure you know them:

  • Ability to work simultaneously on different documentation modules and products in a fast paced development environment with minimum supervision
  • Ability to work in a deadline driven environment with strong emphasis on consistency, usability, and quality

Sometimes they are combined:

  • Able to work in a very fast paced environment and handle multiple projects at the same time.

The first one says, “We won’t protect you from competing priorities” or, in short, “Your manager won’t manage.”

The ability to manage all projects on all products in a fast-paced environment and produce high-quality, accurate, consistent, and readable documentation is often combined with an experience level of no more than five years. In other words, the employer is not about to pay for a senior writer. So the second one says,”We expect the impossible.” It’s a basic rule of project management: You can have it Good. You can have it Fast. You can have it Cheap. Pick Two.

Experience aside, if you are flipping from product to product, it’s difficult to get a coherent body of knowledge in your head assembled and then re-packaged. This multiplies the chance of a mistake: of missing something, of inconsistency, of applying a detail from one product to a description of another product. You need a manager who will deflect or delay some work requests.

4 June, 2011

Word-free instructions

Filed under: accuracy,technical communication,visual communication — monado @ 02:28

The Mary Sue blog offers new examples of Ikea-like instructions¬† for science fiction. You’ll notice that the images have omitted a few important details. These are obviously component-level assemblies.

diagram shows parts of Tardis with arrows indicating put it together

Step 1: Assemble the parts

4 March, 2011

Where to start with technical writing?

Filed under: technical communication,writing — monado @ 06:32

Pradipta Pati on LinkedIn started a discussion on, “How can a technical writer from non-technical background succeed in managing complex technical information or document?” There were several good answers: look into content management systems and help tools,write in XML, ask a lot of questions, maintain a query sheet, shut up and listen, use the S1000D standard for documentation about manufacturing, do your homework, insist on seeing demos and source documents, talk to others than just the engineers. Here’s my contribution:

Do some research into the development cycle of whatever you’re documenting, the industry and its practices, and currest best practices in project management and documentation. A glossary is key because you need to understand what people are telling you.Find out what knowledge your audience brings to their reading, so that you know where to start explaining. Develop a description of the beginner, typical user, and advanced user, then use them to check whether you’re covering what they need to know. Get lots of feedback at early stages:audience definition, knowledge to be transferred, discrete topics, who needs to know what, and a coherent order of presentation.

Try to include overviews and concepts as well as how-to information. Support verbiage with diagrams or tables. Ask the experts if your translation of what they said is accurate, but also identify gaps in their explanations. Use your research to fill in the parts that they assume everyone knows.

21 February, 2011

Wanted: Bilingual Technical Writer in Ottawa

Filed under: careers,technical communication — monado @ 20:32

Nortak Software Limited, with offices in Ottawa and Toronto, is looking for a bilingual technical writer with a security clearance to write about IT topics. It’s in the NCR, which must be National Capital Region and not National Cash Register, so that’s Ottawa.


  1. Must be fluent in English writing and reading.
  2. Experience working with MS Word, MS Excel, MS Powerpoint, Acrobat, and Visio.
  3. Experience in interviewing technical/business staff.
  4. Valid Reliability Status (RS) security clearance.

Related criteria:

  1. Must demonstrate experience in editing and revising French and English documents including Websites.
  2. Must demonstrate experience working with a technical team, i.e.: System Analysts, Developers, technical specialists, IT Service Management specialists.
  3. Must demonstrate experience working with business requirements and technical specification documents.
  4. Must demonstrate experience as a Technical Writer.

19 November, 2010

Technical Writer contract in Mississauga

Filed under: technical communication — monado @ 14:59

The agency TeamRecruiter is looking for a technical writer for a contract in Mississauga. The job requires experience in complying with ITIL or ISO documentation standards.

Next Page »

Create a free website or blog at