Audio Zone TriggerIt’s validating when people come back for more!

In this case, Joe was happy with my work on his Zone Trigger documentation, so asked me to polish the Audio Zone Trigger manual. This entailed creating both a conventional HTML Help (.chm) and web-based help with pictures.

Jo was kind enough to mention me on a forum for independent software vendors:

I just had the documentation revamped for all my products by fellow OISV member Documentation Doctor. I just want to recommend his services to everyone here, this guy is in a league if his own, and a pleasure to work with.

 

Whoa dude!Imagenomic make software for enhancing and modifying digital images.

This means that prolonged exposure to the images making up their documentation is almost guaranteed to induce psychedelic dreams!

Fortunately, the visual overload does not seem to have affected the quality of the resulting document:

Documentation Doctor took our assignment, which required absolute accuracy for a lengthy, image-intensive product tutorial, and turned it around promptly and with minimal need for additional input or adjustment. This doctor had the right remedy for a painful situation, and we are feeling better for it! I highly recommend the Documentation Doctor, and would not hesitate to use his affordable yet highly professional services again.

 

Say It With BulletsAre you shooting yourself in the foot with bullets?

Ever click on a radio button, only to get a popup window  or – worse – a crazily whirring C: drive and a sluggish progress bar? Annoying isn’t it? More importantly, you quickly learn to distrust the GUI.

Bullets in documentation are a bit like that.

The format of instructional text, like the design of a GUI control, can either succeed or fail to suggest its function. In other words, just like software, documentation can have good or bad affordances.

Bullets look like a non-ordered list…

Continue reading »

 

SPG exampleTo be honest, this project scared me!

SmartPropertyGrid.Net is a cool, user-friendly, easy-to-deploy replacement for the Microsoft Property Grid, familiar from applications and programming environments. As a techwriter, I’m thrilled by the product – it locks out a lot of UI issues, and ensures consistent layout.

The snag is that, though I’ve done some coding in the past – and boast that I’m a wizard with VBA – I have no experience of .Net.

.net code!

Thankfully, all Nicolas wanted was a Basic Edit. Though he communicates effectively in English, his first language is French. He needed somebody to make the manual read as if written by a native speaker, and to give the presentation a polish, for example turning paragraphs into numbered instructions.

It was a bit like that children's game...From the outset, we agreed that this would only work if we acted like an in-house team…. though actually, it was a bit like playing that children’s game, “Battleships and Cruisers”.

Whenever I got stuck – which was often at first – I mailed Nicolas with two or three guesses. Sometimes one of my guesses was “on target”. Other times, I was so wrong it was funny!

Thankfully, my misunderstandings enabled Nicolas to supply new – clearer – draft copy which I could then edit. Mostly, we nailed queries in one iteration. However, there was one pesky paragraph which I think went to ten emails!

In the end, it was all worthwhile. Nicolas got the manual he needed, and was happy to say so in a public forum:

He just finished reviewing/fixing my 50+ pages Programmers’guide and the result is excellent with already positive feedback from my customers. I’m french and my doc was a poor word for word translation…

 

 

This was a fun project. Andrea has created a customisable shortcut tool for people who prefer keystrokes to mouse-clicks

Direct Access in action!My first reaction was “Good grief, this is retro!” I half-expected it to have a black-and-white DOS style command screen…

Of course, it turned out to be a modern, user-friendly application. It’s heaven for the command-line addict, and a natural choice for the trained typist. It’s also one of those products with all sorts of business uses. For example, the autotext function lets you handle dozens of similar, but unique, email interactions in record time, e.g. for operating a support desk.

I helped a bit with the press release and the website text. I’m also particularly proud of the animated .gif. Humour is not always a good idea in technical communication… but it has it’s place.

However, most of my work was on the manual itself, which I created as a HTML Help (.chm), and as a web-based help.

Andrea seems pleased with the results:

You offered exactly what I needed and I could not be more happy with the result.

I’m looking forward to his next release!

 

frontdoor.GIFOne of the nice things about running the Documentation Doctor, is that I get to work on the sorts of products that actually do the things people expected computers to do, back in the 1980s!

