Technical Documentation: Are you all-in or just dabbling a little?

SUBSCRIBE

When Technology Companies come to me with their self-written manual to read and edit, some of the major obstacles they were not ready or willing to contend with are invariably exposed.

The natural outcome of a writing process is to find the objective of the procedure and explain it so that inadvertently all other procedures will be better understood.

If that is the case, then why do we need a complete manual if we can get away with one procedure? I meet a lot of companies who have that mindset. They prefer to present customers with outdated YouTube videos than write it like it is.

It’s almost impossible to rewrite something easily – sometimes it’s more financially smart to write it from scratch – especially if the important parts are new – you CAN change the screen and then what? The textual procedure comes to assert the screens – a 1000 words were saved – but nobody knows how to use the feature.

The long and the short of it is – if you want your manual to be succinct but worth the effort – let me write it for you.

We at TechDocs are very motivated to get your users in the know.

Home

Facebook
WhatsApp
Twitter
LinkedIn
Pinterest