Zone Trigger 1.8 is just such a product. It doesn’t just monitor webcams for movement, it actually lets you specify hotspots to trigger alarms and alerts. This is great if – for instance - a webcam monitoring the approaches to your vandal-prone front door overlooked a busy street. 

I had great fun giving the Zone Trigger documentation a Basic Edit. I supplied the help in two formats: web pages with screenshots so potential customers can get a feel for the product; and a leaner .chm for use as online help.

Gratifyingly, Joe seems happy with the results:

Overall I am very satisfied, I think this is a huge tune up for my product. You went beyond technical writing and really took the time to know my product. I will definitely seek your help again. (You can quote me on this).

 

Some people make a career of house doctoring. I’m doing the same with technical documentation.

There’s this UK TV show where a brilliant Californian house doctor hurtles around a property, improving its value. She doesn’t add much to the house – perhaps a coat of paint here, a plant pot there – but she does transform its presentation. Suddenly, it’s worth a good dollop of extra cash.

That’s what I do with documentation. I don’t pretend to add content, just value.

Modern software developers already have a detailed functional spec, or draft manual. You don’t need a technical author underfoot, spending billable days investigating the product and asking questions!

What you do need is somebody to rewrite, reorganize and reformat your existing content, turning it into professionally presented user-friendly documentation. That’s what I do, and that’s why I call myself the Documentation Doctor.

 

Mrs TrumanRemember Mrs Truman in the Truman Show ?

Well, persuasive language in documentation is just about as welcome as a product placement in your kitchen.

Just imagine…

You need to know if SmiteMaster600 – supposedly a “state-of-the-art security system” – is worth buying. The best way to find out is to download the software, and to then invest a precious hour of your life playing with it.

First challenge – how do you switch everything on? Well, according to the documentation….

Activation of the Main Security Features

Our skilled designers have optimized SmiteMaster600 for maximum ease-of-use, enabling you to quickly activate the main security features. Simply bring up the SmiteMaster Console, and click the Activate button.

Your first reaction is probably “Argh!” (or something less printable…). This is like having your driving instructor trying to sell you a car mid-lesson.

You just wanted to learn how to use the product! You really don’t want to waste time plowing through a sales pitch. Worse, though you now know the how, you still don’t know the why. If the rest of the documentation is like this, you’d need very good reasons to waste more time evaluating the product.

What went wrong?

In trying to persuade the reader, the author forgot that they were addressing a user!

It’s pointless trying to persuade a user that the software is “user-friendly” – they’ll decide that for themselves, based on hands-on experience.

Also, nobody actually enjoys reading documentation. So, to get people to read on, you need to include useful information. The above example does not.

How to present a feature effectively

You don’t have to do anything complicated. Just…

  • Say what the feature does, and why.
  • Describe how to use it.

An improved version of the SmiteMaster documentation would probably read like this….

ACTIVATING THE MAIN SECURITY FEATURES

The Main Security Features protect your installation from all known Type 9 Incursions. Since they may interfere with normal traffic, we recommend you only switch on these features during an alert (as defined by your organisation).

To activate the Main Security Features

-In the SmiteMaster Console, click Activate

You’ll note that the instruction is terse, without even a “simply…”. Since the feature really is easy-to-use, we can let it stand on its own merits. In fiction, this is known as show, don’t tell (something Andrea Nagar identifies as one of the rules of good documentation).

Not only is documentation like this easier to use. It’s also easier and faster to write!

 

Well, here it is! My revamped site, created by my pocket web design guru, Andy at Ex-Nihilo, who saved me investing time on technical details. (If you’re reading this having found me via Google, then the chances are his Search Engine Optimisation worked…)
The big change is this - the WordPress blog. I’ll admit to being a reluctant blogger, despite good advice to the contrary, and the example of plenty of role models ranging from the commercial, through to the literary.

However, it was my friend and client Andrea Nagar who pointed out the obvious – a blog is a great way to really show where I’m coming from.

So, I’m going to kick off by blogging about technical authoring, and about the way I do it.